Skip to content

IMPORTANT: Druids office running in codeSplitter, and the preview stays up until the owner has seen it #1412

Closed

Description

@QuinnsCode

Important. Owner's words: "I want Druid Office to be running in codeSplitter. I want that worker to stay alive until I have seen this happen. That might mean I have to now push codeSplitter to its own room tomorrow."

What this is

The Druids-skinned Agent Office (the 3D office with workers, queue and PR board) running as a codeSplitter feature, on the office-preview stage from apps/agent-office/PREVIEW.md (#1385, plan in #1384).

State today

  • The stage and runbook exist. Nothing is deployed from them.
  • The office itself is not in the Worker yet: the Durable Object for the queue, desks and roster, and the 3D client (with the Druids skin) served from the Worker. The four gaps in MOVE.md are open too: PTY over WebSocket, container lifetime, per-floor cost cap, auth mapping. PREVIEW.md says checks 1 to 5 can't pass until those land.

Stay-alive rule (until the owner has seen it running)

  • Do not rustybuns destroy --stage office-preview, and do not send home the worker driving it, until the owner says they have seen the Druids office running in codeSplitter.
  • The live office (apps/agent-office binary) and the live codeSplitter stage keep running untouched, as MOVE.md says.
  • Price it against COSTS.md first; smallest resources; destroy only after the owner has seen it.

Tomorrow

The owner may push codeSplitter to "its own room" tomorrow (2026-10-14). That wording is a guess at what was meant (own repo? own org? own deploy?). Settle it before then; whatever it is, apps/codesplitter must stay valid for the Cloudflare git competition (submission closes 2026-10-14 11:59 PM PDT; keep Workers + Artifacts, LICENSE, accurate run instructions, tag contest-submission).

Done when

  • The Druids office loads from a codeSplitter Worker and a worker takes a task to a PR on a throwaway repo (checks 1 to 5 in MOVE.md).
  • The owner has seen it. MANUAL RUN: the deploy and the viewing need the owner (secrets via varlock).
  • What "its own room" means is written here, and the docs match.

Metadata

Metadata

Assignees

Labels

codesplittercodeSplitter (apps/codesplitter)enhancementNew feature or requestmanual runNeeds the owner to run it by hand (tokens, sign-ins); agents can't close it

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions