VXU / JournalIZItay ZrihanFounder / CEO↗
VXU LABS / OPEN-SOURCE LAUNCH

Your session ends. Your project remembers.

Introducing DIP: persistent project memory for coding agents, with an open invitation to help build it.

You reopen a project. The code is there, but the reason behind a change is buried in a conversation. One task was finished, another was paused, and a passing check may belong to an older version. Before you can move forward, you have to reconstruct what happened.

DIP, the Development Intelligence Platform, gives that history a place alongside the code. Plans, future ideas, ownership, checkpoints and verification evidence live in a project record that can travel through Git.

Give the next session a useful starting point.

With supported hooks enabled and trusted, DIP records ordinary agent, file and Git activity automatically. Codex and Claude Code integrations supply compact context at session entry. Agents can then use MCP tools to claim work, refine intent and leave a meaningful handoff.

That distinction matters: recording activity tells you what was observed. It does not automatically prove a task is complete. DIP keeps checkpoints, task state and verification separate.

A green check needs a connection to the code.

DIP runs named checks you configure and stores the result with a code snapshot. When relevant code changes, the evidence becomes stale. The next person or agent can see that the previous result needs another look.

A local coordinator also manages task and scope claims across worktrees on one machine. Separate machines need a shared coordinator for live exclusivity. The current release does not claim distributed locking through Git.

Local records. An open implementation.

DIP makes no model or API calls of its own. Your existing coding agent interprets intent; DIP keeps the project record. The source is available under Apache-2.0, and the current early release requires Node.js 24 or later.

The installer changes machine integrations, including agent settings and Git hooks. Read the setup guide before installing, and check the documented automation boundaries. A single-project path is also documented for trying the local workflow.

You can make the next developer’s first session better.

We are inviting contributors to start with concrete, reviewable work. You do not need to understand the entire system to make a useful contribution.

Comment on the issue with your proposed scope before starting. The contributor guide explains setup, isolated testing and commit sign-off.

Try one handoff. Tell us what is missing.

Take a disposable project, save an unfinished task and a checkpoint, then return to it. Does the record tell you enough to continue? A precise report of what you could not recover can be as useful as a pull request.