Skip to main content
Put the rules that shape a session there, and put the team somewhere you can run. An AGENTS.md is read by one harness in one session, and it goes stale without anyone noticing. The team is a different thing: which stage gets which engine, the files it may write, who reviews it, and where a no goes. In Obversa that is a TypeScript file. Claude Code, Codex, Grok and OpenCode are seats in it, each engine call is a fresh process, and the file runs the same way every time. Obversa does not load that file as a prompt inside one harness, and it does not review your instructions file for you.

In Obversa

Five stages, a panel that passes on two of three, and a person at the end, in the file that runs them:
examples/feature-team.ts (excerpt)
target names where a failing panel returns the work, and maxKickbacks caps how many times. Save the file, share it, and run it again.

Agent harness

The harness is the thing an AGENTS.md shapes. Obversa runs harnesses as seats. What is an agent harness? has the term.

Next steps