Never4gA, short for never forget again, is memory for you and every AI agent you work with. It keeps your notes, decisions and project history as plain Markdown on your machine, and hands each agent session exactly the part it needs before the session starts.
Early days. This is version 0.1, in daily use by the person who built it and new to everyone else. Expect rough edges and interfaces that still move, and tell us when you hit one.
It does that without a model. Finding the right context is lookups, queries and file reads, so it costs no tokens, takes seconds, and gives the same answer every time. Your agent spends its budget on the work, not on searching for what it should already know.
Why it's built this way
Most agent memory asks a model to decide what's relevant, or lets the agent go looking with its own tool calls. Both spend tokens and turns before any work happens. Never4gA does that part first, mechanically:
- Fewer tokens. In the vault it was built in, 2,153 files and about 3 million tokens of notes, a session starts with a pack of about 10,000 tokens. That's what the agent reads. Nothing else is loaded.
- Faster starts. That pack is assembled in about four seconds, including live Git and tracker state, with zero model calls.
- You can see why. Every item in a pack names the reason it was included. The same question gets the same pack.
What it does
| Remembers across sessions | Each session opens with what the project is, the rules it follows, what was decided, and what the last session left open. |
| Remembers across tools | Claude Code, Codex, Antigravity and any MCP client read the same memory. Switch tools and nothing is lost. |
| Writes back what happened | Sessions record progress and decisions as dated logs, so the next one picks up where this one stopped. |
| Keeps your notes yours | Everything is Markdown in a normal Obsidian vault. Uninstall Never4gA and your notes are exactly as they were. |
| Starts from the notes you have | Point it at an existing folder. Your files stay where they are, and your notes are searchable on the first run. |
| Brings in your tracker | Open work items from OpenProject join the pack, and a session can update them. |
How it works
flowchart LR
V[("Your Markdown<br/>vault")] --> I["Local index"]
subgraph M["Found by lookup, not by a model"]
direction TB
S1["Where you are<br/>repo → workspace"] --> S2["Types and metadata"]
S2 --> S3["Full-text search"]
S3 --> S4["Links and relations"]
S4 --> S5["Git and tracker state"]
end
I --> M
M --> P["Context pack<br/>every item says why"]
P --> A["Claude Code · Codex<br/>Antigravity · MCP"]
A -. "what the session did" .-> V
A pack is built in stages, and each stage is a query: which workspace this repository belongs to, which documents that workspace holds, what full-text search finds, what those documents link to, and what Git and your tracker say right now. A pack never grows past its budget. A model gets involved when you ask for judgment, and never for work a lookup can do.
In Obsidian: the Never4gA Companion plugin shows the same pack beside the note you're reading, with the reason each item is there. Install it from its latest release or with BRAT; it isn't in Obsidian's community plugin list yet.
Quick start
Never4gA is made to be driven by your coding agents. You install it once and connect the agents, and from then on they open each session, look things up and write back what they did, using the Skills Never4gA gives them. You don't run it by hand in day-to-day work.
1. Install it and make a vault (a folder of Markdown, new or already full of your notes):
uv tool install never4ga
export NEVER4GA_VAULT=~/notes
never4ga init
never4ga index
uv installs the Python version Never4gA needs if you don't already have it.
2. Connect your agents to Claude Code, Codex or Antigravity, whichever you have installed. The Code tab in the Claude desktop app runs Claude Code, so it is connected the same way:
never4ga adapters sync --apply # the Skills, into each agent
never4ga adapters mcp --apply # the MCP server, so agents can call Never4gA directly
3. Attach a project. Give the repository a workspace in your vault, and tell the agents working there to ask Never4gA for context:
cd ~/code/my-project
never4ga workspace create "My Project" --type project
never4ga workspace map <workspace-id>
never4ga adapters sync --apply --repositories
--repositories writes a small pointer file into the mapped repository, ignored by Git, that tells an agent to start from Never4gA. Without it, adapters sync --apply only updates the agents themselves.
4. Start a session. Open Claude Code (in a terminal or the Claude desktop app), Codex or Antigravity in that repository and work as usual. The agent runs the never4ga-startup Skill first, which hands it the project's context pack: what the project is, the rules it follows, what was decided, and what the last session left open.
What your agents can do with it
The Skills are what the agents actually use. Each one is a short set of instructions for a single job, so an agent does it the same way every session:
| Skill | The agent uses it to |
|---|---|
never4ga-startup |
Open a session with the project's context pack. |
never4ga-context |
Look up more on a topic once work is under way. |
never4ga-checkpoint |
Record progress as it happens, so an interrupted session loses nothing. |
never4ga-wrap |
Close a session by writing the dated log the next one starts from. |
never4ga-create |
Write a plan, note or other document into the right place with valid metadata. |
never4ga-decide |
Draft a decision for you to accept. It never accepts one itself. |
never4ga-capture |
Put a loose thought in your Inbox for you to file. |
never4ga-doctor |
Check the vault's health and report what it finds. |
You can ask for any of them in plain words ("check the vault", "write this up as a note") and the agent picks the Skill. The same operations are available to any other MCP client through never4ga-mcp.
Using the command line directly
Everything the agents do is also a never4ga command, and the commands are there when you want them: searching your notes, inspecting a pack, or scripting.
never4ga search "what we decided about auth"
never4ga context startup --client claude-code --cwd .
never4ga doctor
never4ga --help lists the rest.
What it won't do
- Call a model for you. It has no API key and never meters your usage. You bring the AI tools you already pay for.
- Send your notes anywhere. Everything runs on your machine, and the service only listens on localhost.
- Take over your files. The index is disposable and rebuilt from your Markdown. Your files are the only source of truth, and nothing is committed to Git for you.
Good to know
- Context packs follow repositories. A workspace is attached to a Git repository, and a pack is built for the repository you're in. Notes that aren't tied to one are fully searchable but don't get a pack yet.
- Platforms. Built and tested on Linux and macOS. On Linux the background service runs under systemd; on macOS, run
never4ga servein a terminal instead. Windows is not supported yet. - Four ways in. The Skills and MCP server your agents use (
never4ga-mcp), thenever4gacommand line, a local HTTP API, and the Obsidian companion. All four run the same code.
Tell us where it's wrong
If something didn't make sense, or didn't work the way this page says it does, open an issue. That's the most useful thing you can send.
GitHub is Never4gA's only public home. Issues and pull requests go there. To report a security problem, see SECURITY.md rather than opening an issue.
Working on Never4gA
The design is written down. docs/specs/ holds the specifications; start with 00-spec-index.md. They're generated from the maintainer's notes, so propose a change in an issue rather than editing them. AGENTS.md is the contract for AI agents working in this repository, and a fair summary of the rules for people too.
uv venv --python 3.14 .venv
VIRTUAL_ENV=.venv uv pip install -e '.[dev]'
.venv/bin/ruff check . && .venv/bin/ruff format --check . && .venv/bin/mypy && .venv/bin/pytest
That last line is the gate, and every pull request runs it.
License
Apache License 2.0. Never4gA, by BezaCore Labs.
Metadata
Release files for never4ga 0.1.2
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | Actions |
|---|---|---|---|---|
| never4ga-0.1.2.tar.gz | 516.4 kB | With provenance | Details for never4ga-0.1.2.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| never4ga-0.1.2-py3-none-any.whl | Python 3 | none | any | Details for never4ga-0.1.2-py3-none-any.whl |
Total release size: 1.2 MB
Release files / never4ga-0.1.2.tar.gz
| Download URL | never4ga-0.1.2.tar.gz |
|---|---|
| Size | 516.4 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
b2ccb75f3f5e204c2ea7821baeb64da7e577c1f56956d175dc2452858f696b3e
|
|
BLAKE2b-256 checksum How to use checksums |
5dc938a1b970b88f25f1cd70ef4dbf9113eda3b3a795c81e2250e8678e94c96d
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.16
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Oct 28, 2026.
Transparency logRelease files / never4ga-0.1.2-py3-none-any.whl
| Download URL | never4ga-0.1.2-py3-none-any.whl |
|---|---|
| Size | 641.1 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
5a3e4158cdd78eaca32ba1e0bd6637b8a84468985ee5663cf44fa8ead810ea06
|
|
BLAKE2b-256 checksum How to use checksums |
cd7a8d0fddbc365935e727db1baea29c0c907ed0446726443fda815fd6c63bc0
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.16
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Oct 28, 2026.
Transparency logSecurity for never4ga 0.1.2
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
Full provenance
Both files in this release have been uploaded with provenance metadata.
Attestation for never4ga-0.1.2.tar.gz
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Oct 28, 2026.
Transparency logA note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.