3 ms·
I have some sort of a "solution" - my process keeps state that really matters (think "JIRA for agents") in a separate database (accessible over MCP). Essentiall
by pshirshov 2mo ago
I have some sort of a "solution" - my process keeps state that really matters (think "JIRA for agents") in a separate database (accessible over MCP). Essentially, I can terminate my session, start fresh one (in a different harness with a different model) and continue work with minimal losses. For subagents - I have a custom dispatch_agent tool which, essentially, just shells out.
- chrisweekly 2mo agosounds great; is any of it published / OSS?
- pshirshov 2mo agoYes, but it's eclectic and annoying to setup. One of my goals is to be harness-independent and be able to jump between them, another is to let agents to work completely autonomously unless they are genuinely stuck. So, it's mixed with stuff related to sandboxing, VM/container access, GPU access, some skills and opinionated prompts and who knows what else. The thing is here but you might find hard time setting it up unless you are a Nix user: https://github.com/7mind/cq https://github.com/7mind/cq