OtoDock creator Dimitris claims its released self-hosted, multi-tenant application lets teams collaborate on Claude Code and Codex agents using existing subscriptions or local models, potentially replacing separate coding-agent sessions with a shared company workspace.
state: seedheat: lowuncertainty: highconvergesscott: mediumagent-harnesses coding-agents self-hostingOtoDockDimitris
What is this?
The supplied case identifies OtoDock as a released application by a creator named Dimitris, pitched as a freely self-hostable “company OS” where teams collaborate with Claude Code and Codex agents organized into departments. Its claimed multi-tenant workspace, existing-subscription support, and local-model support are creator claims in the case, not independently verified by the supplied search snippets. Those snippets discuss other self-hosted coding agents and collaborative agent systems but do not directly establish OtoDock’s implementation or release; the web answer’s attribution to a team at Amazon is unsupported by the supplied results.
Why it matters to Scott
OtoDock’s claimed departmental company workspace converges with Scott’s All-in-one software programmable company runtime and overlaps his Proposal Compiler’s existing Claude/Codex job orchestration, making it a concrete build-versus-adopt comparison rather than just another multi-agent example. This is provisional product-direction convergence: the supplied material does not verify tenant isolation, durable coordination, or subscription/local-model compatibility, and the related radar pages track adjacent products rather than OtoDock itself.
dev:project.all-in-one-softwaredev:project.proposalradar:concorde-shared-organization-agentradar:claude-orgtree-visual-agent-orchestratorradar:open-session-agent-orchestrator
queries asked of Scott's wikis
- shared coding-agent workspaces versus individual sessions
- agent harness orchestration Claude Code Codex
- self-hosted agent infrastructure multi-tenant isolation
- subscription-backed agents versus API costs local inference
- team agent coordination shared memory persistent workspaces
Measured heat
now 0 pts/hpeak 0 pts/hcomments 0/hpeers p14momentum: steady2 platformsage 766h
points/hour across evidence · reading as of 2026-10-12 02:59:37.977291+11:00 · deterministic, not a model opinion
How the heat travelled
pace: p63 vs 519 stories at the 720h mark (now 766h old) — ahead of base3-ternary-gguf-packing (1.0x), behind hunterbench-live-pentesting-benchmark (0.9x)
Evidence (2) — ⭐ canonical anchor
Interpretation history
2026-09-10T18:01:59Z
The new comments sharpen the diligence question from workspace organization to reliable completion verification, but provide neither an OtoDock-specific failure nor independent validation. It remains a provisional build-versus-adopt candidate whose execution receipts, review mechanisms, and collaboration properties need demonstration.
2026-09-09T20:44:52Z
The refreshed discussion adds a parallel builder's interest and questions about routing and differentiation, not evidence that OtoDock's shared-agent workflow works in practice. It remains a provisional build-versus-adopt comparison; neither independent deployment nor the claimed collaboration and isolation properties are validated.
2026-09-09T18:32:03Z
OtoDock remains a creator-announced build-versus-adopt candidate, with no independent implementation or adoption evidence; the repository echo is the same creator's testimony, not corroboration. The prior alert rationale overstated the supplied evidence: persistent memory, sandboxing, and outbound-only remote execution are not established here.
2026-09-09T18:29:59Z
grounded: converges/medium — OtoDock’s claimed departmental company workspace converges with Scott’s All-in-one software programmable company runtime and overlaps his Proposal Compiler’s ex
2026-09-09T18:24:42Z
case created — A creator-linked deployable artifact establishes a distinct shared-agent workspace episode, though the supplied evidence does not substantiate the scout's additional sandboxing, memory, scheduling, or remote-worker claims.
Decision trace
- 09-26 12:34review_dormantscheduled targets exhausted or 28 quiet days
- 09-26 12:34drop_targetsquiet through full ladder or over cap 8
- 09-11 04:01repriceThe new comments sharpen the diligence question from workspace organization to reliable completion verification, but provide neither an OtoDock-specific failure nor independent validation. It remains
- 09-11 04:01alert_silentThe release announcement was already routed; the refreshed discussion adds useful evaluation questions, not a demonstrated capability, failure, or access change. These can wait for the next briefing w
- 09-11 04:01alert_routeThe release announcement was already routed; the refreshed discussion adds useful evaluation questions, not a demonstrated capability, failure, or access change. These can wait for the next briefing w
- 09-11 03:23sensor_dirtycomment_update
- 09-10 13:21sensor_dirtyengagement_update
- 09-10 10:21sensor_dirtyengagement_update
- 09-10 08:21sensor_dirtyengagement_update
- 09-10 07:21sensor_dirtyengagement_update
- 09-10 06:44repriceThe refreshed discussion adds a parallel builder's interest and questions about routing and differentiation, not evidence that OtoDock's shared-agent workflow works in practice. It remains a
- 09-10 06:44alert_silentThe release announcement was already routed. These comments add no consequential product, access, or implementation delta, so another interruption would repeat the existing case rather than inform a n
- 09-10 06:44alert_routeThe release announcement was already routed. These comments add no consequential product, access, or implementation delta, so another interruption would repeat the existing case rather than inform a n
- 09-10 06:22sensor_dirtycomment_update
- 09-10 05:22sensor_dirtyengagement_update
- 09-10 04:32repriceOtoDock remains a creator-announced build-versus-adopt candidate, with no independent implementation or adoption evidence; the repository echo is the same creator's testimony, not corroboration.
- 09-10 04:32alert_silentThe release announcement has already been routed, and this revisit adds no consequential delta. Retain the shared departmental-agent workspace as a provisional comparison for Scott's projects, bu
- 09-10 04:32alert_routeThe release announcement has already been routed, and this revisit adds no consequential delta. Retain the shared departmental-agent workspace as a provisional comparison for Scott's projects, bu
- 09-10 04:30alert_shadowThe creator’s release announcement makes OtoDock a concrete build-versus-adopt comparison for Scott’s programmable company runtime and Proposal Compiler orchestration today. The claimed package combin
- 09-10 04:30alert_routeThe creator’s release announcement makes OtoDock a concrete build-versus-adopt comparison for Scott’s programmable company runtime and Proposal Compiler orchestration today. The claimed package combin
- 09-10 04:29groundOtoDock’s claimed departmental company workspace converges with Scott’s All-in-one software programmable company runtime and overlaps his Proposal Compiler’s existing Claude/Codex job orchestration, m
- 09-10 04:24createA creator-linked deployable artifact establishes a distinct shared-agent workspace episode, though the supplied evidence does not substantiate the scout's additional sandboxing, memory, schedulin