instibrain
Sign in
instibrain  /  works with

Your AI runs your systems, as you.

Your AI reads a tool's page, signs in as you, and fetches each key from your own store at use.

the rule every page shares

Your AI signs in as you and fetches each key from your vault when it uses it.

No connector of ours sits in between. Every page below says what to ask, and where the limits are.

The map

A page names the system, its owner, and where its key lives. Never the value.

access/map.md
Your vault

The key is fetched inside the command that uses it. Nothing prints.

your store, not ours
The system

Your account, your permissions. Edits carry your name.

no connector of ours
1 · password managers

Your AI reads a password from your vault inside the command that uses it.

Your AI opens your vault as you. Pages name items; values are fetched at use.

1Password

Read at the moment of use, through your unlocked app.

what you can ask Bitwarden

Collections and your own vault, one field at a time.

what you can ask Keeper

Shared folders by seat, through Keeper Commander.

what you can ask Keychain

Your computer's own store, read with no prompt.

what you can ask
2 · documents and files

Your AI works in your Gmail, Sheets, Docs, Drive and Notion, signed in as you.

A script you deploy runs Gmail, Sheets, Docs and Drive as you. Notion takes your own token.

Gmail

Search, threads, drafts and cleanup, a send only on your go, through your own script.

what you can ask Google Sheets

Formats, formulas, tabs and real dates, through your own script.

what you can ask Google Docs

Docs edited in place, the writer's text untouched, through your own script.

what you can ask Google Drive

Files, sharing and shared drives, through the folder and your own script.

what you can ask Google Apps Script

The one script behind Gmail, Sheets, Docs, Drive and Calendar.

what you can ask Notion

Pages and databases you can open, under your own token.

what you can ask
3 · team chat

Your AI reads your Slack channels and posts only after your go.

The workspace's own app, approved once. Nothing posts before you see it.

Slack

Your channels read as you; posts sent after your go.

what you can ask
4 · code

Your AI opens pull requests with your own token, and Codex checks its work.

Your own token on the code host, and a second AI in the same folder.

Bitbucket

Repos, pull requests and code search, with your own token.

what you can ask Codex

A second AI on your ChatGPT plan, beside Claude Code.

what you can ask
5 · websites and SEO

Your AI publishes complete WordPress posts and reads your search numbers as you.

Your own user, account and seat. Measured and modelled numbers stay apart.

WordPress

Posts and users, as your own user or through wp-cli.

what you can ask Search Console

Measured clicks and position, per query, as you.

what you can ask Semrush

Rankings, audits and AI visibility, on a team seat.

what you can ask
6 · browsers and terminals

Your AI opens the right Chrome profile and a named terminal window for each task.

Bookmarks changed through Chrome's own API; terminal windows opened by name and colour.

Chrome

Profiles and bookmarks, changed through Chrome's own API.

what you can ask Terminal

Windows opened by name, each in its own colour.

what you can ask
7 · the AI that runs them

Claude Code runs them, and Codex works beside it.

Each runs the commands as you, on your own computer. Claude on the web and the phone reads the map in an open space and runs nothing.

Claude Code

Your AI itself: it reads the brain and runs every tool.

connect it Codex

A second AI on your ChatGPT plan, in the same folder.

connect it

Write the map once, for every AI.

Which systems exist, who owns them, where credentials live. The keys stay put.

Request access → Connect Claude Code