Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Zerostack – A Unix-inspired coding agent written in pure Rust

crates.io

Post reply on HN
Print view View original

241–250 of 334 posts

Re: Zerostack – A Unix-inspired coding agent written in pure Rust

#241

Post by gidellav »

nextaccountic wrote: post #237

> Bash execution ... optional sandboxing for isolation Sandboxing should be the default. Rather than routinely allowing unsandboxed access, one should be able to configure the sandbox to allow exactly what is needed That's hard. For example, I've been unable to give wayland access to agents inside the sandbox (there's a special flag in bubblewrap to mount /dev/dri in a way you can make use of it, but you also must gi…

This is actually a topic of current interest, and I think that I will switch to a sandbox-by-default once the bwrap implementation inside of zerostack is well tested and highly configurable.

Re: Zerostack – A Unix-inspired coding agent written in pure Rust

#242

Post by gidellav »

whazor wrote: post #216

It says inspired by Pi, but I don't see any extension/plugin possibilities. The best feature of Pi is that an extension can hook anywhere and completely change the behavior. It also allows two extensions to stack on the same hook where there are no conflicts. I believe Pi extensibility is the most important feature, exactly as how it was important for WordPress. WordPress won because anyone could install it and add t…

Check https://news.ycombinator.com/item?id=48164948

Re: Zerostack – A Unix-inspired coding agent written in pure Rust

#243

Post by gidellav »

zbyforgotp wrote: post #145

We don’t trust llm execution- so we add user approvals. But task decomposition calls for co-recursion between code and prompts. This means that the approvals should be evocable at any depth. I think we need some kind of protocol for that (à la the Cubes OS protocols for cut and paste between vms). Maybe a workaround could be to use bubblewrap of the scripts ther recursively call the llm (and run the agent in yolo ins…

zerostack contains --sandbox flags that forces bwrap usage on all shell tool usage

Re: Zerostack – A Unix-inspired coding agent written in pure Rust

#244

Post by crabmusket »

tjoff wrote: post #189
rullopat wrote: post #173

I understand the need for memory footprint in some situations, but what's the point of seeking performance for a software that mostly calls LLMs and waits?

Before I tried coding agents my guess would have been: none. But seeing how slow claude code and copilot cli are and how much ram they use I'm flabbergasted. If you have long running sessions they can both take tens pf gigabytes of ram and feel quite sluggish.

I've been playing with running Claude Code inside a Vagrant VM. I can't be certain it was getting OOM killed when I allowed the VM 4GB of RAM, but when I went to 16 it did seem to be more stable...

Re: Zerostack – A Unix-inspired coding agent written in pure Rust

#245

Post by krzyk »

cyberpunk wrote: post #153
rvz wrote: post #84

Earlier quoted context omitted.

yes.

How come the official codex install instructions say use npm install? (I just rebuilt my sandbox vm a few days ago….) Or are there two separate codex clients? https://developers.openai.com/codex/cli

Because people are crazy, usage of npm for installing binaries is quite common unfortunately.

Re: Zerostack – A Unix-inspired coding agent written in pure Rust

#246

Post by crabmusket »

ink-splatters wrote: post #234
jwxz wrote: post #190

Earlier quoted context omitted.

I didn't see anyone mention this, but I think having a single binary is much nicer than having a JS (or Python) program sprawled all over your system.

Having single binary output is completely different problem and is solved for both Python and typescript (bun supports the later).

Node and Deno can also bundle apps into a single executable.

Re: Zerostack – A Unix-inspired coding agent written in pure Rust

#247

Post by krzyk »

kirtivr wrote: post #83
usernametaken29 wrote: post #51

Now make it into an IntelliJ plugin which has proper access to the search index. I’ll pay for it. For Christs sake it’s insane JetBrains hasn’t figured this out yet

Jetbrains does not have their own IDE-integrated coding agent? What do Jetbrains users use then? Amp?

What is the use case for integrating coding agent in IDE?

I use run agents outside of my IDE, while they work I can look at the code they created, or I can us IDE to do different work.

Re: Zerostack – A Unix-inspired coding agent written in pure Rust

#248

Post by hnlmorg »

tcfhgj wrote: post #232
gf000 wrote: post #228

Earlier quoted context omitted.

What's the latency difference between a long running process issuing a network call in Java vs rust? This is such a short time that it is completely overshadowed by noise (OS doing something else, what other software is running etc) As for throughput: you have 1-2 requests going at a time, the next one waiting for the reply. What throughput are we talking about? That's like speeding to the post office and expecting y…

you seem to specifically aim at the current example, but mine wasn't Anyways, consider how higher memory usage can affect the systems performance dramatically once the system needs to start swapping memory to disk signficantly

If you cannot write a simple Java agent without consuming so much RAM that your system is swapping then that really says more about the developer than anything.

Java is used in plenty of embedded systems and other memory constrained environments. Yes, it’s not going to perform well compared with Rust, but that doesn’t mean it’s an Electron-equivalent bloated clusterfuck of an ecosystem that’s going to eat all your system resources.

Re: Zerostack – A Unix-inspired coding agent written in pure Rust

#249

Post by bheadmaster »

ijustlovemath wrote: post #227
GodelNumbering wrote: post #205

Earlier quoted context omitted.

I haven't used Rust extensively but my feeling is, if you change the design (which inevitably happens in many early stage projects), the refactoring takes more time due to borrow-checker semantics. Although I am far from a representative sample and could well have been using it wrong

When you write Rust long enough you settle on certain architectures (message passing, event loops) that go well with the borrow checker, and don't end up thinking about it too much. Plus you can always throw an agent at the first set of errors from the refactor and let the compiler guide the annoying parts.

> When you write Rust long enough you settle on certain architectures (message passing, event loops) that go well with the borrow checker

So basically Go?

Post reply on HN