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

How to keep project intent alive across agent sessions with living specs with Thinkrail

Let the agent read and maintain a connected graph of SPEC.md files beside your code.

Short answer: Open your repo with thinkrail ~/code/my-repo; then use the bundled project setup workflow to start the spec graph; ask the agent to record decisions and intent in SPEC.md files as it works. All steps.

Who it is forA team lead whose agents forget design decisions every time a new session starts.

The problemChat context disappears at the end of a session, so the next agent re-learns or contradicts earlier decisions.

The outcomeA graph of SPEC.md files the agent searches and updates through spec tools, rendered as a tree in the workbench.

What you need first

  • macOS, Linux or Windows (Linux needs the GTK and WebKit libraries listed in the README)
  • A git repository
  • JetBrains AI sign-in or a provider connected through pi's own auth
  • The GitHub CLI (gh) for PR workflows

Steps

  1. Open your repo with thinkrail ~/code/my-repo
  2. Use the bundled project setup workflow to start the spec graph
  3. Ask the agent to record decisions and intent in SPEC.md files as it works
  4. Browse the graph in the read-only Specs tool
  5. Start a new chat later and check that the agent reads the specs before changing code

Prompt for your agent

In JetBrains/thinkrail, set up living specs for <repo>: write SPEC.md files for the main modules with their purpose and key decisions, link them into a graph, and keep them updated as you implement <feature>.

Caveat.

Use this in your AI agent

Ask your agent

Using the Deduped MCP, get the setup steps for JetBrains/thinkrail and "Keep project intent alive across agent sessions with living specs"

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