Show HN: Self-hosted company OS, Claude Code and Codex agents in departments
21–24 of 24 posts
[flagged]
Re: Show HN: Self-hosted company OS, Claude Code and Codex agents in departments
#22[flagged]
Re: Show HN: Self-hosted company OS, Claude Code and Codex agents in departments
#23If you organize agents by department, who verifies an agent's 'completion' report? In my experience, reviews using the same model rarely caught its own mistakes—only a different model or execution receipts (rc·sha256·stderr) caught them. How are you handling this here?
OtoDock does not verify a report by itself, but you can set it up in your installation. A delegated agent runs as a normal session on the platform, so the whole run is persisted, every tool call and its output, and both the delegating agent and a human can open that session instead of trusting the summary. Delegation can also pin a different model or engine per lane, so the reviewer can run on Codex or a local model while the worker ran on Claude.
For the deterministic part I use scripts, not agents. For example to publish a new version I have a script with all the gates, it runs the tests and the scanners and refuses the export if anything is off. The agent cannot declare a release done, the script does.
Re: Show HN: Self-hosted company OS, Claude Code and Codex agents in departments
#24Looks great. I didn't like the paperclip system with my main issue being that agents would go over daily budgets all too often. Looking forward to giving this a try.
Glad you like it. If you test it out I would love any feedback!