Memory for Cline

Memory for Cline — Persistent Context Across Tasks | Awareness

Give Cline persistent memory across tasks and sessions: local Markdown, structured decisions, and a shared task board. Free, no account.

Install locally

npx @awareness.market/setup --ide cline

Local-first. No account required. The setup CLI writes the rules and MCP config for this IDE.

The problem

Cline starts every session from zero.

Each Cline task starts informed

Cline is task-oriented: approve, run, repeat. Without memory, every task starts from zero and re-discovers the same constraints. Awareness loads the project decisions and open questions before the first tool call.

Recall happens before planning

The injected rules make the agent load recent decisions and constraints at session start, so it does not re-derive what the last session already settled.

Local-first by default

Memory lives in Markdown and SQLite under your project. No account, no API key, and nothing leaves the machine unless you opt into cloud sync.

One brain across IDEs

The same daemon serves every editor and agent. A decision recorded in one tool is available in the next, with project isolation by directory.

How it works

Recall before work. Record after.

01

Install the memory layer

Run the setup CLI. It detects the IDE, writes the MCP config, and injects the workflow rules that make the agent recall before it plans.

02

Keep working as usual

No new commands to remember. The agent initializes memory at session start and records decisions as it works.

03

Switch IDEs without losing context

Open the same project in another editor. The task board and memory are already there.

Awareness injects workflow rules into Cline's configuration, so the agent initializes memory at session start, recalls before work, and records decisions after every change. Retrieval runs on local SQLite with hybrid semantic + full-text search; it makes zero LLM calls.

What gets remembered

Knowledge, not a transcript.

  • Decisions and the reasons behind them
  • Constraints, pitfalls, and failed approaches
  • Open questions and the next concrete step

Compare

Where Awareness fits.

CLAUDE.md / AGENTS.md alone

Static files someone has to maintain. Awareness is written by the agent as it works, and recall is automatic.

Cloud memory APIs

Managed and remote. Awareness is local-first by default: Markdown + SQLite on your machine, no account.

Editor chat history

Locked to one tool and one session. Awareness is shared across IDEs and survives restarts.

Frequently asked questions

Does Awareness work inside VS Code with Cline?

Yes. The setup CLI writes the Cline MCP server config and injects the workflow rules. Cline keeps its normal approval flow.

Does it record every tool call?

No. The agent records decisions, constraints, pitfalls, and open questions — not raw logs. You can review and edit the Markdown at any time.

Can multiple Cline tasks share a task board?

Yes. Tasks live in the same local daemon, claim atomically, and expose a handoff so the next task does not repeat work.

Does this require an account?

No. Local-first memory is free forever and needs no account or API key. Cloud sync and team features are optional.

Where is the memory stored?

In a .awareness/ directory inside your project: Markdown files plus a SQLite index. It is portable and git-friendly.

How is this different from a rules file?

A rules file is static. Awareness records what actually happened — decisions, pitfalls, open questions — and the agent recalls it before planning.

Give your agent a memory that compounds.

Local-first, no account, no credit card. Start in 30 seconds and keep the data on your machine.