Agentlas
Agentlas
← Back to app
Agentlas OS

Context Map — scoped edits, not project dumps

Keeps an AI edit scoped to what a task actually depends on, and requires the affected files to be reviewed before the task can be marked complete.

Commands

hephaestus context refresh --project .
hephaestus context locate "entity kind routing" --project .
hephaestus context slice --project . --task "fix entity kind routing" --target src/package-kind.ts
hephaestus context impact --project . --changed src/package-kind.ts
hephaestus context verify --project . --changed src/package-kind.ts --reviewed src/register/route.ts

What each one does

  • refresh — builds a dependency map of your project (definitions, backlinks, module edges), kept fresh automatically by a source fingerprint.
  • locate / refs — find where something is defined and everywhere it's referenced.
  • slice — for a specific task, returns only the files and interfaces that task actually depends on, not the whole project.
  • impact — before you change a file, shows what actually depends on it downstream.
  • verify — requires the impacted files to be reviewed (by local tests, CI, or both) before a task can report complete.
INFO · Stays local

Network and Hub discovery never receive your project's source or local map paths. Context Map runs entirely on your machine.

Claude Code and Codex get an automatic warning about reverse references immediately before an edit tool runs — the same map backs Desktop, Terminal, Stormbreaker, and Network staffing, so the answer doesn't change depending on which surface you're using.

Context Map — scoped edits, not project dumps · Agentlas docs