Crash Override Endpoint
Prompt to production provenance.
Crash Override Endpoint is the developer-machine surface of the data plane.
We watch the agents. We are not one of them.
Endpoint runs on the developer's machine and observes AI-assisted engineering: which AI coding tools are used (Claude Code, Cursor, Copilot, Codex, Devin), what they were asked to do, what they produced, and how that work moves into the build and out to production. Everything it observes lands in the same provenance graph as Chalk's build and runtime data. Chalk is the data plane; Endpoint extends it to the machine.
Action-level detail, not a summary.
Observed on the machine, deterministically. No model sits in the data path guessing about your code.
- Sessions
- For transcript-backed tools such as Claude Code and Codex: the prompts and responses themselves, tied to the user, the files, the tools and the network activity around them.
- Actions
- Tool calls, denied tool use, shell execution with exit codes, and file create, modify and delete.
- MCP
- First-class visibility into Model Context Protocol activity: server starts, tool calls and references.
- Network
- External calls the agent initiates: DNS, URLs, methods, status codes and provider routes.
- Attribution
- Agent-to-source and engineer-to-source attribution, with provider, model and session identity.
- Timeline
- A session-level unified timeline joining AI activity to source change, build, deploy and runtime.
Zero-touch through your MDM, or one machine at a time.
Endpoint ships zero-touch through the MDM you already run. There is no developer opt-in, no IDE plugin, no Dockerfile change and no CI configuration, so coverage does not depend on every team remembering to instrument every repo.
-
Zero-touch rollout
Deployed through your existing MDM. No developer opt-in required.
-
MDM optional
MDM is the easy path, not a requirement. You can install Endpoint on a single machine from this page.
-
Generally available
Apple Silicon Macs on macOS Tahoe 26.0 or later. Windows and Linux are coming soon.
-
Optional for Chalk
Chalk works without Endpoint. Endpoint extends the same thread left, to the machine where the code is now written.
Session timeline
Prompt to commit, in one thread
- E004 Prompt fix the payment retry logic
- E009 Plan 3 steps proposed · accepted
- E012 Read payments/retry.ts · 412 lines
- E018 Edit payments/retry.ts · +12 −4
- E024 Shell test suite · exit 0 · 124 passed
- E031 Commit signed · queued for build
Action-level audit
What the agent actually did
- A017 server.start issue-tracker
- A019 tool.call search_issues
- A023 tool.call read_file
- A026 tool.call write_file denied
- A031 reference spec/retry-policy
Before you install.
Endpoint is generally available on Apple Silicon Macs running macOS Tahoe 26.0 or later. Windows and Linux are coming soon.
No. MDM is the easiest way to roll Endpoint out across a fleet with no developer opt-in, but it is not required: you can install it on a single machine from this page.
Everything Endpoint observes lands in the same provenance graph as Chalk's build and runtime data. It records what AI coding tools did (prompts, tool calls, file changes, commits), not what the human typed outside that context, and it captures no keystrokes or screen content outside the coding context.