Finish setting up your Brain in VS Code

You set the Brain up through Visual Studio Code, and a few last pieces aren't working yet — the buttons, and the claude command. This page fixes all of it. It's mostly one copy-and-paste.

Why it's not working yet: the Claude Code VS Code extension and the claude command are two different installs. The extension gives you the chat panel inside the editor — but it does not install the claude command in your terminal, and the three buttons need that command. So we install the command, then rebuild the buttons. That's the whole job.

Open the Claude chat you already have

You're set up in VS Code, so you already have a Claude session — that's all we need.

Open the Claude Code panel in VS Code (the one you've been chatting in). If you'd rather use a terminal, that's fine too — but the panel works perfectly for this.

Copy the fix and paste it in

This one block installs the claude command, rebuilds the three buttons with the right colors and behavior, and connects Obsidian.

Copied!

Paste it into your Claude chat and press Enter. It will ask you to do two clicks in Obsidian near the end — that's normal. Let it run the rest by itself.

Prefer to read it first? Open this

Do the two Obsidian clicks

Two safety steps no app can skip — the Brain does everything else.

Open Obsidian → "Open folder as vault" → pick your Brain folder (the one with CLAUDE.md in it).
When it asks, click "Trust author and turn on community plugins."

One vault only: the Brain folder is your vault. Don't point Obsidian at the Desktop or any other folder, or it won't see your notes.

What your three buttons do

After the fix, you'll have three colored shortcuts on your Desktop. Right-click each and choose "Pin to taskbar".

Green — Mission Control

Opens a simple board showing what you're working on. It's a file on your computer — bookmark it.

Amber — New Session

Starts a Claude session you can also use in your browser at claude.ai/code (Remote Control is on).

Red — Close Out

Saves everything, then shuts the PC down. Close its window during the countdown to cancel.

The one habit that matters: when you finish a piece of work, just say the word "handoff" to your session. It writes a tidy resume note and saves it, so the next session picks up exactly where you left off. The word does the handoff — the red button just saves and powers off.

Check these 5 things

1. In a fresh PowerShell window, claude --version prints a version number.
2. The three Desktop shortcuts show colored circles (green / amber / red), not the plain PowerShell icon.
3. Click amber → a window opens and within a few seconds your session appears at claude.ai/code (green dot = live).
4. In that session, type handoff → it replies "Saved", and you see a new entry in wiki/Session Handoff.md.
5. Click green → your Mission Control board opens in the browser.

If any step fails, tell your Claude session exactly what happened — it can diagnose and fix it from there.

Should I keep using VS Code, or the buttons?

Use the amber button to start your working sessions — it launches the proper claude command, which is the only way every session goes "remote" automatically (so it shows up in your browser and on your phone). Keep VS Code open alongside if you like seeing changes highlighted in the editor — but let the button be the thing that drives the session.