R5 · DEVELOPER TOOLING · NPMPROTOTYPEMar 2026

Context that survives between AI coding sessions

THE QUESTION

Can a plain folder structure, set up by one command, help AI coding assistants keep their context from one session to the next?


Founder, Bodham LabsUpdated

What did we build?

  • NeoGravity: running npx @vibcoder/neogravity init scaffolds .agents/ (workflows, skills), .knowledge/ (tasks, research notes) and projects.json.
  • In its README: "It doesn't write code for you — it manages the infrastructure around your AI assistant: context persistence, architectural enforcement, multi-session memory, and workflow orchestration."
  • Published on npm as @vibcoder/neogravity. VibCoder was our founder's earlier label.

What does the evidence show?

Values exactly as recorded. The source column says where each one was recorded.
WHATVALUESOURCE
Published version4.0.0, on 5 Mar 2026npm registry
Downloads124 in the last yearnpm registry, as of Oct 2026
Automated testsNone yetpackage source

Where has it led us?

  1. Context that lives in files survives between sessions. Context that lives only in a chat does not. That is the whole idea, and it is simple on purpose.

  2. The tool manages the structure around an assistant. It does not try to be another assistant.

  3. It shipped without automated tests. That is the main gap.

What is still open?

  • Does the folder structure measurably cut the time an assistant needs to get back up to speed?
  • Which parts of the scaffold do people actually keep using?

NEXT STEP · NOT DONE YET

What would we do next?

Add automated tests, then measure how long an assistant takes to resume a task with and without the scaffold.

Have a problem that needs this kind of research?

Tell us about it