Documentation

Using rinkata with Grok

Connect Grok to this project from Settings. About two minutes. Nothing to install.

Once connected, ask Grok for what's on Work, capture ideas, or update tickets, the same project you see on screen.

Using Grok inside Cursor? See Cursor. That path connects every model in Cursor, including Grok Bot. Use the steps below when you want a Grok-only paste into Grok Bot.

Step 1: Mint a key

In rinkata, click your name (top-right) → Settings.
Find API keys.
Type a name, anything that reminds you which machine it's for, like cursor grok. A name is required; skip it and Create key errors.
Click Create key.

rinkata shows the key and, underneath it, a Grok Bot (Cursor) card already filled in, your key and the address you signed in at.

Don't dismiss that panel until you've copied. The key is shown once. If you lose it, mint another.

Click Copy for Grok.

Step 2: Paste it to Grok

Open Grok Bot in Cursor and paste what you copied. Grok registers the connection for you.

Then keep going, Step 3 is not optional. A running Cursor holds the old connection.

Step 3: Reload and check

Reload Cursor's tools, or restart Cursor.
Ask Grok: "List my rinkata projects." You should get your workspace's projects back.
Then ask for one of them by name, "what's on Work for <your project>?"

Using it

Talk in plain language, "what's ready to start on <your project>?", "capture an idea called X", "what's on Needs attention?" Grok looks up the project by name.

You can read and change the same things you can on screen: Ideas, Work, Complete, decisions, and tickets.

If something's not working

What you see	Fix
Grok has no rinkata tools after setup	Reload Cursor's tools or restart Cursor. The list is read once at startup
"Not authenticated" / 401	The key is wrong or was revoked, mint a new one, paste Copy for Grok again, then restart
"Which project?"	Name the project, or ask Grok to list your rinkata projects first

Replacing your key

Mint a new key, click Copy for Grok, paste. The copied request replaces the existing connection rather than adding a second one.

A running Cursor keeps the old key. Reload tools or restart Cursor after you swap. This is the step people miss.

To cut a key off entirely, revoke it in Settings → API keys. That takes effect on rinkata's side immediately.