Install and Connect

Prerequisites

Before using the extension, you will usually want these running:

city start
city start
city agent start

If you load the extension from this repo, build it first:

npm run build:extension

Load It in Chrome

1. Open chrome://extensions
2. Enable Developer mode
3. Click Load unpacked
4. Choose products/chrome-extension/dist

First-Time Configuration

The default extension target is:

• Host: 127.0.0.1
• Port: 5315

If your Console UI is elsewhere, open the extension settings page. The page is split into three parts:

• Connect Console: set Console Host and Port, then paste a Bearer token
• Inline Composer: choose the default mode, instant executor, instant model, and instant ACP agent
• Agent / Channel: choose the default Agent and default Channel Chat used by the popup

If you do not have a token yet, create one in the local terminal first:

city token create my-token

If you prefer the interactive flow, run:

city token

The flow can copy the newly issued token right away.

Then paste the returned value into Access Token.

After token save succeeds, the extension will attach Authorization: Bearer ... to later requests automatically.

How Inline Composer Modes Work

The inline composer supports two modes:

• Channel Mode: uses the default Agent / Channel Chat delivery path
• Instant Mode: runs a temporary session and returns the result directly on the page

Inside Instant Mode, you can choose one executor:

• Model Executor: runs against the selected Console model pool entry
• ACP Executor: runs against the selected ACP agent project

If the selected instant executor has no valid default target, the inline composer will ask you to go back to settings and complete that configuration first.

How Agent and Chat Selection Works

The extension first asks Console for the Agent list, then reads the available chat contexts for that Agent.

If no Chat is available, it usually means:

• that channel has no message history yet
• the Agent is not running
• the Console address is wrong

After Updating the Extension

Whenever extension code changes, rebuild it:

npm run build:extension

Then go back to chrome://extensions and press the refresh button for the unpacked extension.