Docs › Account and usage › Reporting a problem and getting help

Reporting a problem and getting help

Report a problem from the editor, send a run to the team, find the logs, and contact support.

On this page

The fastest way to get something fixed is to report it from the editor, at the moment it goes wrong: the report carries the diagnostics that identify most problems, and you see all of it before it is sent. Before that, the troubleshooting pages list every message you might see, with its fix.

Report a Problem

You can start a report from several places:

  1. Start a report from any of the places above. If you are signed out, the editor asks you to sign in first, so we can tell you when it is fixed.
  2. The editor writes up what happened from its log (Writing up what happened). Edit the one-line summary if anything is wrong, or write your own: What went wrong? One line.
  3. Add anything else worth knowing in the next box. It is optional.
  4. The review window, Send this to AstraCode support?, shows the whole report, diagnostics included. Choose Attach a screenshot or recording to add an image (png, jpg, gif, webp or bmp) or a video (mp4, mov, webm or m4v).
  5. Choose Send. If your description looks like it contains something private, the editor says so and asks before sending anyway.
  6. The editor says Reported as ticket with its number. You are asked to confirm when there is a fix.

What a report contains, and what it never contains, is listed in What AstraCode sends and keeps.

If the report does not send

MessageWhat to do
Your AstraCode session has expired. Sign in again and the report will go through.Run AstraCode: Sign In, then send it again.
That attachment is too large to send.Attach a screenshot rather than a recording.
The report was rejected as incomplete. A one-line summary is required.Fill in the one-line summary.
Could not reach AstraCode. The report has not been sentSend it again when you are back online.
AstraCode could not accept the report just now.Nothing was lost; try again shortly.
A proxy or firewall on your network blocked the report.Nothing was sent. Try again from another network.
Something on your network answered instead of AstraCodeA captive portal or proxy answered. Sign in to the network, or use another one.

If a report cannot be sent at all, describe the problem on the contact page instead.

Send this run to the AstraCode team

When a run did something wrong and the details matter, send the run itself. It shows the team exactly what was asked, what the agent did and what it changed.

  1. On the run's summary card, rate it, then choose Send this run to the AstraCode team.
  2. A read-only preview opens beside the chat with everything that would be sent: your request, the agent's reply, its own check, and the diffs of the changed files, with secrets removed.
  3. Read it, then confirm in Send this run to the AstraCode team?
  4. The editor says Sent. Thank you: we read every one. and the date it will be deleted.

Logs

AstraCode writes three logs, each an output channel in the editor's Output panel. They are the first thing to read when something is not working, and what support will ask about.

LogWhat is in itHow to open it
AstraCode AgentAgent runs, requests, errors and the chat panelAstraCode: Show Agent Log, or Agent log in the chat's More menu
AstraCode MCPConnectors, sign-in to connectors, updates and first-run setupAstraCode: MCP: Show Connection Log, or Connection log in AstraCode Settings > Customize > MCP servers
AstraCode HooksEach hook that ran, its exit code and outputOpen the Output panel (View: Toggle Output) and choose AstraCode Hooks in its list. It appears after the first hook runs. AstraCode Settings > Customize > Hooks also has an Execution log.

Before you paste a log anywhere, read it: it can contain file paths and command lines from your project.

Contact support

← What AstraCode sends and keeps Troubleshooting →

All documentation

Get started

Using the editor

Agent

Context

Workspaces

Connectors

Extending AstraCode

CLI

Account and usage

Troubleshooting

Reference