Is it safe to give an agent?
Paths outside the workspace are unreachable, symlink escapes included. Every edit is a compare-and-swap on a content hash, so it fails rather than landing on text the agent never saw. Writes to one file are serialized across processes, and editMatches is all or nothing.
Does it replace git?
No. Change tracking sits beside git and commits through it, with real git commit, so your hooks, signing and history are untouched. Its journal lives in .git/vegvisir/ and its file versions in git’s own object store.
Which languages does it understand?
Every text file, through a zero-dependency heuristic parser. With the optional tree-sitter layer, which the MCP server and the pi extension load automatically, declarations are exact for TypeScript, TSX, JavaScript, Rust, Python, Java, Kotlin and Swift.
Will it slow my agent down?
It is meant to do the opposite: the same work in fewer round trips. Searches skip dependency and build folders, binaries and very large files, and every output is capped so one call cannot flood the context.
Does it need Ordne?
No. Vegvísir is a standalone set of npm packages that works with any MCP client. Ordne is where it is most at home, because Ordne can show each agent’s changes and commit them per agent.
Can my agent still use the shell?
Yes. Vegvísir replaces file plumbing, not the shell. The pi extension can additionally block read-only shell file commands such as cat and grep, and point the agent at the matching tool instead; set VEGVISIR_BASH_GATE=0 to turn that off.