DEDUPED Hot AI repos, turned into use cases Get 5 a day

How to approve or reject agent memories in the Graphicle app with Graphicle

Review the memories your agents propose and keep only the ones you approve.

Who it is forA tech lead or maintainer who wants control over what project knowledge agents store for future sessions.

The problemAgents can write notes about a project that may be wrong or out of date, and those notes can mislead later sessions.

The outcomeOnly memories you have reviewed remain, so later sessions start from project knowledge you trust.

What you need first

  • A local Git repository with the code you want to index
  • Homebrew, or the install script from the Graphicle README, to install the program
  • A terminal on macOS or Linux, or the Windows preview build for x86-64
  • A coding agent that supports MCP, such as Claude Code, Codex or Cursor (optional, for agent use)

Steps

  1. Set up Graphicle in the repository with graphicle setup.
  2. Run graphicle open to open the Graphicle app in your browser.
  3. Open the memories waiting for review and read each proposed memory with its linked code.
  4. Approve the memories that are accurate and reject the rest.
  5. Start a new agent session and check that approved memories appear in its context.

Prompt for your agent

In the Graphicle-AI/graphicle repository, run `graphicle open` for <repo-path> and review the memories waiting for approval. Expected output: a browser view of the graph, sources and memory with pending memories listed. Verify that a memory you approved is shown as reviewed and that a memory you rejected does not appear in new sessions.

Caveat. The README says a memory goes stale when the code it is tied to changes, so approved memories still need periodic review as the code evolves.

Share: X LinkedIn Hacker News Email Copy link

Disclaimer

Deduped lists open-source repositories that belong to other people. We do not own, maintain, audit, or vouch for any of them, and a repo appearing here is not an endorsement or a safety check. The use cases, steps, and prompts are written by AI and may be incomplete, outdated, or just wrong. Where a use case is marked "Seen in the wild", we link to public posts where someone described something similar, but we have not verified those posts and the use case itself is still our AI's own write-up. Use all of this at your own risk. Only run code, commands, or agents on systems and accounts you are authorized to use, and read the code and every command before you run it, especially anything that touches credentials, files, or the network. Nothing here is professional, security, legal, or financial advice. All trademarks and project names belong to their respective owners, and their use here does not imply affiliation. Content is provided as is, without warranties of any kind. Found a mistake, a safety problem, or something you want removed? Email [email protected] and we will look at it promptly. Full disclaimer page