Plugins & marketplace

Your agent starts with your codebase. Most real work also runs through tools your team already uses — issue trackers, monitoring, databases, payments, docs. Plugins add those capabilities without wiring everything yourself: open the Marketplace, install what you need, connect the service once, then ask the agent in plain language.

Installing a plugin does not weaken security. Actions that reach external systems still follow the same approval rules as editing files or running commands.

What are plugins

A plugin is a ready-made extension for X4RGE, usually built around a service you already rely on — Linear, Datadog, Stripe, Notion, and many others. When you install one, you get:

A path for the agent to use that service (after you sign in under Tools & MCP)
Optional guidance so the agent follows sensible patterns for that integration

Think of plugins as apps for your agent: install what your workflow needs; leave the rest.

Plugins and connections

The Marketplace is where you find and install plugins. Tools & MCP is where you sign in and manage those connections. See MCP if you want detail on how linked services work once a plugin is installed.

What is the marketplace

The Marketplace is the in-app catalog inside X4RGE Desktop — like an app store for your agent. Each listing has a name, description, and logo so you can search by service or category and install with a few clicks.

Step	What you do
Browse	Open Marketplace and search (e.g. Linear, Datadog, Stripe)
Install	Add the plugin to your user or workspace
Connect	In Tools & MCP, sign in to the service when prompted
Use	Describe what you want in chat — the agent uses the integration when it fits the task

Your organization controls which listings appear. If something you need is missing, ask your admin — they may need to enable it for the team.

In practice

When you ask…	With the right plugin installed and connected
"Why is checkout failing in prod?"	The agent can pull recent errors from Sentry or Datadog instead of guessing from code alone
"File a bug for the team with repro steps"	The agent can create or update a ticket in Linear or Jira
"Look up this customer's subscription"	The agent can query Stripe or similar tools with your approval
"Follow our usual AWS deployment steps"	Bundled guidance helps the agent match patterns your team expects

Plugins extend what the agent can reach — they do not replace reading and editing code in your repo when that is what the task needs.

Why install plugins

Without plugins	With plugins installed
Paste logs, ticket text, or screenshots into chat	The agent can pull live data from the tools you connect
Manually file follow-up work after the agent helps	The agent can create tickets or issues when you ask
Rely on general knowledge about an integration	The agent can follow patterns bundled for that service

You still describe goals in plain language. Plugins remove the busywork of copying context in and out of chat.

What plugins add

What you get	In plain terms
Service connection	The agent can use an external app after you connect it in Tools & MCP
Skills	Best-practice hints so the agent uses that service the way experts would
Team rules (optional)	Conventions that keep answers aligned with how your org works

During a task, the agent picks up what is relevant. Calls that change data or touch production still pause for your approval in chat.

Examples in the catalog

Category	Services you may see
Project & issues	Linear, Atlassian, monday.com, Notion
Observability	Datadog, Sentry, Grafana, Elastic, PostHog
Cloud & data	AWS, Supabase, Firebase, Neon, Snowflake
Commerce	Stripe, Shopify, Chargebee
Identity & secrets	Clerk, 1Password
Developer platforms	Vercel, Cloudflare, Prisma, Semgrep, Sourcegraph

Open Marketplace in the app to see the full list your organization offers.

Install and use

Open Marketplace
In X4RGE Desktop, open Marketplace and search by service name or category.
Install
Install the plugin for your user or workspace. Some listings are restricted by org policy.
Connect the service
Go to Tools & MCP, select the integration, and complete sign-in or OAuth when prompted.
Use in chat
Describe what you want — mention the service when it helps: "Create a Linear issue for this bug" or "Check Datadog for checkout 5xx in the last hour."

After install, you do not configure low-level details for most marketplace listings. The agent uses plugin capabilities when they fit the task.

Name the service in your prompt

When several plugins are enabled, saying Linear, Datadog, or Notion helps the agent choose the right one on the first try.

Your organization

Who	What they control
You	Install allowed plugins, connect services in Tools & MCP, use them in agent sessions
Org admin	Choose which marketplace listings are available to the team
Platform	Maintains the curated catalog and quality of marketplace listings

Stay safe

Review before approving — Treat plugin connections like any third-party integration.
Use scoped credentials — Prefer OAuth or least-privilege access where offered.
Disconnect what you do not use — Remove unused connections from Tools & MCP.
Keep secrets out of chat — Never paste API keys or tokens into prompts.

See Agent security for org-wide policy and approval habits.

MCP

How linked services work after you install a plugin.

Tools

Built-in agent capabilities and when each action needs approval.

Agent security

Organization controls for integrations and sensitive operations.