Cursor
Route Cursor's Agent through MarkDB.
Cursor can use any OpenAI-compatible endpoint as a custom model provider. Point it at the MarkDB proxy and every Agent conversation is captured.
Configure
In Cursor settings, add a custom OpenAI-compatible model with:
- Base URL:
https://proxy.markdb.cloud/v1 - API key: your
mk_live_...key - Model: any model MarkDB is configured for, e.g.
gemini-2.5-flash
Cursor sends standard /v1/chat/completions traffic, which MarkDB captures and
dispatches natively to the underlying provider.
Chat continuity
Cursor replays the full conversation on every request and rotates its session id each time. MarkDB derives a stable chat key from the opening messages, so a long Cursor chat stays a single session instead of fragmenting -- and repeated history is de-duplicated rather than re-stored.
Verify
Start a chat in Cursor, then open the Work log. You should see one session for the conversation, with user and assistant turns captured as you go.