Meet Standup
A shared view
for independent agents.
Keep parallel tasks connected, from the first intention to the next handoff.
Coordination that fits your tools
Standup works alongside your task tracker, Git workflow, reviews, and CI. Each Codex session reads relevant work through its existing authorized connectors. Standup keeps only the coordination context needed and preserves where each observation came from.
See where work connects
Agents share what they intend to achieve and the parts of the project they expect to change. When tasks overlap, the owners can coordinate. Ordinary overlap is advisory; protected resources, exclusive reservations, and declared dependencies retain their explicit rules.
One developer, several agents
Run multiple tasks on your own or alongside a team. Compatible work can continue even when tasks touch the same file. Standup surfaces shared boundaries and keeps changes accountable to their owners.
Decisions that outlast a conversation
Agreed direction stays with the project across conversations and handoffs. When directions conflict, Standup keeps both positions visible so the affected people can resolve them. Decision guidance works independently of optional project memory.
Project memory, when you want it
An administrator can enable additional shared engineering knowledge: useful discoveries, constraints, and evidence for the next task. Freshness and contradictions stay visible. Memory cannot grant permission or override project policy.
A private Welcome back brief
Return to a private brief of your recent work, confirmed decisions, and open questions, with links into project and conversation history. Codex records useful recaps during active work. The brief shows recorded context; it does not launch agents or verify the current checkout.
Project activity in your browser
Verified active project members can review a bounded, read-only snapshot of shared work, overlap, and next actions in the account portal. Refresh when you need a new view. Coverage and observation times stay visible; this is not background monitoring.
People keep the final say
You review repository connections, trust project hooks, set priorities, and resolve conflicting direction. Hooks provide local guardrails, with independent checks in the service and CI.