Getting Started
Install
The fastest way to install Symposium is with cargo binstall:
cargo binstall symposium
If you prefer to build from source, use cargo install instead:
cargo install symposium
On Arch Linux, install the symposium package from the official repositories:
pacman -S symposium
Installing gives you the symposium command. cargo agents is the same command under its cargo subcommand name: it accepts the same subcommands and behaves the same way, so symposium init and cargo agents init are interchangeable. This guide uses symposium.
Initialization
Once you have installed Symposium, you need to run the init command:
symposium init
Your agents
This will prompt you to select the agents you use (Antigravity, Claude Code, Copilot, etc.). The ones Symposium finds installed, recognized by their config directory such as ~/.claude or ~/.codex, are already checked, so usually you just press Enter:
ℹ️ Detected: Codex CLI, Kiro
Which agents do you use? (space to select, enter to confirm):
> [ ] Antigravity CLI
[ ] Claude Code
[x] Codex CLI
[ ] GitHub Copilot
[ ] Goose
[x] Kiro
[ ] OpenCode
After installing or uninstalling an agent, rerun symposium init: the list reflects the change, so you just confirm. You can also run symposium init --add-agent <name> or --remove-agent <name>.
Global vs project hook registration
Next, Symposium will ask you whether you want to register hooks globally or per-project:
- global registration means Symposium will activate automatically for all Rust projects.
- project registration means Symposium only activates in projects once you run
symposium syncto add hooks to that project.
We recommend global registration for maximum convenience.
Tweaking other settings
You may wish to browse the configuration page to learn about other settings, such as how to disable auto-sync.
After setup
Symposium will now install skills, MCP servers, and other extensions based on your dependencies automatically.
Most plugins come from two places: the central recommendations repository, which is enabled by default, and crates your project depends on directly that ship their own. A dependency’s plugin stays off until you enable it: an interactive symposium sync asks about each one, and symposium status lists the ones waiting for an answer. If you have a crate and would like to add a plugin for it to symposium, see the Supporting your crate page.
If you have private crates or would like to install plugins for your own use, you can consider adding a custom plugin source.