Find the decision behind the code.

Code shows what was built. The reasons sit in design docs, issues and long threads. Neutron answers from those sources with citations, and engineers can ask in the askneutron app or from Codex and Claude over MCP without leaving their editor or terminal.

Get started free Talk to sales

Sample answer · a fictional company

What's still blocking the v2.4 release?

Two blockers left: the billing migration and the iOS launch crash.

Answered from

  • Linear · v2.4 cycle
  • #release-v2-4
Only sources this person can open

The questions engineers ask every day.

Questions Neutron can answer once the right sources are connected, and where each answer comes from.

Why did we move session storage off Redis?

From the design doc and the issue where it was decided.

What is still blocking the v2.4 release?

From synced Linear or Jira issues and the release channel.

How do I run the billing service locally?

From your developer setup guide.

Who owns the payments webhook, and where is its runbook?

From your service ownership list and on-call docs.

What is our policy on adding a new third-party dependency?

From your engineering standards document.

Has anyone seen this timeout in the search worker before?

From past issues and the Slack threads you can see.

What changed in the public API in the last release?

From release notes and your docs site.

What is the escalation path for a database incident?

From your incident response runbook.

Docs, issues and threads in one place.

Upload design docs, decision records and runbooks, or crawl your internal docs site and public API reference on a schedule.

In preview, Linear and Jira sync issues and comments, Slack syncs channel history, and Google Drive syncs design docs. These sources sync into the knowledge base; live lookups and changes in those tools are not available yet. Linear syncs public teams only, and connectors for Notion and Confluence are coming soon.

  • Design docs, decision records and runbooks
  • Docs sites and API references, crawled on a schedule
  • Linear, Jira, Slack and Drive, in preview
Documents, sites, and tools connect to askneutron The askneutron mark sits on a raised central surface. Short connections join it to app, document, API, and database symbols, showing company systems connected in one place.

Ask from your editor or terminal.

Connect the askneutron MCP server to Codex, Claude or another MCP client. Your coding agent can search company knowledge with your access, so it can check the design doc or the team’s decision before it changes code.

Engineers who prefer chat use the askneutron app, and platform teams can build search into internal tools with the hosted API.

  • MCP for Codex, Claude and other clients
  • The askneutron app for chat
  • The hosted API for your own internal tools
Set up MCP
How engineering teams use askneutron A plug connects to symbols for knowledge, workflow tools, and an organization. It represents ways to connect the assistant to other systems.

Your access, nothing more.

MCP and the API follow the same rules as the app. An engineer gets answers only from sources they may read. Private Slack channels stay with their members, Jira project permissions carry over, and private Linear teams are not synced.

Neutron does not change code or issues. Any change an agent prepares waits for a person’s yes before it runs.

  • Each MCP connection uses the person’s own account
  • Jira and Slack access rules carry over
  • Private Linear teams stay out
How confirmations work
A shield covers documents to show access controls A shield with a check mark covers layered document surfaces. It represents access controls for company knowledge.

Engineering questions.

All questions

All integrations

One knowledge base, an agent for each team.

All use cases

Give your coding agent the context.

Get started free Talk to sales