Something failed, ran slow, surprised you, or is missing. Bugs and requests are tracked in public at elide-dev/elide, and there are four ways to get one there.
| Path | Use it when | Start |
|---|---|---|
| Your coding agent | You work in Claude Code, Codex, Cursor or another MCP client. | Report from your agent |
| GitHub issue | You want to file and follow the issue yourself. | File a GitHub issue |
| Discord | You want help now, or aren’t sure it’s a bug. | elide.dev/discord |
| Security advisory | The problem is a vulnerability. | Report it privately |
Report from your agent
This docs site is also a public MCP server. Connect it once and your agent can search these docs, and it can write: file a bug, send a performance report, record a missed expectation or ask for a feature, each as a public issue in elide-dev/elide. Nothing is sent until you have seen it and said yes.
claude mcp add --transport http elide-docs https://elide.help/mcp
codex mcp add elide-docs --url https://elide.help/mcp
Then say what went wrong:
elide test hangs after the last test passes. Report it to Elide.
The agent checks for an existing issue, gathers evidence with elide agent, and shows you a preview with secrets,
home paths, email and IP addresses removed. You confirm once. The report joins a queue that an hourly job turns into a
public issue, and report_status tells your agent when it lands.
The server also asks your agent to keep watch while you work: a failure, a slow run or a surprise earns an offer to report it.
- Report from your agent: report kinds, the confirm step, evidence and what is stored.
- From report to fix: the queue, the hourly triage, labels, and how to follow a report.
File a GitHub issue
elide agent bug prints an issue body with your Elide version and platform filled in. It sends nothing.
elide agent bug
File this report at https://github.com/elide-dev/elide/issues
Or send it through the docs MCP server at https://elide.help/mcp
---
### What happened
<!-- the command you ran, what you expected, what occurred -->
### Environment
| key | value |
| --- | --- |
| version | 1.6.3 |
| platform | linux-amd64 |
…
Open a new issue, paste the body, and fill in what happened.
Include what fits the problem:
| Problem | Include |
|---|---|
| Error or crash | The command, its full output, and the newest file in crash_root if one was written. |
| Wrong result | What you expected, what you got, and why: a docs page or another runtime’s output. |
| Slow run | elide agent perf timings against the runtime or Elide version you compared with. |
| Missing feature | What you would build with it. |
elide agent diagnostics prints your version, platform and crash-report directory (crash_root). Attach the
smallest project or file that reproduces the problem.
elide agent diagnostics
elide agent perf --baseline "node app.ts" -- elide run app.ts
elide agent perf --against 1.6.2 -- elide run app.ts
--against runs an Elide version you already have installed; it never downloads one.
Security vulnerabilities
Report a vulnerability privately through GitHub security advisories. Don’t open a public issue, post on Discord, or send it through the docs MCP server, which files public issues.
Before you report
- Troubleshooting covers common errors with their fixes.
- Compatibility and the API overview list what Elide does not support.
- Check that
elide --versionis the latest release; see Upgrading. - A wrong or missing docs page is a report too: an
expectationwith the page as its basis is labelledsite:docs. Was this page helpful? at the end of each page records your vote and comment; it does not open an issue.