codex-symphony
Install and operate a portable OpenAI Symphony + Linear orchestration setup in any Git repository. Use when the user wants a one-command local Symphony runner, a reusable WORKFLOW template, background launch scripts, or a Codex wrapper that restarts Symphony automatically when reopening the CLI.
Best use case
codex-symphony is best used when you need a repeatable AI agent workflow instead of a one-off prompt.
Install and operate a portable OpenAI Symphony + Linear orchestration setup in any Git repository. Use when the user wants a one-command local Symphony runner, a reusable WORKFLOW template, background launch scripts, or a Codex wrapper that restarts Symphony automatically when reopening the CLI.
Teams using codex-symphony should expect a more consistent output, faster repeated execution, less prompt rewriting.
When to use this skill
- You want a reusable workflow that can be run more than once with consistent structure.
When not to use this skill
- You only need a quick one-off answer and do not need a reusable workflow.
- You cannot install or maintain the underlying files, dependencies, or repository context.
How codex-symphony Compares
| Feature / Agent | codex-symphony | Standard Approach |
|---|---|---|
| Platform Support | Not specified | Limited / Varies |
| Context Awareness | High | Baseline |
| Installation Complexity | Unknown | N/A |
Frequently Asked Questions
What does this skill do?
Install and operate a portable OpenAI Symphony + Linear orchestration setup in any Git repository. Use when the user wants a one-command local Symphony runner, a reusable WORKFLOW template, background launch scripts, or a Codex wrapper that restarts Symphony automatically when reopening the CLI.
Where can I find the source code?
You can find the source code on GitHub using the link provided at the top of the page.
Related Guides
SKILL.md Source
# Codex Symphony Use this skill when the user wants to install or operate a local OpenAI Symphony setup for a repository. ## When to Use Use this skill when the user asks to: - install Symphony into a repo - restart Symphony after reopening Codex - add a reusable `codex-symphony` command - bootstrap Linear-driven agent orchestration - create a portable Symphony package for another machine or repo - diagnose why Symphony is not starting - initialize repo-local Symphony env files safely ## Core Rule Do not assume a fixed repository path. Always resolve the target repo by: 1. explicit argument, if the user gave one 2. `git rev-parse --show-toplevel`, if running inside a repo 3. otherwise ask for the repo path ## Install Run the bundled installer: ```bash bash scripts/install.sh [optional-repo-path] ``` The installer will: - copy `WORKFLOW.symphony.md` - copy `scripts/symphony/*` - copy `.env.symphony.example` - enable `./scripts/symphony/init.sh` for `.env.symphony.local` - enable `./scripts/symphony/doctor.sh` for readiness checks - append `.symphony/` to `.gitignore` if missing - install `~/.local/bin/codex-symphony` - link this skill into `~/.codex/skills/codex-symphony` ## Operate After install, the normal commands are: ```bash ./scripts/symphony/init.sh ./scripts/symphony/doctor.sh codex-symphony ./scripts/symphony/logs.sh ./scripts/symphony/restart.sh ./scripts/symphony/start-background.sh ./scripts/symphony/status.sh ./scripts/symphony/stop.sh ``` ## Required Env The target repo must provide: - `LINEAR_API_KEY` - `LINEAR_PROJECT_SLUG` - `SOURCE_REPO_URL` - `SYMPHONY_WORKSPACE_ROOT` Optional: - `GH_TOKEN` - `SYMPHONY_PORT` ## Expected Help Pattern When helping the user: 1. run the installer if the repo is not bootstrapped yet 2. prefer `./scripts/symphony/init.sh` over manual env editing 3. run `./scripts/symphony/doctor.sh` before starting if setup looks incomplete 4. tell the user which env vars or tools are still missing 5. start Symphony only after the repo is configured 6. report dashboard URL and log path only