Skills no longer come from the user's ~/.agents library - most users have none, and the CEO branch that compiled the entire catalogue into its prompt overflowed the model context (1.1MB) and failed every CEO run. - Bundle "built-in skills/" with the app (extraResources) and stage it at startup into <profile>/builtin-skills as one dir-per-skill copy - both bundle shapes (SKILL.md dirs and flat category .md files) normalize into the same importable layout - Import the staged catalogue per org at startup and inside onboarding, so the CEO's first run already carries it - Forced house style: resolveRuntimeSnapshot unions the humanizer skill into every agent's runtime (CEO included) as a resolution rule - no binding row to forget, delete, or bypass; revoke_skill refuses it - CEO staffs hires with skills: hire_agent accepts a skills array, grant_skill/revoke_skill adjust later, list_skills now shows descriptions from skill frontmatter - Kill the c_suite compile-all branch; everyone resolves bindings-only, capped at 200k chars with omissions named in the prompt - Remove the Skills settings page and its import/sync/test IPC surface; drop ~/.agents discovery and the AGENTCOMPANY_NEW_SKILLS_ROOT seam in favor of AGENTCOMPANY_NEW_BUILTIN_SKILLS_DIR - Tests: staging/import/forced-resolution/cap units, real-bundle CI check, e2e asserts the tab is gone and the catalogue self-imports
80 lines
1.7 KiB
Markdown
80 lines
1.7 KiB
Markdown
# Codex Integration
|
|
|
|
Converts all Agency agents into Codex custom agent TOML files. Each source
|
|
agent becomes one standalone `.toml` file containing the minimal Codex-required
|
|
fields: `name`, `description`, and `developer_instructions`.
|
|
|
|
## Installation
|
|
|
|
### Prerequisites
|
|
|
|
- [Codex](https://developers.openai.com/codex/overview) installed
|
|
|
|
### Convert And Install
|
|
|
|
```bash
|
|
# Generate integration files (required on fresh clone)
|
|
./scripts/convert.sh --tool codex
|
|
|
|
# Install agents
|
|
./scripts/install.sh --tool codex
|
|
```
|
|
|
|
This copies generated agent files to `~/.codex/agents/`.
|
|
|
|
## Generated Format
|
|
|
|
Each generated file lives in:
|
|
|
|
```text
|
|
integrations/codex/agents/<slug>.toml
|
|
```
|
|
|
|
The mapping is intentionally minimal:
|
|
|
|
- `name` is copied from the source frontmatter unchanged
|
|
- `description` is copied from the source frontmatter unchanged
|
|
- `developer_instructions` contains the full Markdown body unchanged
|
|
|
|
Source-only metadata such as `color`, `emoji`, `vibe`, and other unsupported
|
|
frontmatter fields are omitted.
|
|
|
|
## Usage
|
|
|
|
After installation, reference the custom agent by name in Codex:
|
|
|
|
```text
|
|
Use the Frontend Developer agent to review this component.
|
|
```
|
|
|
|
Codex uses the `name` field inside the TOML file as the source of truth, so the
|
|
generated filename slug is only for filesystem safety.
|
|
|
|
## Regenerate
|
|
|
|
After modifying source agents:
|
|
|
|
```bash
|
|
./scripts/convert.sh --tool codex
|
|
./scripts/install.sh --tool codex
|
|
```
|
|
|
|
## Troubleshooting
|
|
|
|
### Codex integration not found
|
|
|
|
Generate the Codex artifacts before installing:
|
|
|
|
```bash
|
|
./scripts/convert.sh --tool codex
|
|
```
|
|
|
|
### Codex not detected
|
|
|
|
Make sure `codex` is in your PATH, or that `~/.codex/` already exists:
|
|
|
|
```bash
|
|
which codex
|
|
codex --help
|
|
```
|