Use the certified Codex integration—or an explicitly described projection or manual workflow in another host—with the same Project Memory, Task lifecycle, and completion rules.
Changing agents or starting a fresh conversation does not reset the project.Tell your agent the outcome and the safety boundary.
Skopos can help translate the request into its technical model after the intent is clear.
“Set up this coding-agent host to load compact Skopos Session context at the start of work. Show me which context, handoff, child-Task, compaction, and completion capabilities the host can actually provide, and use the documented manual fallback for anything unsupported.”
A reviewed path from intent to project behavior.
- 01
Load context
The host receives a compact view of relevant Memory, current work, questions, and next safe action.
- 02
Project the lifecycle
Host-native features may open Sessions, deliver child work, or return completion without inventing new Task semantics.
- 03
Fall back honestly
Unsupported automation returns an exact reviewed prompt or command instead of pretending delivery happened.
Common project uses.
- Start a fresh Codex Task with bounded work
- Resume after conversation compaction
- Review the available Claude Code hook projection
- Copy a reviewed assignment into another host
The Skopos names for what you just configured.
- Host adapter
- A bridge that projects the Skopos lifecycle into a coding-agent environment.
- MCP
- Structured access to the same Skopos runtime authorities used by the CLI.
- Session
- One participant's recoverable view and role in the current project work.
A host adapter never creates a separate work model. Support must be described capability by capability, and generated assignments are not reported as delivered unless the host operation succeeds.