twagent 2.4.1

Unified configuration framework for AI coding agents — Claude Code, Copilot CLI, Pi, Codex, VS Code, opencode. One canonical TOML, one CLI, two deploy modes.

What you get

• One config at ~/.config/twagent/config.toml describes every skill, subagent, prompt, instruction template, and MCP server you care about.
• One CLI (twagent apply) renders Jinja templates, symlinks file artifacts, and compiles MCP configuration in each agent's native shape.
• Runtime secrets stay as ${VAR} references (or Codex's environment-backed fields), so twagent never writes resolved credentials.
• Two deploy modes: globally (each agent's default profile to ~/.claude/, ~/.copilot/, etc.) or locally (into the current directory).

twagent apply --global                          # sync everything globally
twagent apply -s tw-claude                      # local: drop a profile into cwd
twagent apply --global -s e2e-emea              # swap MCP env for the day
twagent apply --global -s e2e-emea -a copilot-cli  # one agent only

Mental model

  ┌──────────────┐    ┌─────────────┐
  │  Registries  │ →  │   Profiles  │ →  apply (local | global)
  │              │    │ (composable │        │
  │ instructions │    │   bundles)  │        ▼
  │ skills       │    │             │   per-agent paths
  │ subagents    │    │  extends... │   (global or cwd-relative)
  │ prompts      │    │             │
  │ servers      │    │             │
  └──────────────┘    └─────────────┘

• Artifacts live in registries — globally unique name + source path.
• Profiles bundle artifact references, composable via extends.
• Agents declare capabilities and per-kind paths (global and per-project).
• global_profile is the bridge: each agent names exactly one profile as its default loadout. When you run twagent apply --global, the agent's global_profile is resolved (including all extends chains) and the resulting artifacts are deployed to the agent's paths.global.* locations.
• --select is polymorphic (profile or artifact names, mixed) and exhaustive (only kinds in the selection deploy).

How global_profile works

[agents.copilot-cli]
global_profile = "tw-copilot"   # ← this is the default loadout

[profiles.tw-copilot]
extends      = ["core", "pr_review", "web_research"]
instructions = ["AGENT-md"]

[profiles.core]
skills = ["bkmr-memory", "twmux", "skill-creator", "tw-comprehend"]

[profiles.pr_review]
skills = ["tw-review", "tw-add-pr-review", "tw-check-pr"]

Running twagent apply --global resolves the full extends tree and deploys all referenced skills, instructions, and servers to the agent's global paths. Each agent can have a different global_profile, so Claude, Copilot, and Pi can share profiles (via extends) while each carrying a distinct default set.

Without a global_profile, apply --global skips that agent entirely — it only deploys agents that declare one.

Install

uv tool install twagent
# or, from a clone:
make install

Python 3.13+. Optional: fzf >= 0.35 improves the --interactive picker.

First deploy

twagent edit --init                # bootstrap a commented starter config
$EDITOR ~/.config/twagent/config.toml
twagent apply --global -n          # preview
twagent apply --global             # deploy

→ Full walkthrough: Quick Start (10 min) and Tutorial (30 min, two-agent setup).

Documentation

Develop

uv sync
make test
make format
make lint
make build

License

BSD-3-Clause.