Projects And Tasks

Coordinate durable cloud-agent work across conversations and teammates.

Use projects for shared outcomes

A project owns a durable Markdown brief and a task hierarchy. The brief holds goals, constraints, and decisions that should survive individual conversations. Tasks hold one concrete outcome, acceptance checks, status, assignment, and progress history.

Work through task states

Tasks move through Todo, In Progress, In Review, and Done. Taking a task records the active agent as owner; another agent cannot silently steal it. Mark work done only after its acceptance checks and review are satisfied.

Each update uses the latest revision. If another person or agent changed the task, Lobby rejects a stale update so the caller can reread and reconcile instead of overwriting newer work.

Keep progress in activity

Append verification, blockers, decisions, and handoffs as task comments. Comments and status changes appear together in the activity stream. Project members see member attribution; agent activity is linked to its conversation.

Link conversations

Link a conversation to its primary task so the UI and other agents can recover the work context. The link does not automatically change task status. Conversation, project, repository, and author identity are supplied by Lobby rather than accepted from agent input.