meisnerd

7 ms·

1.
by meisnerd 6mo ago
You're right that this is fundamentally a signal flow problem. The whole architecture is designed around that — tasks, inbox messages, decisions, and activity log are all just JSON files that any agent can read/write. The daemon p
2.
by meisnerd 6mo ago
100% agree on making debugging obvious. That's exactly why everything is local JSON files — you can literally cat tasks.json | jq '.tasks[] | select(.kanban=="in-progress")' and see exactly what's happening. No
3.
by meisnerd 7mo ago
It's modular by design, but the UI is the primary interface — no standalone CLI yet. On the opinionated/piecemeal question: the data layer is intentionally unopinionated. Everything is plain JSON files — tasks.json, inbox.json, de
4.
by meisnerd 7mo ago
"Orchestrating amnesiacs" — that's a good way to put it, and it's a fair critique of any system spawning claude -p sessions. Mission Control's mitigation is treating the shared data layer as the durable state rather
5.
by meisnerd 7mo ago
Yes. When you're making the task (or asking claude code to populate the mission/subtasks), you can mention what folder to output to (like in the task description or mission). So far I havent specified, and it has just been droppi
6.
by meisnerd 7mo ago
This is exactly right — and it's why acceptanceCriteria is a first-class field in the task schema, not just a description. Every task has an explicit acceptanceCriteria: string[] array that defines what "done" actually means:
7.
by meisnerd 7mo ago
Update: just shipped the loop detection + decision escalation I mentioned. Here's how it works now: When you run a "continuous mission" (one-click to execute an entire project), the daemon chains tasks automatically — as each
8.
by meisnerd 7mo ago
Thanks, man! A landing page is definitely on the list — right now I'm focused on getting the core solid first, but you're right that it would help with discoverability. For now the GitHub README is doing double duty as the landing
9.
by meisnerd 7mo ago
Great question — and I think you're right that self-evaluation is the harder problem. Right now, Mission Control's daemon handles the mechanical side: exponential backoff retries (configurable), maxTurns and timeout limits per ses
10.
Show HN: Mission Control – Open-source task management for AI agents(github.com)
45 points by meisnerd 7mo ago|21 comments