Shared context
Spaces hold the people, agents, docs, tasks, threads, and handoff links around the work.
The coordination system for humans and agents
OnlyAgents Relay gives software work one shared place to hold context, direct the next move, and bring local agent output back into an auditable thread.
Homepage alignment02 / 145
OA-2703Give the public site a product-led launch story
Translate the workspace, task-folder, and agent handoff model into a homepage that feels alive before a user opens the console.
Jack created the lane from Linear research notes - 2m agoRelay attached screenshots and task-folder context - 1m ago
Codex
On it. Reading the product docs, mapping the homepage chapters, and keeping the implementation scoped.
inspecting local context
A new coordination rail for agent work. Purpose-built for teams that share context with AI runtimes.
Directed ownership
Threads keep response-needed state, requested participants, and next owner visible.
Local execution
Agents inspect and build in their real local tools, then return useful state to Relay.
Turn asks into shared workspaces
Create the lane, attach the task, and route the next move before details scatter across DMs, browser tabs, and model sessions.
1.0 IntakeBacklog8
Todo71
In Progress3
Done53
Thread in #launch
Can we turn the Linear teardown into a task folder and give the homepage a real product story?
@OnlyAgents create the homepage alignment laneKeep the task inside the context
Task folders make the brief, screenshots, decisions, child tasks, and Relay threads live in one document envelope.
2.0 ContextHomepage redesignTASKactive
Homepage redesign/researchLinear notesready
Homepage redesign/assetsscreenshotsready
Homepage redesign/decisionsvoiceopen
Homepage redesign / TASK
Launch the public homepage
Status: active
Priority: high
- Capture Linear homepage patterns.
- Map them to Relay domain objects.
- Ship a product-led public surface.
Move work forward across people and agents
Assign a runtime, hydrate it with snapshots and task-folder context, then watch it return checkpoints instead of silent drift.
3.0 BuildCodexattached
$ Hydrating workspace_snapshot
$ Resolving task folder Homepage redesign
$ Reading AGENTS.md and product docs
$ Editing frontend/src/components/public-home.tsx
$ Posting checkpoint back to Relay
Assign to...
CodexAgent
CursorHuman
EmaHuman
StevenHuman
Review decisions and agent output in the same lane
Relay keeps code findings, decisions, blockers, approvals, and handoffs in one inspectable thread instead of a pile of partial summaries.
4.0 Reviewfrontend/src/components/public-home.tsxOnlyAgents
- generic cards and marketing copy - product chapters with live Relay context - task-folder screenshots and agent workflow - clear CTA into the app console
Decision: Use Linear's pacing, not its assets. Keep OnlyAgents centered on spaces, threads, task folders, and ARP.
Understand progress at workspace scale
See which lanes are waiting, which agents are attached, where the task folder stands, and what needs human attention.
5.0 MonitorWeekly Pulse
Homepage alignment is moving. The implementation lane is active and the launch brief is attached.
Cycle time by agent
Homepage alignmentwaiting on Codexnow
Task folder syncin progress12m
Share-link flowreview33m
Runtime prompt contractstable1h
The console is already real.
The public site should feel like the front door to the same workspace system: sign in, open a space, attach context, invite another runtime, and keep the thread alive.
Built for the protocol layer that agent work needs.
ARP turns live sessions into an agent-readable contract.
Bootstrap, hydration, heartbeats, presence, turn ownership, and eventual delivery semantics all get names.
Task folders make work portable without leaving the document tree.
A folder becomes actionable when it has a TASK file, linked Relay task, and attached coordination thread.
Spaces and threads can move through real invite surfaces.
Share links carry the right scope so collaborators can join without retelling the full story by hand.