TURSIOPS Vs Code Companion
Set up once, then it runs quietly alongside your agent.
HOW IT WORKS
Set up once, then it runs quietly alongside your agent.
-
01 AUTH_FLOW
Sign in, once
Open the extension → sign in or sign up → you're sent to the website in your browser → after authenticating, you're sent straight back to VS Code, signed in. Same flow as Cursor or CodeRabbit.
-
02 API_KEY
Add your Gemini key
Paste in your own Gemini API key. Every refine, summary, and navigation from here on runs on that key — nothing else powers the model.
-
03 AGENT_PROMPT
Then you just code
You prompt your agent — IBM Bob, Antigravity, whatever you use — like always. Tursiops saves that prompt, refines it with Gemini into a short, clean version, and stores it.
-
04 RECALL_LOOP
Next prompt, full context back
Before your agent builds the next thing, Tursiops forces it to read the refined file first — so it works with everything it's already done, instead of the last message or two it actually remembers.
FEATURES
Four functions, one panel — each powered entirely by your own Gemini API key.
-
1. Prompt Memory
AI agents lose context after 2–3 prompts. Prompt Memory stops that: every prompt you give your agent is saved to a file, refined into a clean, concise version by Gemini, and your agent is forced to read that file before building the next thing — so it always has full context, not a fading memory of the last message or two.
-
2. Navigator
Move through your project's files — check something, compare a file, look something up — without disturbing your main agent's active session or context. Browsing never resets or interrupts the work in progress.
-
3. Change Summary
Every single prompt's changes are recorded, not just the ones that make it into a git commit. Ask for a summary anytime and get a plain-language account of what actually changed and why — without digging through diffs yourself.
-
4. MiniGit
Real commits usually bundle 2–3 prompts' worth of changes, so a bad AI edit inside that window isn't its own commit — you can't just revert it. MiniGit checkpoints every prompt's change in between commits, so if the AI does something you didn't want, you can retrieve that exact prompt's state back, even without a commit to roll back to.
SECURITY
Local by design — nothing leaves your machine unless you choose.
Sign-in doesn't give us your data
Authentication happens through your browser, the same pattern Cursor and CodeRabbit use — you sign in on the website, it redirects back to VS Code with just a confirmation. Tursiops never sees your website password; it only knows you're signed in.
Your Gemini key is yours alone
You generate it, you paste it in, and it's stored in VS Code's SecretStorage — backed by your OS's secure keychain, never written to source, settings, or logs. Every refine, summary, and navigation call runs on your key, not a shared one.
Secrets never reach Gemini
Before any file content is sent for refining or summarizing, Tursiops automatically excludes .env files and variants, private keys (id_rsa, id_ed25519), credentials.json, .netrc/.npmrc/.pypirc, and certificate/keystore files (.pem, .key, .p12, .pfx, .crt, .jks) — along with anything in node_modules.
Untrusted workspaces are locked down
Open a workspace VS Code hasn't marked as trusted, and Tursiops disables itself automatically — no file read, no prompt sent, no risk taken.
MiniGit snapshots stay local
Per-prompt checkpoints between commits are stored on your machine only — they're for your own rollback, never transmitted anywhere.
USER MANUAL
Set up once — then it runs alongside your normal coding, no habit changes required.
GETTING STARTED
-
1.
Install Tursiops from the VS Code Marketplace — it appears in your side panel.
-
2.
Sign in or sign up from the panel → you're redirected to the browser to authenticate → you're sent straight back to VS Code, signed in.
-
3.
Paste in your own Gemini API key when prompted. This key powers every refine, summary, and navigation call — nothing works without it.
YOUR DAILY FLOW — NOTHING CHANGES ABOUT HOW YOU CODE
Keep prompting your agent — IBM Bob, Antigravity, whatever you use — exactly as before. Tursiops runs quietly underneath: saving each prompt, refining it with Gemini, and feeding that context back to your agent before its next build. You don't have to do anything extra for this part.
USING THE FOUR FUNCTIONS
| FUNCTION | WHAT IT'S FOR | WHEN TO REACH FOR IT |
|---|---|---|
| Prompt Memory | See every prompt you've given, refined and organized, with a Remember/Forget switch | Check what context your agent is actually working from |
| Navigator | Browse and check files without disturbing your agent's active session | Looking something up mid-task without breaking flow |
| Change Summary | Plain-language summary of what changed after any prompt | Understand a change without reading the raw diff |
| MiniGit | Retrieve the state from any single prompt between commits | The agent made a change you didn't want, and it's not its own commit |