Build the right Codex agent team for this repository and goal.
Codesemble audits bounded project evidence, generates only the specialists your work needs, and shows every project-local change before applying it.
Quick start · How it works · Safety · Documentation
- Project-specific — agents are derived from your repository and intended outcome.
- Small by design — every proposed role must cover justified project work.
- Native and reversible — Codesemble configures Codex project files with exact preview, Doctor, and rollback support.
Codesemble is an open-source, repository-aware team builder for native Codex multi-agent orchestration. It configures Codex; it does not replace the Codex runtime.
codex plugin marketplace add VAMFI/codsemble --ref fc247152961c25e79b525a969806991f499a2bac
codex plugin add codsemble@codsembleThe pinned commit is the merged, validated v0.2 candidate. Start a fresh Codex session after installation so the plugin skills are discovered.
$codsemble:initialize-team Build the recommended Codex team for this workspace.
Codesemble audits the workspace and presents Focused, Recommended, and Extended options. It prepares a side-effect-free exact plan before writing any project file.
After you approve and apply the team, work normally in the primary Codex thread:
Review the checkout flow, fix the highest-risk issue, and validate the result.
Start another fresh Codex session after apply or configuration changes so the generated project agents are discovered.
The primary agent remains user-facing and accountable. Project-local orchestration guidance delegates bounded, separable work to installed specialists when useful, reconciles their evidence, and keeps final decisions with the primary thread.
Installed roles are available capabilities, not always-running processes. The project worker ceiling limits simultaneous spawned workers, excludes the primary thread, and is independent of installed role count.
$codsemble:update-team Re-audit this workspace and preview team changes.
$codsemble:team-doctor Check this project's generated team and configuration.
$codsemble:rollback-team Preview rollback of the latest Codesemble transaction.
You stay in control. Audit and preview are read-only. Codesemble writes project files only after you approve the exact current plan, refuses stale or changed plans, preserves transaction history, and previews rollback before restoring managed files. It does not change personal Codex settings or publish anything.
Repository evidence + your goal → Work Packages → Project team → Preview → Apply
- Audit bounded, typed project signals locally.
- Compile the capabilities and separable work the goal requires.
- Generate evidence-backed Focused, Recommended, and Extended teams.
- Preview every role, sandbox, instruction, and configuration change.
- Apply only the exact fresh plan you confirm, with Doctor and rollback support.
Repository evidence
GitHub Actions + delivery goal + security requirement
Recommended Codex team
Delivery specialist owns the delivery Work Package
Security specialist reviews the security boundary
Independent validator verifies the high-risk delivery path
Spawned-worker ceiling: 4
The names and number of agents change with the repository evidence and confirmed goal. Codesemble explains the evidence and Work Package behind every generated role before apply.
Read the compiler contract → · See the architecture →
Codesemble does not install a fixed team of 111 agents.
The current 111-entry catalog is a reusable primitive library—not a roster, recommendation ceiling, team-size target, or concurrency limit. For each workspace, the compiler derives Work Packages from bounded evidence and explicit goals, then generates only justified project-specific roles.
- Focused is the smallest complete team covering required Work Packages.
- Recommended adds independent verification only for evidenced high-risk work.
- Extended adds only closed-rule, evidence-backed optional lifecycle work and may equal Recommended.
Catalog size, installed roles, and active workers remain separate. A project may install 12 useful specialists while allowing only 4 workers to run concurrently.
Explore the primitive library → · See the bounded comparison →
- Solo builders who want useful specialists without designing a team by hand.
- Maintainers who need reviewable, reversible project configuration.
- Product teams whose work spans engineering, testing, design, docs, growth, or operations.
- Organizations that want project-local defaults without silently changing personal Codex settings.
AGENTS.md bounded orchestration guidance
.codex/agents/<role>.toml native specialist definitions
.codex/config.toml optional project worker ceiling
.codex/codsemble/manifest.json ownership and selected-team record
.codex/codsemble/transactions/ reversible transaction history
Codesemble does not edit ~/.codex/config.toml, mark a project trusted, collect
credentials, broaden permissions, or publish anything for you.
Understand configuration safety → · Read the privacy boundary → · Review the threat model →
| I want to… | Read… |
|---|---|
| Install, initialize, update, diagnose, or roll back | Usage |
| Understand the compiler and native Codex outputs | Architecture |
| Inspect EvidenceRef, capability, Work Package, and admission contracts | Project Capability Compiler |
| Migrate a v0.1 team safely | v0.2 migration |
| Review concurrency, no-clobber apply, and recovery | Configuration safety |
| Approve from a realtime voice session | Voice-friendly approval |
| Understand reusable primitives and dynamic generation | Primitive library |
| Understand local data handling | Privacy |
| Review trust boundaries and abuse cases | Threat model |
| See what has actually been tested | Validation evidence |
| Compare Codesemble with simpler baselines | Bounded usefulness comparison |
| Understand the project promise and release gate | Definition of Done |
| Reuse the visual identity correctly | Brand guide |
Codesemble v0.2.0 is merged on main as the Project Capability Compiler
candidate. Its merge-head CI passed on Node 22 and 24 across Ubuntu, macOS, and
Windows, with CodeQL and dependency review also passing. It has not been tagged,
released, or marketplace-published; v0.1.0 remains the latest release.
Runtime and physical-device claims remain tied to the exact tested payload and boundary. Structural checks never prove that every Codex version, policy, model, operating system, or voice device will accept a generated team.
See validation evidence → · View the roadmap →
Try Codesemble in an isolated repository and report where its audit, proposed roles, or explanations were incomplete. Contributors can add representative fixtures, improve compiler policies, strengthen lifecycle tests, or refine the documentation.
Start with the contribution guide, use support guidance for reproducible questions, and report vulnerabilities through the private process in SECURITY.md.
Codesemble is an independent open-source project licensed under the Apache License 2.0.