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:
- The command palette: AstraCode: Report a Problem.
- Report this on a failure card in the chat.
- Report what went wrong in the status bar, with a bug icon, which appears for two minutes after something fails.
- Report at the foot of a reply, or on the popup when you select text in a reply.
- Right-click a selection in the editor and choose Report a Problem, or the Report a problem lens above a selection. The selection is used as the starting point of the report.
- 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.
- 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.
- Add anything else worth knowing in the next box. It is optional.
- 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).
- Choose Send. If your description looks like it contains something private, the editor says so and asks before sending anyway.
- 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
| Message | What 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 sent | Send 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 AstraCode | A 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.
- On the run's summary card, rate it, then choose Send this run to the AstraCode team.
- 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.
- Read it, then confirm in Send this run to the AstraCode team?
- The editor says Sent. Thank you: we read every one. and the date it will be deleted.
- It is kept for 30 days, only the founders can read it, you can delete it from your dashboard, and it is never used for training.
- Binary files, key files and anything over 2 MB are not sent.
- The editor holds the last 20 runs. An older one says This run is no longer held by the editor, so it cannot be sent. Use Report a Problem to describe it instead.
- There is an hourly limit: That is the most runs that can be sent in an hour.
- Signed out, it says Sign in to AstraCode to send a run.
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.
| Log | What is in it | How to open it |
|---|---|---|
| AstraCode Agent | Agent runs, requests, errors and the chat panel | AstraCode: Show Agent Log, or Agent log in the chat's More menu |
| AstraCode MCP | Connectors, sign-in to connectors, updates and first-run setup | AstraCode: MCP: Show Connection Log, or Connection log in AstraCode Settings > Customize > MCP servers |
| AstraCode Hooks | Each hook that ran, its exit code and output | Open 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
- The contact page reaches the team directly.
- Email: support@astracode.io.
- Say which version you run (Help: About in the command palette) and your platform, and include the ticket number if you already sent a report.
← What AstraCode sends and keeps Troubleshooting →
All documentation
Get started
Using the editor
- Tab completion
- Edit and ask about a selection
- Reviewing the agent's changes
- Git: commit messages, branch review and conflicts
- Dictation
- Layout, themes and the settings page
Agent
- Agent overview
- Agent, Plan, Ask and Debug
- Approvals and permissions
- Plan mode
- Debug mode
- Tools
- Browser tools
- How the agent checks its work
- Checkpoints and undo
- Running several agents at once
- Subagents and background tasks
- Remote agents in GitHub Actions
- Infrastructure as code
Context
Workspaces
Connectors
- Connectors (MCP servers)
- Connector configuration reference
- Use AstraCode from Claude, ChatGPT and other apps
Extending AstraCode
CLI
Account and usage
- Usage and limits
- Bring your own key
- What AstraCode sends and keeps
- Reporting a problem and getting help
Troubleshooting
- Troubleshooting
- Sign-in problems
- Install and update problems
- Chat panel problems
- Agent run problems
- Connector problems
- Dictation problems
- Usage, billing and network errors
- CLI problems