Solo lets you add the same agent CLI more than once, each time with a different name and set of default arguments. Think of these as reusable launch presets: one installed tool, several useful ways to start it.
This is handy when you regularly switch models, reasoning levels, permission modes, or other CLI flags. Instead of remembering and retyping those flags, give the configuration a name and pick it like any other agent.
Add a named agent
- Open Settings → Agents.
- In Agent tools, click Add tool.
- Enter a unique Name. This is the name Solo shows when you launch the agent.
- Enter the CLI in Command, such as
codex. - Put the flags you always want in Default arguments.
- Leave Tool type mode set to Auto detect when Solo recognizes the command, then save the tool.
The new entry uses the same installed CLI, login, and configuration as the original. It does not install another copy of the tool or create a separate account.
Example: Codex Smart
Suppose you want a named Codex option for harder work where you want the model to spend more effort reasoning. Add a tool with these values:
| Field | Value |
|---|---|
| Name | Codex Smart |
| Command | codex |
| Default arguments | --model gpt-5.6-sol -c model_reasoning_effort=xhigh |
| Tool type mode | Auto detect |
Solo will now offer Codex Smart as its own agent choice. Launching it runs:
codex --model gpt-5.6-sol -c model_reasoning_effort=xhighYou could keep the built-in Codex entry for normal work and choose Codex Smart when a task needs the heavier configuration. You can also add another uniquely named Codex entry with different default arguments for quick fixes, reviews, read-only work, or any other setup you use often.
The flags belong to the underlying CLI, not Solo, so check the tool's --help output before saving a preset. Solo simply appends Default arguments to the command when it launches the agent.
Named agent or Agent with flags?
Use a named agent when you expect to reuse the same configuration. It stays in Solo's agent picker and saves you from rebuilding the command each time.
Use Agent with flags when you only need to change the command for one launch. Solo pre-fills the tool's normal command and default arguments, then lets you edit the full command before starting. See Launching agents for the complete launch flow.
If auto-detection gets it wrong
Solo recognizes commands such as codex automatically. If your Command points to an alias or wrapper script instead, edit the tool, change Tool type mode to Set manually, and choose the underlying tool type. This preserves tool-specific behavior even when the command name is custom.
After adding a tool, click Refresh health to confirm Solo can find it. If the command works in your terminal but not in Solo, see Agent installation health and Shell environment loading.