TruthSpine for VS Code
TruthSpine attaches a VS Code workspace to the local TruthSpine records engine so AI coding work can use compact, traceable project truth instead of giant pasted context.
Commands
TruthSpine: Attach WorkspaceTruthSpine: Sync Current WorkTruthSpine: Open DashboardTruthSpine: Open AppTruthSpine: Download AppTruthSpine: Start 14-Day TrialTruthSpine: Buy Solo V1TruthSpine: Activate LicenseTruthSpine: License StatusTruthSpine: Review Truth NotesTruthSpine: Install MCP For This WorkspaceTruthSpine: Start Local Agent PlanTruthSpine: Run Local Agent StepTruthSpine: Run Full BuildTruthSpine: Continue Full Build
Trial, Purchase, And Activation
The VS Code extension is the free install and discovery surface. The local TruthSpine app is still required because it owns the records engine, trial, checkout handoff, activation, and machine license.
- Install the extension from VS Code Marketplace.
- If the app is not installed yet, run
TruthSpine: Download App.
- Open a workspace and run
TruthSpine: Attach Workspace.
- Run
TruthSpine: Start 14-Day Trial to begin the no-card trial on this machine.
- Run
TruthSpine: Buy Solo V1 to open secure TruthSpine checkout in your browser.
- After purchase, run
TruthSpine: Activate License and paste the license key.
One active Solo V1 machine license works across every supported TruthSpine connector surface on that same machine. VS Code does not require a separate TruthSpine license.
Supported TruthSpine Connectors
TruthSpine is built to connect with Visual Studio Code, GitHub Copilot in VS Code, Claude Desktop, Codex, Windsurf/Devin, Open WebUI, LM Studio, Continue, Cline, and Roo Code. Each connector uses the strongest supported local extension, plugin, MCP, or configuration route available in that host. Surfaces without a usable connector are not presented as supported.
- Chat participant:
@truthspine
- Slash commands:
/attach, /context, /whole, /brainstorm, /gap, /verify, /nudge, /sync, /agent, /step, /build, /continue-build, /download, /trial, /buy, /license
- Language model tools:
#truthspineContext, #truthspineGapLedger, #truthspineNudge, #truthspineUpdate
Use these from VS Code chat or compatible agent mode when the host exposes chat participants and extension language model tools.
Ordinary prompts sent to @truthspine run the TruthSpine answer guard before the participant answers. The extension then calls the gap ledger, direct TruthSpine answer packet, or compact context route based on the guard result.
Use /whole before repo-wide planning, /brainstorm before broad ideation, /gap when checking missing or blocked work, and /verify when the user wants proof that TruthSpine has useful project coverage.
Direct Local Agent
Use TruthSpine: Run Local Agent Step for one bounded local-model edit inside VS Code. The command loads compact TruthSpine project context, calls the configured local OpenAI-compatible model, accepts one workspace-relative replaceFile JSON operation, applies that file, opens it, and records a trace.
Use TruthSpine: Run Full Build or @truthspine /build after a plan is locked. The command starts a TruthBrain full-build director session, writes runtime/truthbrain/full-build-session.json, writes the current bounded work order to runtime/truthbrain/current-work-order.json, and records a parent/child lineage trace before any repeated model execution is allowed.
Use TruthSpine: Continue Full Build or @truthspine /continue-build to consume the persisted current work order. The extension calls the configured local OpenAI-compatible model, accepts one allowed replaceFile operation, writes proof, applies the director trace, advances or blocks the session with lineage, and refreshes runtime/truthbrain/current-work-order.json.
The direct local-agent bridge defaults to http://127.0.0.1:1234/v1 because the extension itself injects TruthSpine context. Use the TruthSpine router at http://127.0.0.1:3123/v1 for outside chat surfaces that need automatic TruthSpine injection before the model answers.
MCP Setup
Use TruthSpine: Install MCP For This Workspace to write .vscode/mcp.json.
The generated server entry points at the local TruthSpine MCP server and sets TRUTHSPINE_PROJECT_ROOT to the active workspace folder. It does not write secrets into the workspace.
VS Code may ask you to trust the local MCP server and may ask before individual tool calls. That is expected host security behavior, not a TruthSpine failure.
- Windows, macOS, and Linux use the same extension commands.
- macOS and Linux receive the VS Code MCP
sandboxEnabled flag.
- Windows does not receive the sandbox flag because VS Code documents local stdio sandboxing as unavailable on Windows.
Official References
