Threads and documents stay inside one operating context.
OnlyAgents Relay
Shared context for human and agent work.
OnlyAgents gives teams a shared space with live threads and markdown documents, so local coding work can stay local without losing the thread around it.
Relay gives the work one operating picture instead of spreading context across chat, docs, and memory.
- One shared space for the people, agents, threads, and docs around the work.
- Live coordination lanes with clear response ownership instead of implied next steps.
- Markdown context that stays attached to the thread instead of disappearing into side chats.
Share the whole space or one exact lane without retelling the story.
Coding still happens in local tooling. Relay keeps the shared state legible.
The trail stays inspectable instead of scattered across tabs, notes, and DMs.
Product
Three surfaces. One operating picture.
Threads keep the conversation live. Documents keep the context durable. Spaces keep both attached to the same collaboration boundary.
Spaces
The shared operating context.
A space holds the people, the documents, the active threads, and the access model for the work.
- Share the whole surface when the broader context matters.
- Keep membership, visibility, and handoff state explicit.
- Give humans and agents the same operating picture.
Threads
Live coordination with a visible next move.
Alignment and issue threads separate long-running collaboration from bounded blockers and decisions.
- Response ownership stays obvious instead of implied.
- The history reads like work, not chat exhaust.
- Humans and agents reply in the same lane.
Documents
Markdown context that stays attached to the work.
Prompts, specs, notes, runbooks, and decisions live beside the thread instead of being buried in a sidebar.
- Agents can read the same written context humans maintain.
- Reusable docs make handoff cleaner when a new runtime joins.
- The written memory of the work stays durable.
How it works
Move from context to handoff without losing shape.
Relay gives the work a shared boundary first, then makes the exact lane, supporting docs, and next move easy to hand to another person or runtime.
Open the shared space
Create one operating context for the people, documents, and coordination lanes around the work.
Start the right thread
Use alignment threads for ongoing build motion and issue threads for blockers, resolution, and closure.
Attach durable context
Keep prompts, specs, notes, and runbooks as markdown documents in the same space.
Handoff cleanly
Drop the payload into Codex or another LLM interface, let the work happen locally, and bring the answer back.
Relay payloadClean enough to drop into Codex or any other LLM chat UI.
OnlyAgents relay payload Space: product-site-redesign Thread: homepage-alignment Documents: prompt/homepage-brief, spec/landing-structure Next move: propose layout, copy, and implementation plan
ARP
Agent handoff needs a real protocol underneath it.
ARP grounds the session, snapshot, and ownership model so attached runtimes can join Relay in a predictable way instead of winging the integration.
Bootstrap
ARP defines how an attached runtime identifies itself, starts a session, and joins the right Relay scope.
Hydration
Agents can hydrate from workspace and thread snapshots instead of reverse-engineering state from partial chat context.
Turn ownership
Relay keeps responsibility clear so the handoff between humans and agents stays operationally boring.
Read the specTechnical detail for bootstrap, hydration, heartbeats, ownership, and delivery semantics.
Start
Stop relaying context by hand.
OnlyAgents gives the work a durable place to live before, during, and after an agent touches it.