Troubleshooting

1. Cannot Reach the Server

Check:

• whether Protocol is correct
• whether Host and Port are correct
• whether Base Path is correct
• whether the target Server is actually running
• whether the browser can reach that address

If you just updated the extension code, rebuild first:

npm run build:extension

Then refresh the unpacked extension.

2. The Current Connection Requires a Token

If you see:

• Missing bearer token
• Invalid bearer token
• Permission denied

the target Server usually requires unified auth, but the current connection does not have a valid token yet.

Fix it by:

1. opening the extension settings page
2. selecting the matching connection
3. running studio token create my-token in the local terminal
4. pasting the token into settings and saving

3. The Remote Service Is Not Exposed Publicly

If you are targeting a remote machine, also confirm that the Console is not only bound to loopback.

From the studio CLI code:

• without --host or --public, Console stays in local mode on 127.0.0.1
• with --public, it binds to 0.0.0.0

Typical commands:

studio start --public

or:

studio console start --public

If you want that public binding to persist across later restarts, use:

studio public on

4. No Available Agent

This usually means:

• studio agent start is not running
• the connection address is wrong
• the Agent is offline

5. No Available Session

The extension does not create Sessions by itself.

This usually means:

• that chat channel has no prior session history
• the current Agent has no connected chat channels
• the saved default Session is no longer valid and must be reselected

6. The Captured Body Looks Wrong

Full-page capture is best-effort, not a perfect reader-mode 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.