Orient before acting
Index the workspace, resolve imports per language, detect service relationships, and read your project instructions — so the first move is informed rather than exploratory.
MAP · CONTEXT · MEMORYWorkspace intelligence for VS Code
See the system.
Ship the work.
Blacksite gives an AI coding agent the wider view: your codebase, the relationships inside it, the plan, the follow-up queue, and every action taken along the way.
- Views
- Six, connected
- Map
- Live topology
- Keys
- Bring your own
- Control
- You approve changes
◈ Blacksite
Auto
Mode
Ask anything about your codebase…
⌘↵ send@ mention a file/ commands
Implementation plan
Checkpointed session migration
Agent-authored · execution approved · phase 2 of 3
01
Dual-write behind a flag
src/session/checkpoint.ts · 3 files · write latency verified
02
Move readers to the checkpoint store
src/session/*.ts · one-release dual-read window
03
Remove the legacy store
Blocked on phase 2 acceptance criteria
Decision record — why a dual-read window phase 2
Research — legacy store call sites and owners plan level
Work queue
Tickets
Durable outcomes, independent of any one plan.
Open 5
Triage 2
Active 1
All 8
File a ticket…
normal
Add
Next up
Retry backoff must stay under the gateway TTL
BLK-12 · high · small — isolated policy change
●
BLK-12
Retry backoff must stay under the gateway TTL
in progress
BLK-18
Add an empty state for disconnected map services
triage
BLK-21
Document the release rollback path
backlog
Base context · rides along in every request
API response conventions
Pinned
The API returns snake_case; the frontend is camelCase. Conversion happens once, in the transport layer — never in a component.
src/api/transport.ts
src/api/types.ts
Frozen areas
legacy/ is frozen pending the Q3 decommission. Read it for context; do not modify it without an explicit instruction.
Vocabulary
"The queue" always means the Redis one. The SQS path is called "the export pipeline" and is unrelated.
Release checklist
Disabled — only relevant during a release week, and it costs tokens on every turn while it's on.
ExplorerQueryAssistantVectorsRAG
SQL · READ
SELECT plan, count(*) AS n
FROM subscriptions
WHERE status = 'active'
GROUP BY plan ORDER BY n DESC;3 rows4 ms
| plan | n |
|---|---|
| free | 9,042 |
| pro | 1,284 |
| team | 382 |
Writes are classified, never executed by the agent gate
Codebase map
Workspace architecture
Files, modules, services, and live agent context- Files
- 1,284
- Indexed links
- 2,941
Find a file or module…
FilesServicesRoles
Agent reading
src/agent-session.ts
Selected star
Agent session
src/agent-session.ts
Source · 11 links · high heat
Ready
claude-sonnet-4-6
18.4k / 200k context
Live browser recreations of the six extension views — switch views or replay a request. Example project data; current product structure.
Agentic coding
Architecture mapping
Plans & follow-up work
Local data tools
Six views, one workspace
More than a chat box
beside your code.
Chat is only the front door. Plans, tickets, context, data, and the map keep the useful parts of the work visible after a conversation ends.
Chat
The agent loop, visible
Every call appears in the transcript as it runs — file reads, map queries, shell commands, and editor navigation. Four request profiles change how the agent works, not just what it says.
Codebase MapStructure you can query
Files are stars, relationships are arcs, and folders form territories; a separate Services lens shows deployable units and typed routes. The agent queries the same graph for blast radius, paths, and hubs.
PlansWork that outlives a session
Multi-phase plans with per-step state, dependencies, validation, and acceptance criteria. Attach specifications and decision records to the phases that need them.
TicketsFollow-up work that stays found
Capture work that matters without letting it take over the current task. Triage it in the sidebar, move it across the board, connect it to a plan, and see its territory on the map.
Base ContextSay it once
Curated topics and file references that ride along in every request — the conventions, decisions, and vocabulary that don't live in any single file. Toggle a topic off when it stops being relevant.
DataAsk your data directly
An embedded SQLite workbench with a catalog explorer, query editor, natural-language assistant, and local vector search. The agent reads through the same layer — and can never execute a write.
Codebase Map · interactive
Your codebase,
legible at a glance.
Drag the field, scroll to zoom, search, filter by file role, and select a star. The extension runs this view on WebGL against your live workspace; the example below uses a fixed, clearly labelled project.
Codebase map
Workspace architecture
Files, modules, services, and live agent context
Files1,284
Indexed links22
FocusAll
File role
Scroll to zoom · drag to pan · click a star · arrow keys work too
Selected star
Agent session
src/agent-session.ts
- Role
- Source
- Links
- 11
- Heat
- High
Coordinates the turn: tool calls, approvals, compaction, and the durable working context.
Import
API call
Shared data
Note
Blast radius, before you change anything
Ask map_impact what a change reaches: the transitive set of dependents, N hops out, with the edge chain connecting each one back to the seed — grouped by depth and by area.
Paths between two files
map_path returns the shortest concrete chains between two files, one entry per hop with the edge kind. For when you know both ends and need the middle.
Traces while the agent works
Files it reads pulse, files it edits flare, shell commands light up their working directory. The earliest signal that a request was misunderstood is watching it wander.
A calmer way to build
One agent.
The whole picture.
Blacksite keeps execution grounded in the work you're actually doing, so the agent moves with intent instead of producing plausible code and hoping.
Make the intent visible
Turn a request into phases with scoped files, dependencies, validation, and acceptance criteria — something you can argue with before any code moves.
PLANS · DECISIONS · QUESTIONSWork with the gates on
Every edit is a diff you approve. Every sensitive command asks. Every tool call is logged with its input and its result, so nothing about the run is a mystery afterwards.
APPROVALS · DIAGNOSTICS · LOGSBuilt for the whole workspace
Depth where it
actually matters.
The unglamorous parts — schema conversion per provider, cache breakpoints, retry budgets, approval tiers — are the parts that decide whether a tool like this is usable on a real repository.
Navigate relationships, not just files.
Imports resolved per ecosystem — TypeScript path aliases, Go module paths, Java and C# namespaces, Python re-exports, PHP autoload. Plus a service lens that only draws an edge when the client side is verified, so a line means a call rather than two strings that rhyme.
The editor's own semantics.
Symbols, navigation, hierarchies, diagnostics, rename, and code actions come from your language servers — the same answers F2 would give, not a pattern match. Edits target symbols, not line numbers.
Reads run. Writes get classified.
The agent explores the catalog, grounds SQL in the real schema, and executes read queries. Write and DDL statements are classified and handed to you — it cannot run them.
Keep a human hand on the controls.
The model cannot do anything — it emits a structured request, and the extension decides whether to honour it. Diffs before writes, modal prompts for network and destructive commands, per-project allow and deny lists, and an execution log of every call.
Learn the thing, not just the buttons
Documentation that
teaches you something.
Two tracks. Learn explains the concepts behind agentic coding tools in general. The guides explain how Blacksite implements them and how to drive it well.
Start here
Getting Started
Install, connect a provider, let the index build, and make a first request that teaches you something about your own repository.
ConceptHow an agent loop works
Why a model that only produces text can edit your files — and why every safety property lives in the harness rather than in the model's judgement.
ReferenceApprovals & Safety
Where the gates sit, what the three permission lists do, what leaves your machine, and the one setting you should think hard about before enabling.
ReferenceTool Reference
Every family the agent can call, and what knowing they exist changes about how you ask for things.
SetupProviders, Keys & Models
Anthropic, OpenAI, OpenRouter, and Bedrock. Where keys are stored, how thinking effort works, and why a long conversation is cheaper than its token count suggests.
ReferenceSettings & Commands
Every blacksite.* setting and command, with the defaults clearly marked so you only change what you mean to.
Work with the whole system
Build with a
better point of view.
Open Blacksite in VS Code and bring architecture, context, and execution into the same place. Bring your own key — nothing is proxied, and there is no account to make.
Download the latest .vsix, then run code --install-extension blacksite-vscode-<version>.vsix.