Connect your AI assistant in VS Code to every Instructed Intelligence tool — knowledge, work, support — with one sign-in. Bring your own AI (Claude or Codex).
Installation
Launch VS Code Quick Open (Ctrl+P), paste the following command, and press enter.
Connect the AI assistant you already use in VS Code to your organisation's
Instructed Intelligence tools, with one sign-in.
You bring the AI. Install Anthropic's Claude extension (recommended) or
OpenAI's Codex extension, signed in with your own account. II Workbench ships
no model and no AI runtime — your own subscription or API key does the
thinking.
We bring the wiring. One Instructed Intelligence sign-in gives your AI
one connection that carries every tool your organisation has:
Cornerstone — your organisation's knowledge (ask it before answering
from memory; capture and distil back to it).
Coordinator — your work (anything with a state is a ticket).
Support — so your AI can raise a ticket when something annoys you.
Whatever ships next — new tools appear on their own; nothing to update.
It stays connected. Your credential doesn't go stale, so a chat you
started last week still reaches your knowledge today.
Works in VS Code and in Cursor (with the Claude Code extension). One product,
several incarnations: this sits alongside the Workbench desktop app and the
Workbench capture agent, for the IDE-native platform.
How it works
Sign in once with your Instructed Intelligence account — a browser tab
opens, you sign in, done. Your credential is kept in your operating system's
keychain and stays valid until you sign out.
VS Code's built-in agent is connected straight away.
Connect my tools adds the same connection to Claude and/or Codex,
whichever you have installed — one sign-in, every tool, no per-tool logins.
Tools show up in your next chat session.
Add the knowledge guide (optional) teaches your AI to check your
organisation's knowledge before answering, offer to save new decisions and
rules (you approve each one), and flag anything that may be out of date.
Simplify the layout (optional) turns VS Code into a chat-first workspace.
Your previous settings are saved and can be restored with one click.
Commands
Command
Does
II Workbench: Sign in
Sign in to Instructed Intelligence in your browser
II Workbench: Sign in with an API key (advanced)
Paste a key from your Instructed Intelligence connect page instead
II Workbench: Sign out
End the session and disconnect every tool
II Workbench: Connect my tools to Claude / Codex
Wire Instructed Intelligence into your AI
II Workbench: Add the knowledge guide to this workspace
Write the guide into CLAUDE.md / AGENTS.md
II Workbench: Simplify the layout (chat-forward)
Hide programmer clutter
II Workbench: Restore my layout
Put your previous settings back
II Workbench: Show connection status
Sign-in state, wired clients and endpoint
II Workbench: Open getting started
Re-open the first-run walkthrough
Settings
Setting
Default
Purpose
iiWorkbench.junction.url
https://junction.instructedintelligence.com
Your Instructed Intelligence endpoint. Change only if your organisation self-hosts.
iiWorkbench.tenant
empty
Your organisation's knowledge-base id. Leave blank to be asked on first use.
Privacy
Your AI vendor relationship is your own. Instructed Intelligence never sees
your Anthropic or OpenAI credentials and never routes your prompts.
Your Instructed Intelligence credential lives in your operating system's
keychain, never in a file. Signing out revokes it and removes the connection
from every assistant the extension wrote to.
The extension sends that credential only to your Instructed Intelligence
endpoint, over HTTPS. It collects no telemetry.
Before writing to Claude's settings the extension backs the file up to
~/.claude.json.ii-bak, and it refuses to write if the file can't be read.
In Codex's settings it only ever adds or removes its own sections.
Develop
npm install
npm run watch # tsc in watch mode
# then press F5 in VS Code to launch the Extension Development Host
npm test # headless tests, no network
npm run package # build a .vsix
Configuration is per-user and safe to wipe (II Workbench: Sign out clears
the stored session).
