Troubleshooting

1. The Inline Composer Does Not Appear

Check:

• whether the page is http:// or https://
• whether the extension was refreshed in chrome://extensions
• whether the content script loaded successfully on that page

If you updated extension code, rebuild first:

npm run build:extension

Then refresh the unpacked extension.

2. Cmd/Ctrl + U Does Nothing

Possible causes:

• the content script did not inject successfully
• focus is currently inside an input/editor/contenteditable region
• the browser is still using an old unpacked build

Try again on a normal page after refreshing the extension.

3. Cmd/Ctrl + Enter Does Not Send

Check that:

• the inline composer is already open
• the input actually contains text
• Agent and Chat are selected correctly
• Console and Agent are running

If the page script failed to load, send shortcuts will not register either.

4. No Available Agent

This usually means:

• city agent start is not running
• the Console address is wrong
• the current Agent is offline

If you see:

• Missing bearer token
• Invalid bearer token
• Permission denied

that usually means unified auth is enabled in Console, but the extension does not have a valid token yet.

Fix it by:

1. opening the extension settings page
2. running city token create my-token in the local terminal
3. pasting the token into extension settings
4. clicking Refresh Agent

5. No Available Chat

The extension does not invent a chat context.

This usually means:

• that channel has not received messages yet
• the current Agent has no connected chat channels
• you have not selected a target Chat yet

6. The Captured Body Looks Wrong

Full-page capture is best-effort, not a perfect browser-reader clone.

The current logic:

• prefers the most article-like main/article root
• filters nav, sidebars, and hidden content
• merges multiple strong content roots when needed

Very custom page layouts can still confuse the extractor.