Jul 4, 2026
Start Every AI Session With the Right Memory
Give each new AI coding session a controlled brief of pinned memories, decisions, preferences, recent work, and known context gaps.
A new AI session usually begins with a tax. Before useful work can start, you explain the project, restate the decisions already made, paste the preferences that should have been remembered, and warn the tool about the dead ends you found yesterday. If you switch from one coding assistant to another, you pay that tax again.
Keeping a large instruction file helps only until it becomes stale. It may contain too much for the current project, too little from recent work, or edits you are afraid an automated process will overwrite. The real need is a brief that comes from your current vault, fits the tool you are opening, and stays under your control.
What changed
Auto-Inject Memory gives supported AI tools a compact working brief at the start of each new session. You can include pinned memories, preferences, decisions, facts, recent work, and classification gaps without copying them by hand, while previewing the exact managed block before anything is written.
How it works in practice
Preview the brief before you opt in
Open Connection, choose Auto-Inject, and select Preview block while the master switch is off. You can inspect the exact context 1AIVault would provide before it touches an instruction file. The preview includes the working memory and the gaps the AI should notice, so you can decide whether the snapshot is useful rather than trusting a hidden export.
Nothing is written until you explicitly enable the feature. That makes the first step reviewable: you can check for an outdated preference, an irrelevant project, or a memory that should be pinned before the same brief reaches another tool.
Choose how much context each new session receives
Under How much to inject, choose Minimal, Standard, Rich, or Max. Minimal keeps the brief to critical saved context. Larger profiles include more recent work and unclassified tail context, with the biggest budgets reserved for Pro.
The profile controls the context budget rather than blindly dumping the vault. Each supported instruction target also respects its own file limits. Gemini CLI and Antigravity, for example, share a global rules file with a fixed character cap, so the generated block is sized to fit the environment that will read it.
Enable only the tools you actually use
Turn on injection for Claude Code, Codex CLI, Gemini CLI, Antigravity, Qwen Code, OpenCode, or Windsurf. Each target writes to the instruction file that tool already reads: CLAUDE.md, AGENTS.md, GEMINI.md, QWEN.md, or the relevant global rules file.
After enabling a target, use the built-in test flow. Start a fresh session, paste the provided audit prompt, and ask the AI to describe the context it already knows without calling any tools. If it can name the current projects, decisions, preferences, and gaps, you have direct evidence that the brief was loaded.
Open sessions do not reread static instruction files automatically. When your vault changes, choose Refresh now, then begin a new session. The status row tells you whether the tool is off, injected, handled through the Claude Code hook, or skipped because the block was edited by hand.
Scope the brief to one project
Choose a project when you want the static block to include only memories tagged for that work. A focused coding session can receive the decisions and recent activity for one repository instead of unrelated context from your whole vault.
This keeps instructions smaller and reduces accidental cross-project assumptions. You can return to all projects when the session needs broader personal preferences or work that spans multiple repositories.
Give Claude Code fresh, project-aware memory at startup
Install the Claude Code session hook when you want the newest context on every start. The hook is added to Claude Code’s SessionStart configuration and reads the vault database live, even when the 1AIVault window is closed. It uses the current working directory to include project-specific memories when they are available.
While the hook is installed, 1AIVault removes its static CLAUDE.md block so the same context is not injected twice. If you remove the hook while Claude Code remains enabled, the static block is restored. You can move between the two approaches without cleaning up configuration by hand.
Keep your own instruction edits safe
1AIVault manages only the text between its own markers. Content above and below that block stays untouched. If you edit the managed block yourself, the next automated rebuild recognizes the change and reports Hand-edited — skipped instead of overwriting it.
The service also skips identical rewrites. If the current brief already matches the vault selection, it leaves the file alone. You get refreshed memory when something meaningful changes without noisy file churn on every background event.
Before vs After
| Task | Before | Now |
|---|---|---|
| Start a coding session | Paste the same project background and preferences again | Begin with a vault-generated working brief already loaded |
| Control context size | Maintain one growing instruction file | Choose Minimal, Standard, Rich, or Max |
| Focus on one repository | Remove unrelated notes manually | Scope static injection to a tagged project |
| Check what an AI will receive | Open and inspect several tool-specific files | Use Preview block before enabling |
| Refresh Claude Code context | Rewrite CLAUDE.md and restart the session | Use the project-aware SessionStart hook |
| Preserve manual instructions | Risk an updater replacing your edits | Keep non-managed content untouched and hand-edited blocks skipped |
Who benefits most
Developers who move between Claude Code, Codex, Gemini, and OpenCode can carry the same durable decisions without turning every session into an onboarding conversation. Each tool reads the format it already understands.
People managing several projects can keep context narrow. A client repository does not need the preferences and unresolved questions from a personal experiment, but both can still live in the same local vault.
Teams of one who rely on detailed AI workflows gain a reviewable source of truth. The brief is generated from pinned and recent memory, while the preview and hand-edit guard keep automation from becoming opaque.
Try it
Open Connection → Auto-Inject, preview the block, choose a context profile, and enable one detected AI tool. Start a fresh session and use the test prompt to confirm that your current memory arrived before your first real request.