DEDUPED Hot AI repos, turned into use cases Get the Monday 5

How to review what each coding agent remembers in a web console with Loci

Discover agent memories on your machine and browse them in the built-in Web console.

  • Research
  • Intermediate
  • 30 minutes
  • From the README
  • Any agent

Who it is forA developer who wants to audit or clean up what their coding agents have stored as memory.

The problemAgent memory files are scattered across tools and hard to compare or check.

The outcomeA list of detected harness memories with per-tool stats, browsable in the browser.

What you need first

  • Python 3.11 or newer
  • git and a terminal
  • An embedding endpoint that supports /embeddings, plus a chat endpoint (may be a local one)
  • A notes or project docs directory to index

Steps

  1. Make sure the instance is set up with config.toml, as in the quick start.
  2. Run loci harness to inspect detected agent memories.
  3. Run loci serve-http to start the HTTP backend.
  4. Open http://127.0.0.1:8765/ui in a browser and browse harness memories, file views and per-tool stats.

Prompt for your agent

Using the IvenKooLab/loci repo, run loci harness in the instance at <instance-path> and then start loci serve-http. Expected output: a list of detected agent memories and a reachable console at 127.0.0.1:8765/ui. Verify that the console shows the same memory count as the loci harness output.

Caveat. By default anonymous loopback clients have admin access, so keep the console on the local machine unless you set [http] local_admin = false and configure role-based tokens.

Use this in your AI agent

Ask your agent

Using the Deduped MCP, get the setup steps for IvenKooLab/loci and "Review what each coding agent remembers in a web console"

Add Deduped to Claude Code once

claude mcp add --transport http deduped https://dedupedai.com/mcp

Cursor, ChatGPT, others

Share: X LinkedIn Hacker News Email Copy link

Third-party repos we don't own. AI-written use cases can be wrong. Disclaimer