Awareness Local

Execute the one-command setup using npx. This installs the Awareness Local daemon, initializes the .awareness/ directory structure in your project, and registers the MCP server automatically.

npx @awareness-sdk/setup

If you want to share memory across devices or team members, re-run setup with the --cloud flag. This adds an optional sync layer while keeping the local store as the primary source.

npx @awareness-sdk/setup --cloud

Add the Awareness Local server to your MCP client config. The setup command may do this automatically, but you can also configure it manually.

{
  "mcpServers": {
    "awareness-local": {
      "command": "npx",
      "args": ["awareness-local"]
    }
  }
}

At the start of each coding session, call awareness_init to load recent knowledge, open tasks, and project rules into the agent's context. This is the primary entry point for session continuity.

During a session, use awareness_record to persist key decisions, architectural choices, and implementation notes. The daemon extracts and indexes these automatically into the knowledge store.

Use awareness_recall for progressive disclosure searches (summary first, then full context) or awareness_lookup for fast indexed queries over tasks, knowledge cards, and risk records.