Visp Labs · open tools for coding agents and production systems

Keep the thread.

Coding agents start every session from zero and grade their own work. Production answers to more people than the ones who wrote the code. Visp Labs builds open tools that keep what your project knows, check what your agent builds, and guard what runs.

Meet the tools Read the docs

Fig. 01 · The Visp field

  • Remembered
  • Present session
  • Written down

Move through it. Click to send a pulse.Touch to stir it. It always finds its shape again.

  • Local-first
  • Open source
  • Works with any MCP client
  • Every memory cites its source
  • Evidence is what ran, never what was claimed
  • Abstains when nothing is relevant
  • Edits stay inside the authorized scope
  • Every query recorded before it runs
  • Unsupported SQL fails closed
  • Every answer names its source
  • Same bytes, same answer, Java or JavaScript
  • Reviewed by a model that never saw the claim

From the lab

One thread, five tools.

Three tools for working alongside a coding agent, and two for the production systems it helps you build. Each stands alone, and each one is open source.

For coding agentsMemory · Code · Code Note

  1. 01Available

    Visp Memory

    Decisions, lessons, and goals from your project, recalled for your agent only when they matter. Explore
  2. 02Beta

    Visp Code

    A harness that runs the checks, bounds the scope, and has your agent’s work independently reviewed. Explore
  3. 03In development

    Visp Code Note

    Taking shape in the lab. Details when it’s ready. Coming soon

For production systemsDB Access · Tierwise

  1. 04v0.1.0

    Visp DB Access

    A self-hosted gateway that checks, limits, masks and audits every statement before it reaches your production database. Explore
  2. 05Pre-release

    Tierwise

    Typed, layered configuration and decisions that explain themselves, with the same answer in Java and JavaScript. Explore

How they fit

Before, during, after.

Memory and Code each stand alone, so install one or both. Used together, they cover a session end to end: Memory before and after the work, Code while your agent does it.

Three specimens on a dark lab bench: an amber silk infinity ribbon, a lattice of blue glass rods, and a stack of translucent mint sheets.
Fig. 02 · The lab bench
  • MemoryRemembered
  • CodePresent session
  • Code NoteWritten down · in development
  1. 1Before it startsvisp-memory briefDecisions, warnings and goals that clear the bar, each with its sourceVisp Memory
  2. 2While it worksvisp workOne slice at a time, inside an authorized file scopeVisp Code
  3. 3When it says donevisp doneThe declared checks run, then an independent reviewer judges the resultVisp Code
  4. 4After the changevisp-memory decisionWhat you decided and why, recorded with its reasonVisp Memory
The next session starts with it
One session with both tools. Visp Code Note is in development; details when it’s ready.

Pick up where you left off.

Visp Memory

pip install "visp-memory[mcp,capture]"

Visp Code

npm install -g visp-coder@beta

Visp DB Access

docker pull ghcr.io/djkeshawa/visp-db-access:0.1.0
Memory docsCode docsDB Access docsTierwise docsPyPInpm