Track 2 — Claude Code (in browser VS Code)

Goal: open VS Code in your browser, where the Claude Code CLI and extension are already installed, sign in once, and run a spec-driven task on the LaTeX starter.

This runs as a container in the kit — already up. No host install of VS Code or Claude Code needed.

Docs: https://code.claude.com/docs

1. Open the workspace + fetch the projects

• Browser VS Code: https://aiworkspace.konomondo.org

The Claude Code extension is pre-installed and the claude CLI is on the PATH. Open a terminal (Terminal → New Terminal) and clone the project repos:

clone-projects        # clones latex-starter + hermes into ~/projects

(If an admin set a GITHUB_TOKEN they’re already cloned; otherwise you’ll sign in with your own GitHub account — and your commits are attributed to you.)

Don’t confuse the two chat panels. VS Code has a built-in “CHAT” panel that says “You need to set up GitHub Copilot…” — that is not Claude Code; ignore it. Claude Code is the Claude-logo icon in the left activity bar (or Command Palette → “Claude Code: New Conversation”).

Make your commits yours (optional)

When the kit auto-clones the projects with a shared token, commits would be attributed to that token — not to you. To fix it, in the project’s terminal (e.g. inside projects/latex-starter):

git config user.name  "Your Name"
git config user.email "you@example.com"   # the email on your GitHub account

That alone is enough: GitHub attributes a commit to whoever’s email matches their account, regardless of which token pushed it.

To also push as yourself (or to your own fork), repoint the remote and sign in:

git remote set-url origin https://github.com/Konomondo/latex-starter.git
gh auth login        # or paste your own access token when prompted

Set the identity in each repo you work in (latex-starter, hermes). If no token was set, clone-projects already had you sign in — your commits are yours from the start.

2. Sign in to Claude (one time)

Open a terminal in VS Code (Terminal → New Terminal) and run:

claude

Follow the prompt to sign in. Any paid Claude subscription (Pro / Max / Team / Enterprise) or a Console account works. If the browser sign-in flow is awkward inside the container, an admin can set ANTHROPIC_API_KEY in the stack environment and redeploy — the key is passed into the workspace.

You can also use the Claude Code panel from the VS Code activity bar (the extension) instead of the terminal.

3. Install Superpowers

Superpowers is the spec-driven methodology toolkit. Install it in Claude Code:

/plugin install superpowers@claude-plugins-official

4. First spec-driven task

Now point Claude Code at one of the starter TODOs (e.g. “add an explain_steps tool”) — just describe what you want. Superpowers’ skills trigger automatically: it’ll brainstorm → write a plan → execute with review checkpoints, test-first, instead of dumping code.

Keep the task scoped to the LaTeX project so Tracks 2 and 3 reinforce each other — they share this same workspace.

Done when: claude is signed in, Superpowers is installed, and you’ve completed one brainstorm → plan → execute pass on a starter TODO.

Concept behind this: Spec-driven development · Superpowers. Next: Track 3 — the LaTeX build and the roadmap.