gidellav

6 ms·

1. 31.▲
   by gidellav 4mo ago

   Actually, those two are different versions, but I am considering writing a full-length blog post on what changed in the last 2 weeks (aka: a lot).
2. 32.▲
   Zerostack v1.3.4 released – Lightweight Unix-inspired coding agent(crates.io)

   13 points by gidellav 4mo ago|3 comments
3. 33.▲
   Zerostack v1.3.4 released – Lightweight Unix-like coding agent(github.com)

   6 points by gidellav 4mo ago|0 comments
4. 34.▲
   Zerostack v1.3.2 Released(github.com)

   2 points by gidellav 5mo ago|0 comments
5. 35.▲
   by gidellav 5mo ago

   Check what tools we already implemented, check your "slow" accusation, check the prompt system, check the provider integration (via Rig, so caching is already enabled), check the MCP support and other integrations that you don&#x2
6. 36.▲
   by gidellav 5mo ago

   zerostack contains --sandbox flags that forces bwrap usage on all shell tool usage
7. 37.▲
   by gidellav 5mo ago

   Check https://news.ycombinator.com/item?id=48164948
8. 38.▲
   by gidellav 5mo ago

   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.
9. 39.▲
   by gidellav 5mo ago

   Well... for the most part, you use it like skills, but instead of "commands" you can think of "environments": so '/prompt debug', which is one of the integrated prompts, allows for a debug-focused agent, y
10. 40.▲
    by gidellav 5mo ago

    I am currently deciding on adding ACP support or not (and ACP support should allow connections to JetBrains's IDEs)
11. 41.▲
    by gidellav 5mo ago

    Retry from Safari, sometimes it works better
12. 42.▲
    by gidellav 5mo ago

    Yes, I am open for PRs. What you showed is a clear bug in my codebase, if you can, open a Github issue with each of your bugs. Thanks!
13. 43.▲
    by gidellav 5mo ago

    Isn't 2 second startup time a lot? With zerostack, I managed to get it down to ~90ms
14. 44.▲
    by gidellav 5mo ago

    Exactly, this was my thought process when deciding if we should have Skills or not. In the end, I think that this prompt-only design, with the integrated tools that come with zerostack, is more than enough.
15. 45.▲
    by gidellav 5mo ago

    I understand the concept, but I don't get what's the advantage over adding in the prompt instructions to use a specific bash command for a specific task, acting as a "custom tool".
16. 46.▲
    by gidellav 5mo ago

    Some interesting features I add on top of being lightweight are the prompts library, Git worktrees integration and Ralph Wiggum loops integrations.
17. 47.▲
    by gidellav 5mo ago

    1. I will add some screenshots tomorrow 2. As said before, there are no benchmarks right now, but it is good enough for me, so I hope it's good enough for y'all :) 3. Transfering settings from other agents is out-of-scope for a mi
18. 48.▲
    by gidellav 5mo ago

    Hi, nice comment! 1. I had experience not only with wrong versions selected by the agents, but also weird crates (ex. choosing a crate with 10 github stars when a more complete and more supported one was available), reason why now I always
19. 49.▲
    by gidellav 5mo ago

    I get you, but when I decided to follow a no-skills approach (as in, no agent's Skills used), I had to decide what: 1. Couldn't be built only using prompts 2. Couldn't be built only using MCP servers 3. Would have improved my
20. 50.▲
    by gidellav 5mo ago

    I have to be honest and tell you that try to load such an heavy runtime as a scripting layer is not a great idea; at the same time I can tell you that I am working on another Rust project where I also needed scripting, and after three attem
21. 51.▲
    by gidellav 5mo ago

    Thanks! I don't think that the only advantages are being open and lightweight, but you can actually find some more interesting features such as Ollama support, integrated Prompts (in order to compete with superpowers), git worktrees in
22. 52.▲
    by gidellav 5mo ago

    Yes! This project derived from an OOM killer activation that happened on my old laptop beacuse i had more than 2 opencode instances open together with Firefox...
23. 53.▲
    by gidellav 5mo ago

    I actually though about this issue, but while Pi can have this script-like environment thanks to the fact that it's based on an interpreted language (TypeScript), Rust has its own limitation as a compiled language. I decided to allow f
24. 54.▲
    by gidellav 5mo ago

    While I think that the core philosohpy is the same, i'd like to ask: why adding features like Skills and prompt templates? I personally decided to not implement Skills and instead using a prompt library approach, where certain .md are
25. 55.▲
    by gidellav 5mo ago

    No problem, happy to help!
26. 56.▲
    by gidellav 5mo ago

    While I agree on the fact that it allows to manage resources efficiently, I don't agree on the fact the efficency derives from it being high-level; from a purely tecnical standpoint, i could skim off 2-3MB from the memory footprint by
27. 57.▲
    by gidellav 5mo ago

    Hi! While I didn't try any agent benchmark, I already though of this possible issue, and I tried to approach it on two different levels: 1. The tools that are given to the agent are almost the same to the one defined in Opencode, excep
28. 58.▲
    by gidellav 5mo ago

    Thanks! Funny enough, a good chunk of the coding was done by Deepseek v4 Flash, while I hand-wrote a couple of the TUI logic, as deepseek kept failing on certain cursor-moving logic, and I fully managed the memory optimization process (as y
29. 59.▲
    by gidellav 5mo ago

    Hi, I'm the developer of zerostack! No, the memory footprint is not beacuse of the context window size: on my benchmarks, with a 128k context loaded, and it jumped from 8MB (without any chat/context loaded) to 11MB. The reasons w
30. 60.▲
    Zerostack – A Unix-inspired coding agent written in pure Rust(crates.io)

    575 points by gidellav 5mo ago|308 comments