Vinktar for Codex

Error tracking in Codex

Add Vinktar to Codex and it sets error tracking up in your repo, then reads every error with what the user did right before it. Keep the Sentry SDK you already run, or let it add one.

Start free Set it up

Free up to 50,000 errors a month. No card.

Breadcrumbs· 4

What the browser did in the seconds before the error

ui.clicka.nav-reports[href="/app/reports/revenue"]01:44:29
navigation/app/reports → /app/reports/revenue01:44:30
xhrGET /api/workspaces/current status=200 duration_ms=5001:44:31
xhrGET /api/reports/revenue?period=2026-09 status=200 duration_ms=15101:44:32
errorError captured01:44:43

What it does

From the first error to the fix, without leaving Codex

01 · Set up

Your agent sets it up

Codex reads your repo, adds the SDK for your stack, fetches the project’s write key over the connection and checks that the first error arrives. You approve one sign-in in the browser and paste no key.

Every tool the agent can use

Connect web

Next.js, keeping the Sentry SDK

Step 1, done: The Sentry SDK points at Vinktar
SENTRY_DSN changed, nothing else
Step 2, done: First error arrived
A test exception from production
Step 3, done: Release and environment tagged
web@2.36.0, production
Step 4: Waiting for a signed-in user
Set the user id so errors join to the people they hit

02 · Understand

Each error comes with what the user did right before

Every error keeps the clicks, requests and page changes that led to it, and Codex gets them with the stack trace and the release. Add Vinktar’s SDK and the events you track from the same user sit beside them.

Open an issue in the live demo

Events before· 4

What this session sent in the 30 minutes before, newest firstOpen in Explore

12s beforereport_viewed/app/reports/revenue
1m 35s beforesearch_performed/app/reports
3m 10s beforedashboard_viewed/app/dashboards
4m 20s beforelog_in/login

03 · Switch

Keep the Sentry SDK you already run

Vinktar reads what the Sentry SDKs send. Point the DSN at Vinktar and your code stays as it is. Switching back is the same one-line change.

How to switch from Sentry

.env+1 −1

-SENTRY_DSN=https://abc123@o0.ingest.sentry.io/3
+SENTRY_DSN=https://vnk_pk_8f2c…@in.vinktar.com/12

Setup

Add Vinktar to Codex

Install the plugin

codex plugin marketplace add vinktarhq/agent
codex plugin add vinktar@vinktar

2
Sign in
Your browser opens Vinktar: sign in or make a free account, then approve.
```
codex mcp login vinktar
```
3
Let it set Vinktar up
It reads your repo, adds the SDK for your stack or points the Sentry SDK you have at Vinktar, and checks that a first error arrives.
```
Set up Vinktar in this project
```

Ask

What broke after the last deploy, and what was the user doing?

Questions

What people ask first

Can I add the server without the plugin?

Yes. Add [mcp_servers.vinktar] with url = "https://mcp.vinktar.com/mcp" to ~/.codex/config.toml and run codex mcp login vinktar. The plugin adds the setup skill on top, so Codex knows the steps without fetching them first.

Do I have to remove Sentry?

No. Point the DSN of the Sentry SDK you already run at Vinktar and keep your code. If you change your mind, point it back.

What does my agent see about the user?

With only the Sentry SDK, the breadcrumbs it records: clicks, requests and page changes before the error. With Vinktar’s SDK as well, the product events from the same user, once both name the user with the same id.

Can an error message steer my agent?

Anyone who has your public write key can send an error, as with any error tracker. Vinktar hands captured text to your agent marked as data, inside a boundary the text cannot fake, with each message on one line. You can also connect with read access only. Read how it is handled.

What does it cost?

Free up to 50,000 errors a month. Starter is $29 a month for 150,000. Your agent does the fixing, so nothing is charged per fix. See pricing.

Ask your agent what broke

Set Vinktar up from Codex in a few minutes, and get the user’s steps with every error.

Start free Set it up