Codesemble

Open source · project-scoped · preview before apply

Get the right Codex team for this repository.

Codesemble audits your project, proposes a small evidence-backed team, and shows the exact project diff before anything changes.

Try Codesemble See the 60-second loop
Read-only auditHuman approvalRollbackable
A repository's file signals flow through a compiler into three project role cards.
Repository clues options approved team

The useful part

One clear loop from project context to project help.

No fixed roster. No hidden setup. You see why each role appears and what will be written.

AuditCompileReviewApply
01

Audit

Read repository clues locally and pair them with the goal you state.

project + goal
02

Compile

Turn the work into the smallest complete set of useful roles.

work → capabilities
03

Review

Compare Focused, Recommended, and Extended options with evidence.

options → exact plan
04

Apply

Approve the fresh plan, then verify or roll it back from the project.

human decision → files

Illustrative example

See the decision before you make it.

Change the project clue or coverage level. The example is a model of the explanation Codesemble gives you—not a fixed promise.

Project clues

Release a payment flow safely

An existing test boundary gives the compiler a concrete validation owner.

Recommended · required work plus independent verification

The catalog is a capability library. The project and goal decide the roles.

Control stays visible

Your Codex session stays in charge.

Generated specialists are available capabilities, not an always-running swarm. The primary thread delegates bounded work 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.

Read the safety boundary
Project-local output

Useful files, visible before they land.

  • AGENTS.mdorchestration guidance
  • .codex/agents/<role>.tomlnative specialists
  • .codex/config.tomloptional worker limit
  • .codex/codsemble/manifest.jsonteam ownership
  • .codex/codsemble/transactions/rollback history
What does “preview” mean?

The plan names roles, instructions, configuration, and every managed path. Apply rechecks the exact plan and refuses stale project state.

Start with your project

Install, restart Codex, and ask for the smallest useful team.

Codesemble is project-local. It does not edit your personal Codex settings or publish anything for you.

  1. InstallAdd the plugin from Git.
  2. RestartOpen a fresh Codex session.
  3. InitializeRun the audit in your workspace.
Terminal
codex plugin marketplace add VAMFI/codsemble --ref fc247152961c25e79b525a969806991f499a2bac
codex plugin add codsemble@codsemble

Then ask: $codsemble:initialize-team

Keep exploring

Clear docs for the details.

01UsageInstall, initialize, update, diagnose, roll back.02Compiler contractUnderstand evidence, capabilities, and team options.03Voice approvalUse a speakable exact challenge without weakening control.04ValidationSee what has actually been tested and where.
Why is there a 111-entry catalog?

It is a library of reusable capability primitives, not a roster or team-size target. Codesemble dynamically selects only roles justified by the repository and goal.