Settings
Integrations & extensions
Issue trackers, automations, skills, MCP servers, and remote hosts.
The Extensions group connects Operon to the tools and machines around it — your issue trackers, scheduled workflows, reusable agent skills, MCP servers, and remote hosts. Every extension here is opt-in: nothing reaches outside your machine until you connect it, and credentials go to your operating system keychain rather than into Operon’s database or the cloud.
Integrations
Integrations connect Operon to four issue trackers: Linear, GitHub, Jira, and GitLab. Once connected, you can import an issue when starting a session so the goal is scaffolded from the ticket, and Operon can optionally post the outcome back when the session finishes.
You connect a source by adding an account with an access token. Tokens are stored in your OS keychain — never in SQLite and never synced. Some sources need an extra detail: GitHub takes the repositories to watch, Jira takes your site URL, and GitLab optionally takes a self-managed host (leave it blank for gitlab.com).
Connect an integration
- 1
Open Integrations
In Settings, choose Integrations. You will see a card for each source — Linear, GitHub, Jira, and GitLab.
- 2
Add an account
Click Add account on the source you want. Use the token link in the dialog to generate a personal access token in that provider, then paste it in along with a label.
- 3
Fill in any extra detail
Provide the workspace field if the source asks for one — GitHub repositories, a Jira site URL, or an optional self-managed GitLab host.
- 4
Connect
Click Connect. The token lands in your keychain and the account appears under the source, ready to import issues from.
Writeback
Writeback is the optional half of an integration: when a session that is linked to an issue finishes, Operon can post a comment summarizing the outcome and, if you want, transition the issue’s status. For GitHub and GitLab, which have no named workflow states, transition means closing the issue; for Linear and Jira you name the target state, such as In Review.
Note
Writeback is OFF by default, per source. Operon never posts anything to your issue tracker unless you explicitly turn on Comment or the transition toggle for that source. A per-session skip is also available in the finish dialog, so you can opt out of writeback for a single session even when it is enabled.
Automations
Automations run work for you on a schedule, from a template, or in response to a trigger. An automation pairs a trigger — a cron schedule, a manual button, a session event, or an inbound webhook — with an action, such as running a script or posting to a service. GitHub and Linear webhooks are verified by signature before they fire anything.
You can start from the built-in catalog of starter templates, which cover the common trigger-and-action pairings, or build one from scratch in the create dialog. Webhook URLs are restricted to HTTPS unless you deliberately opt in to localhost.
Skills
Skills are reusable capability packs you install into your agent profiles. The Skills section lets you install a skill, see what is installed, and manage updates: Operon checks for new versions on launch, shows you what changed before you accept an update, lets you pin a skill to a version, and keeps a short history so you can roll back. A badge in the navigation flags when updates are waiting.
MCP Hub
The MCP Hub solves a chore: instead of configuring an MCP server separately for every agent, you install it once here and Operon writes the translated configuration into each compatible agent’s file for you — Claude Code, Cursor, Gemini, and Aider. Your own hand-authored entries are left untouched, and a backup of each file is taken before the first managed write.
Tip
Backups of agent config files land under ~/.operon/config-backups before Operon makes its first managed change, so you can always revert.
The MCP Hub is distinct from the MCP Server section under System — the Hub installs servers into your agents, while MCP Server exposes Operon’s own data to MCP clients. See the System & data guide for that side.
SSH Hosts
SSH Hosts is the address book for remote sessions. Add a host here — its connection details and credentials — and Operon can run a session on that remote machine, streaming its terminal into the app exactly as a local session. Credentials are stored securely, and the host key is pinned on first connect so a changed key is flagged rather than silently trusted.