# Agents Once JetBrains Central CLI is installed and you are logged in, you connect the agents you want to use. From then on you keep launching each agent the way you always have, and JetBrains Central CLI routes its requests through JetBrains Central. This page covers connecting and disconnecting agents, checking your usage, and seeing which agents you are allowed to use. ## Connect an agent There are two ways to connect an agent, and you can mix them freely: * Permanent connection * One-off run | | Permanent connection | One-off run | | --- | --- | --- | | Command | `central add ` | `central run ` | | Agent configuration | Modified, with a backup made first | Left untouched | | Applies to | Every future launch of the agent | That one session only | | Undo | `central remove ` | Nothing to undo | | Best for | Day-to-day use | Trying it out, or keeping a direct-provider setup alongside | ### Connect permanently (Wire) A permanent connection updates the agent's own configuration file, so every launch from then on is routed for you: Claude Agent: ```BASH central add claude ``` Codex: ```BASH central add codex ``` Gemini CLI: ```BASH central add gemini ``` Junie CLI: ```BASH central add junie ``` Pi: ```BASH central add pi ``` Procedure: Connect an agent from the interactive interface 1. Run `central`. 2. Select Wire agents, then pick the agent. If only one agent is installed, the menu offers it directly (for example, Wire Claude Agent). The change is a narrow one. JetBrains Central CLI adds only the settings the agent needs to reach the proxy and leaves everything else in the file as it was. If the agent already has a configuration file, a timestamped copy is saved next to it first, so you can see what the file looked like before: ```TEXT ~/.claude/settings.backup.2025-02-08T14-30-45.json ``` > **Note:** > Connecting an agent also sets it up to start the proxy on its own whenever a session begins, so you never have to start the proxy by hand. The agent does that by running `central proxy start`, which means `central` has to be on your `PATH`. If it is not, the agent cannot start the proxy, and running the same command yourself fails for the same reason — the fix in both cases is to put `central` on your `PATH` ([See instruction](troubleshooting.html#central-not-on-path)). ### Route a single session (One-off run) `central run` routes one session and writes nothing to the agent's configuration. The proxy starts automatically if it is not already running. Anything after `--` is passed straight to the agent: ```BASH central run codex -- "explain this code" ``` Because nothing is written to disk, an agent you have never connected keeps working exactly as before once the session ends. ## Use a connected agent Launch the agent the way you always have: Claude Agent: ```BASH claude "explain this code" ``` Codex: ```BASH codex "refactor this function" ``` Gemini CLI: ```BASH gemini "review this PR" ``` Junie CLI: ```BASH junie ``` Pi: ```BASH pi ``` Your usual model picker still works, and the models you had available before remain available. Requests are authenticated with your JetBrains Account and billed to your JetBrains AI subscription, so no vendor API key is involved. ## Disconnect an agent To undo a permanent connection and put the agent back the way it was: Claude Agent: ```BASH central remove claude ``` Codex: ```BASH central remove codex ``` Gemini CLI: ```BASH central remove gemini ``` Junie CLI: ```BASH central remove junie ``` Pi: ```BASH central remove pi ``` Procedure: Disconnect an agent from the interactive interface 1. Run `central`. 2. Select the reset entry for that agent — for example, Reset Claude Agent. Only the settings JetBrains Central CLI added are taken out. Proxy entries, hooks, and options you configured yourself are left in place, and the agent goes back to reaching its provider directly. > **Note:** > Disconnecting an agent does not uninstall it, and it does not sign you out. Your other connected agents keep working. ## Check your usage To see how much of your AI allowance you have used: ```BASH central limit ``` The command reports a usage limit when your access comes from a workspace seat, and a quota when it comes from a license. Either way the figures are in AI credits — how many you have used, how many remain, and the period they apply to. Procedure: Check your usage from the interactive interface 1. Run `central`. 2. Go to More... | Quota — or More... | Limit, since that entry is named after whichever of the two applies to you. ## Check the current state `central status` answers the three important questions: whether you are logged in, whether the proxy is running, and which agents are connected. ```BASH $ central status ⣿ Auth logged in (AI Pro) ⣿ Proxy running on :19516 ⣿ Agents Claude Agent, Codex ``` This is the first thing to run when an agent behaves unexpectedly — see [Troubleshooting](troubleshooting.html). ## See which agents you can use To list every supported agent along with its current state: ```BASH central agents ``` Agents you cannot currently use are dimmed, with the reason next to them: * Blocked by AI governance. Your organization's allow-list does not include this agent. It cannot be connected, and if it was connected before, it is disconnected automatically once it leaves the list. * Not supported with service accounts. The agent needs a personal account, so it is unavailable on a service-account session. * Not supported with the Bedrock protocol. The agent does not work with the protocol your organization has provisioned. Procedure: See the list from the interactive interface 1. Run `central`. 2. Go to More... | Supported agents. 3. Select an agent to open its documentation in your browser. There, each agent shows whether it is installed and whether it is connected, agents your session cannot use are grouped under Unsupported agents with the reason beside them, and blocked ones under Agents blocked by AI governance. An agent that is installed but blocked also appears on the main menu, dimmed and marked blocked, so you can see why it is not offered without opening the list. Blocked agents you have not installed are not shown there. > **Note:** > Allow-lists apply only when your AI access comes from a workspace. If your access comes from a license, every supported agent is available to you. ## Refresh the allow-list JetBrains Central CLI keeps a local copy of your organization's agent allow-list so it can tell you what you may use without asking the server every time. The copy is refreshed when you log in, when you switch AI access source, and about once an hour while the proxy is running — so in normal use it stays current on its own. If your administrator has just changed the policy and you do not want to wait, refresh it yourself: ```BASH central agents refresh ``` Procedure: Refresh from the interactive interface 1. Run `central`. 2. Go to More... | Supported agents | Refresh agent settings, which reports the result on the spot. The entry is offered only when your organization manages agent settings — on an unmanaged session there is no policy to fetch, so it is absent. A successful refresh updates the list immediately and disconnects any agent that is no longer allowed. If the refresh fails — for example, because you are offline — the previous list stays in force and nothing is disconnected. Run `central agents` afterwards to see the result. ## Review the request log JetBrains Central CLI keeps a local record of every request it forwards on behalf of an agent. To read it: ```BASH central log ``` An entry shows when the request was made, which agent made it, the platform path it reached, the HTTP method and status, and how long it took. Failed requests also carry the error message and a trace ID you can quote when you contact support. Prompts and responses are never recorded — the log holds metadata only, and it never leaves your machine. For the full list of recorded fields, see [Data collection](cli-data-collection.html). Procedure: Browse the log from the interactive interface 1. Run `central`. 2. Go to More... | AI Logs. There, `t` filters by time, `s` filters by success or error, `r` clears the filters, `R` reloads the data, `q` goes back to the menu, and the arrow keys page through the history. The files live in `~/.jetbrains-central/analytics/`. JetBrains Central CLI keeps the five most recent, at 1000 entries each, and drops the oldest as new ones are written. To clear the history, delete the directory — it is recreated with the next request: ```BASH rm -rf ~/.jetbrains-central/analytics ``` > **Note:** > This log covers what your agents sent. The proxy daemon keeps a separate log of its own activity, which is the one to look at when the proxy itself misbehaves — see [Troubleshooting](troubleshooting.html). ## See also ### Related [Commands](cli-commands.html) [Supported agents and features](cli-supported-agents-and-features.html) [Troubleshooting](troubleshooting.html)