Docs › Troubleshooting › Chat panel problems

Chat panel problems

Fix a blank or crashed chat panel, a run that seems stuck, messages that did not send, and attachments that did not attach.

On this page

How the panel works is on The chat panel. Problems with the agent's work itself are on Agent run problems.

The chat panel is blank

The panel is empty, or shows Error loading webview: Could not register service worker.

Cause: the editor's web view cache is stale, usually after an update, or after AstraCode was once started with sudo.

  1. Run AstraCode: Repair the Chat Panel from the command palette.
  2. It asks Clear the editor's webview cache and reload? and names the two cache folders it deletes. Your chats, settings and extensions are not touched. Choose Clear and reload.
  3. If it says some cache files could not be deleted, they are owned by root. Quit AstraCode, run the sudo rm -rf lines it shows in a terminal, and open AstraCode again.

The chat panel hit an error

The panel shows The chat panel hit an error. Your conversation is safe: it is kept by the editor, not by the view.

  1. Choose Try again.
  2. If it comes back, choose New chat. Your past chats are still in history.
  3. If that fails too, run Developer: Reload Window.
  4. Report it with AstraCode: Report a Problem. Details for a report on the error shows the technical message.

AstraCode Settings is blank after a restart

  1. Close the AstraCode Settings tab.
  2. Open it again with AstraCode: Open Settings.

The send button says Log in

The button reads Log in, or sending shows Sign in to AstraCode to send this.

  1. Press Log in, or run AstraCode: Sign In.
  2. Approve in the browser. If that fails, see Sign-in problems.

A message you sent shows as Queued

The message sits at the foot of the chat marked Queued, with sends when the agent finishes.

Cause: a message sent while the agent is working waits for the run to end. That is the default, astracode.agent.sendDuringRun set to queue.

A run seems stuck

Nothing seems to be happening, and the run has not ended.

Cause: almost always, the agent is waiting for you. Approval cards and question cards have no timeout.

  1. Scroll to the bottom of the chat and look for an approval card (Approve, Deny) or a question card (Continue, Skip).
  2. If the chat is not on screen, the editor shows a notification that the chat has a question for you. Choose Show.
  3. Check other chat tabs: a chat with a pending question shows Waiting for you in history.
  4. A command can also be running for a long time. Its card says Still running; choose Move to background (or press Ctrl+B) to let the agent carry on.
  5. If nothing is waiting, press Stop and send the message again.

Stop does not stop straight away

The button shows Stopping the agent and stays disabled for a while.

Cause: the run is finishing the step it is in, such as a command that is being ended. The button resets when it has.

  1. Wait for the button to turn back into Send.
  2. If it never does, run Developer: Reload Window. The chat is kept.

Lost the connection to AstraCode

The chat shows Lost the connection to AstraCode. Trying again until it is back; nothing is lost.

Cause: the network dropped during a run. The run waits and carries on when the connection returns.

  1. Check your connection, VPN or proxy.
  2. Leave the run alone; it resumes by itself. If you need to, press Stop and send the message again once you are back online.

This conversation is too long for the model

Cause: the conversation and its attachments no longer fit in what the model can read. Sending the same message again will not help.

  1. Click the context ring next to Send and choose Compact session, or run AstraCode: Compact Session.
  2. Or detach some files, or start a new chat with New Chat.

Compacting can also answer with:

MessageWhat to do
Finish or stop the current run before compacting.Wait for the run, or stop it, then compact.
Nothing to compact yetThe conversation is still short; nothing needs doing.
Could not summarise the conversation. Nothing was changed.Try again, or start a new chat.
Could not shorten the conversation automaticallyStart a new chat, or try Compact session.
Sign in to summarise the conversation.Choose Sign In.

A dropped file did not attach

The panel shows That drop arrived with nothing attached to it. or That drop carried nothing that can be attached.

Cause: some systems block dragging from Finder or the file manager into a panel, or the file is a type that cannot be attached. Binary files are skipped; text files are cut at 20,000 characters.

  1. Drag the file from the editor's Explorer instead.
  2. Or choose +, then Add files or photos.
  3. Or right-click the file in the Explorer and choose Add to Chat.

Nothing to attach from the terminal yet

Cause: Add to Chat from the terminal, or @Terminal, needs a command that ran with shell integration on, or some selected output.

  1. Run a command in the terminal, with the editor's shell integration on.
  2. Or select the output you want, then press Cmd+L (Ctrl+L on Windows and Linux).

Open a file to add it, or a selection of it, to the chat. means no file was open when you used Add Selection to Chat.

Open the AstraCode chat first

Commands such as Export Transcript say Open the AstraCode chat first. or Open the AstraCode panel first.

  1. Press Cmd+Shift+I (Ctrl+Shift+I on Windows and Linux) to open the chat.
  2. Run the command again.

Stop the current run before rewinding

Cause: a chat cannot be rewound while it is running.

  1. Press Stop, or wait for the run to finish.
  2. Use Rewind to just before this message again.

A beforeSubmitPrompt hook stopped this message

Cause: one of your hooks, or a project's, refused the message.

  1. Open AstraCode Settings > Customize > Hooks and read the Execution log.
  2. Fix or remove the hook. See Hooks.

There is no model picker under the composer

Cause: this is expected. AstraOne chooses the model, and the picker appears only when you use your own provider key and the gateway answers with the models it can use. Hover where it would be for the reason.

Auto-Hide Editor When Empty does nothing

The editor warns that the setting needs the "Toggle Editor Area Visibility" command, which this build does not have. The setting stays off in that build; there is nothing to fix on your side.

← Install and update problems Agent run problems →

All documentation

Get started

Using the editor

Agent

Context

Workspaces

Connectors

Extending AstraCode

CLI

Account and usage

Troubleshooting

Reference