# AI use cases for Graphicle (Graphicle-AI/graphicle)

Repo: [Graphicle-AI/graphicle](https://github.com/Graphicle-AI/graphicle) | Use cases: 4 | Page: https://dedupedai.com/use-cases/graphicle-ai-graphicle/

Graphicle is a local Rust program that builds a code graph of your repository and keeps its docs, decisions and past agent sessions as searchable memory for coding agents.

This file holds every use case of this repo. Each one starts with a "## " heading and ends with its URL.

- Give your coding agent the code graph and project memory: https://dedupedai.com/use-cases/graphicle-ai-graphicle/connect-coding-agent-to-repo-graph/
- Find where a behavior lives by asking from the terminal: https://dedupedai.com/use-cases/graphicle-ai-graphicle/find-code-from-terminal-question/
- See what depends on a function before you change it: https://dedupedai.com/use-cases/graphicle-ai-graphicle/check-what-a-symbol-change-affects/
- Approve or reject agent memories in the Graphicle app: https://dedupedai.com/use-cases/graphicle-ai-graphicle/review-agent-memories-in-browser/

## How to give your coding agent the code graph and project memory with Graphicle

Repo: [Graphicle-AI/graphicle](https://github.com/Graphicle-AI/graphicle) | Difficulty: Intermediate | Time: 15 minutes | Basis: From the README

Install Graphicle once and connect your coding agents to the repo's code graph and memory.

**Who it is for:** A developer using Claude Code, Codex or Cursor on a repository who wants the agent to find code and decisions without searching blindly.

**The problem:** A coding agent has to search the repository from scratch each time, and project docs and past decisions are scattered across files and sessions.

**The outcome:** The agent calls Graphicle's tools and gets relevant code, docs and decisions as excerpts with file names and line numbers.

### Steps

1. Run `brew install graphicle-ai/tap/graphicle` (or use the install script from the README if you do not use Homebrew).
2. Open a terminal in your repository and run `cd your-repo`.
3. Run `graphicle setup` and read the list of files it changed; it backs each one up first.
4. Ask your agent: "use Graphicle to find where failed requests are retried".
5. Run `graphicle doctor` if the agent does not see the Graphicle tools.

### Prompt to paste into your agent

```text
In the Graphicle-AI/graphicle repository's setup, run `graphicle setup --yes` in <repo-path>, then list every file it changed. Expected output: a list of changed files and a confirmation that the Graphicle MCP server is connected. Verify by asking the agent to use graphicle to find <topic> and checking that the answer cites file names and line ranges.
```

### Caveat

Setup edits agent configuration files and Git hooks, so review the list of changed files it prints, and remember that `graphicle disconnect` undoes what it added.

Disclaimer: Third-party repos we don't own or vouch for. AI-generated use cases can be wrong: review everything and run at your own risk. Full text: https://dedupedai.com/disclaimer/

URL: https://dedupedai.com/use-cases/graphicle-ai-graphicle/connect-coding-agent-to-repo-graph/

## How to find where a behavior lives by asking from the terminal with Graphicle

Repo: [Graphicle-AI/graphicle](https://github.com/Graphicle-AI/graphicle) | Difficulty: Intermediate | Time: 15 minutes | Basis: From the README

Ask a plain-language question and get the matching code excerpts with file and line citations.

**Who it is for:** A developer new to a codebase who needs to locate the function behind a feature before making a change.

**The problem:** Searching a large repository by keyword returns many noisy hits, and it is slow to confirm which function really does the work.

**The outcome:** A short set of cited excerpts showing the file, line range and function name for the answer to the question.

### Steps

1. Install Graphicle and run `graphicle setup` in the repository, as in the quick start.
2. Run `graphicle ask "where is tax added to prices?"` with your own question.
3. Read each excerpt's file name and line range, starting with the first.
4. Open the cited file at those lines to confirm the code matches your question.
5. Run `graphicle open` to browse the graph and sources in your browser if you need more context.

### Prompt to paste into your agent

```text
In the Graphicle-AI/graphicle repository, run `graphicle ask "<question>"` inside <repo-path>. Expected output: an evidence list of cited excerpts, each with a file path, line range and symbol name. Verify by opening the first cited file at the stated lines and checking that the code answers the question.
```

### Caveat

With no model configured, `ask` shows only the evidence excerpts, so written answers need `graphicle config set model` with a model you choose.

Disclaimer: Third-party repos we don't own or vouch for. AI-generated use cases can be wrong: review everything and run at your own risk. Full text: https://dedupedai.com/disclaimer/

URL: https://dedupedai.com/use-cases/graphicle-ai-graphicle/find-code-from-terminal-question/

## How to see what depends on a function before you change it with Graphicle

Repo: [Graphicle-AI/graphicle](https://github.com/Graphicle-AI/graphicle) | Difficulty: Intermediate | Time: 30 minutes | Basis: From the README

Build the code graph and list the code that depends on a symbol before you edit it.

**Who it is for:** A developer or reviewer who is about to change a shared function and needs to know what else might break.

**The problem:** Changing a widely used function without knowing its callers can break code far from the edit, and manual tracing is slow.

**The outcome:** A list of the code that depends on the symbol, taken from the code graph, to guide testing and review.

### Steps

1. Install Graphicle and open a terminal in the repository with `cd your-repo`.
2. Build the code graph with `graphicle graph extract . --code-only`.
3. Run `graphicle graph affected "retry()"`, replacing retry() with your function.
4. Review each listed dependent and decide which ones to test or update.
5. Run `graphicle doctor` if the command reports a problem with the install.

### Prompt to paste into your agent

```text
In the Graphicle-AI/graphicle repository's code graph, run `graphicle graph extract . --code-only` in <repo-path>, then `graphicle graph affected "<symbol>()"`. Expected output: a list of code that depends on the symbol. Verify by opening two listed dependents and confirming they call or import the symbol.
```

### Caveat

The code graph covers calls and imports that the parser can see, so treat the list as a guide to check, not a complete proof of impact.

Disclaimer: Third-party repos we don't own or vouch for. AI-generated use cases can be wrong: review everything and run at your own risk. Full text: https://dedupedai.com/disclaimer/

URL: https://dedupedai.com/use-cases/graphicle-ai-graphicle/check-what-a-symbol-change-affects/

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

Repo: [Graphicle-AI/graphicle](https://github.com/Graphicle-AI/graphicle) | Difficulty: Intermediate | Time: 30 minutes | Basis: From the README

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

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

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

**The outcome:** Only memories you have reviewed remain, so later sessions start from project knowledge you trust.

### 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 to paste into your agent

```text
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.

Disclaimer: Third-party repos we don't own or vouch for. AI-generated use cases can be wrong: review everything and run at your own risk. Full text: https://dedupedai.com/disclaimer/

URL: https://dedupedai.com/use-cases/graphicle-ai-graphicle/review-agent-memories-in-browser/