Presets
Save agent launch settings or SSH connection choices for later use.
Why use a preset?
An agent preset records the agent, command flags, environment values, and restart policy you want to reuse. It can also provide a machine, working directory, and initial prompts. For example, a repository-review preset can launch Codex in your project with review instructions and explicit approval settings.
Open Settings → Presets in the dashboard sidebar and choose Agent or SSH. Agent presets are grouped by agent. SSH presets list their destination, connecting node, and authentication choice. The New preset menu offers New agent preset and New SSH preset from either tab. See Connect over SSH to create and use an SSH preset.
Presets are private to your account until you share them. You can share agent and SSH presets with individual people or everyone signed in to the instance. Saving an agent preset doesn't install or authenticate the agent CLI; those steps happen on the machine where the session runs.
Choose a guide
- Create a preset saves a coding-agent configuration.
- Set launch defaults adds a machine, directory, and task text.
- Use and manage presets covers launches, edits, cloning, and agent-created helpers.
For the task text itself, use Reusable Prompts. A reusable prompt stores instructions; a preset stores how and where an agent starts.
What a preset changes
Saving a preset changes future launches that use it. It doesn't reconfigure a running process. Human launch forms prefill the saved defaults and let you review or override them.
For an existing subshell, follow Clone and switch presets to start with different settings.

Last updated on
