4 ms·

Would be interested to hear more about your setup!

browningstreet 9d ago
VPS is production. Linux dev box is my local big box. Macbook just lets me move about and do iOS development. Orca lets me run agents either on linux box or locally on the macbook depending on how I'm feeling, and Orca handles all the worktrees & sub-agents for me (via Opencode). Everything runs in a tailscale network, ssh connects all the things. My github repos all have CONSTITUTION.md files that keep multi-agent dev grounded. Production runs trigger github actions that automatically check logs daily, file bug reports, etc. I launch Orca and literally just type "checking in" and the CONSTITUTION.md file governs the scanning of github issues and prioritization of which issues need to be addressed. Another process prioritizes and bundles them. When I type "checking in" the Orca worktree handles the launching of sub-agents that fix things. Occasionally I weigh in with an opinion or pick a recommendation. If I'm in the mood to pay attention I'll ask it to find another round of bugs and let's keep going. Often I just let it close after the first round. When I tell it "done?" it does a full regression and a production box review. Code auto-deploys to production twice/day. I don't regularly push to production manually. On Fridays the CONSTITUTION.md kicks off a strategy and roadmap review when I type "checking in". As I have ideas I add them to the roadmap in one of the worktrees. Generally nothing happens until they're reviewed on Fridays together, unless I push one manually.. which happens. Hermes runs on the production box. I have a few skills and quick commands that lets me check in on production runs and the status of things. It's read-only by design, basically my version of a dashboard. If I have a thought, idea, research link, or question it'll write to a github issue and we'll deal with it in the next check-in. Orca lets me do all this remotely from an iPhone, and I talk to Hermes via Telegram. I generally don't INITIATE new work using either of these. I report issues/ideas and let the process do the things. But I can, and have.. I just tend not to. The whole thing churns, and so my inclination to "jump in and do a thing" is less than before. My inclination now is to toss things into the machine and let the machine work the schedule. I'm at a point where I could easily automate 80% of this and do my manual things 1x/2x week and I think progress would stay steady. I'll get there at some point, but I like the level of engagement I'm participating in now. Occasionally I use Claude Code as a watchtower review of things, or do a wholesale code review, or do a review of logs. But deepseek is much better at building this machine -- I built something manually over time and through a ship of theseus process it got ugly. Deepseek reviewed the situation and wrote the CONSTITUTION.md and designed the processes independently. It favors deterministic scripts for process but launches them via LLM and monitors for exceptions; also, no memory system which also disqualifies Claude from being at the center of this. Memory plugins didn't work well because instructions start accumulating all through the chain of instruction files (AGENTS.md, memory, etc) and that gets very undeterministic very quickly. Instructions are written once, reviewed/audited intentionally.. it's best not to let LLMs learn and write their own dynamically (yet). I've since used it as a template for other projects I've started -- they work the same. Currently building the GTM agent that will handle all SEO, marketing, keywording, etc for my projects -- it'll be a significantly autonomous Hermes agent. Don't really need Claude for any of this and my Deepseek bill is $50-100/mo.

VPS is production. Linux dev box is my local big box. Macbook just lets me move about and do iOS development. Orca lets me run agents either on linux box or locally on the macbook depending on how I'm feeling, and Orca handles all the worktrees & sub-agents for me (via Opencode). Everything runs in a tailscale network, ssh connects all the things. My github repos all have CONSTITUTION.md files that keep multi-agent dev grounded. Production runs trigger github actions that automatically check logs daily, file bug reports, etc. I launch Orca and literally just type "checking in" and the CONSTITUTION.md file governs the scanning of github issues and prioritization of which issues need to be addressed. Another process prioritizes and bundles them. When I type "checking in" the Orca worktree handles the launching of sub-agents that fix things. Occasionally I weigh in with an opinion or pick a recommendation. If I'm in the mood to pay attention I'll ask it to find another round of bugs and let's keep going. Often I just let it close after the first round. When I tell it "done?" it does a full regression and a production box review. Code auto-deploys to production twice/day. I don't regularly push to production manually. On Fridays the CONSTITUTION.md kicks off a strategy and roadmap review when I type "checking in". As I have ideas I add them to the roadmap in one of the worktrees. Generally nothing happens until they're reviewed on Fridays together, unless I push one manually.. which happens. Hermes runs on the production box. I have a few skills and quick commands that lets me check in on production runs and the status of things. It's read-only by design, basically my version of a dashboard. If I have a thought, idea, research link, or question it'll write to a github issue and we'll deal with it in the next check-in. Orca lets me do all this remotely from an iPhone, and I talk to Hermes via Telegram. I generally don't INITIATE new work using either of these. I report issues/ideas and let the process do the things. But I can, and have.. I just tend not to. The whole thing churns, and so my inclination to "jump in and do a thing" is less than before. My inclination now is to toss things into the machine and let the machine work the schedule. I'm at a point where I could easily automate 80% of this and do my manual things 1x/2x week and I think progress would stay steady. I'll get there at some point, but I like the level of engagement I'm participating in now. Occasionally I use Claude Code as a watchtower review of things, or do a wholesale code review, or do a review of logs. But deepseek is much better at building this machine -- I built something manually over time and through a ship of theseus process it got ugly. Deepseek reviewed the situation and wrote the CONSTITUTION.md and designed the processes independently. It favors deterministic scripts for process but launches them via LLM and monitors for exceptions; also, no memory system which also disqualifies Claude from being at the center of this. Memory plugins didn't work well because instructions start accumulating all through the chain of instruction files (AGENTS.md, memory, etc) and that gets very undeterministic very quickly. Instructions are written once, reviewed/audited intentionally.. it's best not to let LLMs learn and write their own dynamically (yet). I've since used it as a template for other projects I've started -- they work the same. Currently building the GTM agent that will handle all SEO, marketing, keywording, etc for my projects -- it'll be a significantly autonomous Hermes agent. Don't really need Claude for any of this and my Deepseek bill is $50-100/mo.