Skip to content

Vector Claude Code setup

Vector is Justin's Windows 11 Pro PC. Username on the box is Justi (not justinwieb).

What lives on Vector

  • Claude Code installed locally in PowerShell. Fully independent Claude with its own memory store, separate from Console.
  • Vector-Claude memory: C:\Users\Justi\.claude\projects\C--Users-Justi-forge-vector-local\memory\ (own MEMORY.md index, own user/reference/project topic files).
  • Working folder convention: C:\Users\Justi\forge-vector-local\ is the canonical home for forge-related local code on Vector. Sibling layout for tools (Premiere_MCP, future MCPs, etc).
  • Connectors enabled: Gmail, Google Calendar, Google Drive MCP connectors (need auth on first use).
  • Skills loaded: update-config, keybindings-help, simplify, fewer-permission-prompts, loop, schedule, claude-api, init, review, security-review.
  • Premiere Pro installed via Justin's Adobe Creative Cloud subscription. Sol also has it. Don't open the same .prproj on both at once.
  • Past tooling: C:\Scripts\CreateProject.ps1 — right-click "Create Project Directory" PowerShell script (folder automation, finished 2026-03-17).

Drive mappings on Vector

Letter Mount
C:\ Local SSD
M:\ Media network share (probably Finn-served)
W:\ Workspace network share (Finn-served, same drive Sol mounts as /Volumes/workspace/)

Pairing Vector-Claude with Console-Claude

Cross-machine work is done via Vector to Console SSH only (Vector authenticates as a client to Console; Console never has keys into Vector). The trust model: Console is the powerful agent hub with secrets, so we don't push credentials from there to a personal endpoint.

The pattern when both Claudes work on the same task: 1. Console-Claude writes a shared markdown scratchpad in forge/data/<project>/notes/<task>-log.md. 2. Vector-Claude reads it via ssh console "cat /home/justinwieb/forge/.../log.md". 3. Vector-Claude executes the local-side work and appends results via ssh console "cat >> ...". 4. Console-Claude reads the update on next prompt, plans next step, writes back.

Worked example: forge/data/video-edit-eval/notes/round3-install-log.md (hetpatel-11 Premiere MCP install on Vector).

PowerShell-specific gotcha for the write side

PowerShell does NOT support bash heredoc (<<EOF ... EOF). To pipe multi-line content into ssh on Vector, use a PowerShell here-string and pipe:

@"
multi-line
content
"@ | ssh console "cat >> /path/to/file"

The closing "@ must be at column 0 with no leading whitespace.

When to send work to Vector vs do it on Console

  • Vector: anything that needs Premiere Pro, Windows-native tooling, the workspace drive accessed at native speed, or local GPU.
  • Console: anything that needs forge memory, secrets in ~/.forge-secrets/, Cloudflare/n8n/Notion integration, or the broader agent fleet.

[Claude Code]