Audit
Read bounded, typed project signals locally and pair them with the goal you state.
repository + goalOpen source · project-scoped · preview before apply
Audit your repository.
Assemble the smallest capable Codex team.
Codesemble turns repository evidence and your goal into a reviewable, native Codex team—without asking you to design every role by hand.
Evidence-ledNative outputHuman approval
01 Evidence in Native team out
The compiler loop
From a messy project to a useful team in three clear moves.
Codesemble keeps the reasoning visible, so the team is explainable before it is ever written.
Compile
Translate required work into the smallest complete set of evidence-backed roles.
work packages → rolesReview & apply
See the exact project diff, approve a fresh plan, then use Doctor and rollback when needed.
preview → apply → verifyA team that fits the evidence
Pick the level of coverage your project actually needs.
The names and count change with the repository. These options show the decision, not a fixed roster.
Example project signal
Release a payment flow safely
Codesemble found evidence for delivery, security review, and an existing test boundary.
Why this matters
A delivery goal activates a delivery work package and makes its evidence traceable.
Smallest complete coverage3 roles
Delivery specialistowns the release work
Security specialistreviews the security boundary
Test specialistchecks the payment flow
Required work plus high-risk verification4 roles
Delivery specialistowns the release work
Security specialistreviews the security boundary
Test specialistchecks the payment flow
Independent validatorverifies the high-risk path
Evidence-backed optional lifecycle work4 roles
Delivery specialistowns the release work
Security specialistreviews the security boundary
Test specialistchecks the payment flow
Independent validatorverifies the high-risk path
Spawned-worker ceiling: 4 primary thread excluded
You keep the wheel
The primary thread coordinates. You decide.
Generated specialists are available capabilities, not an always-running swarm. The primary Codex thread delegates bounded work, reconciles evidence, and owns the final result.
01
Preview first. Audit and planning are read-only.
02
Confirm exactly. Apply requires a fresh plan and human approval.
03
Recover cleanly. Doctor and rollback preserve project-local control.
Project-local output
Useful files, visible before they land.
Codesemble configures the project boundary. It does not edit personal Codex settings, trust, credentials, or runtime permissions.
AGENTS.mdorchestration guidance.codex/agents/<role>.tomlnative specialists.codex/config.tomloptional ceiling.codex/codsemble/manifest.jsonteam ownership.codex/codsemble/transactions/rollback historyWhat does “preview” mean?Expand the review boundary
Before apply, the plan names the roles, instructions, sandbox/profile requests, worker ceiling, and every managed path. Apply rechecks the current plan, relevant evidence, and output preimages.
+ .codex/agents/security.toml
+ .codex/codsemble/manifest.json
· personal ~/.codex/config.toml untouched
A common misconception
111 is a library, not a roster.
The catalog contains reusable capability primitives. Codesemble selects only roles justified by your project and goal; installed roles and active workers remain separate.
Explore the primitive library111reusable
primitives
primitives
delivery
security
validator
Start with your repository
Let the project tell you what team it needs.
Install the plugin, open a fresh Codex session, and ask Codesemble to audit before you choose a team.
Install from the validated v0.2 candidate
codex plugin marketplace add VAMFI/codsemble --ref fc247152961c25e79b525a969806991f499a2bac
codex plugin add codsemble@codsembleThen ask:
$codsemble:initialize-team Audit this workspace and help me choose the smallest useful team.Go deeper when you are ready