Walkthrough
How to make a coding assistant remember repo conventions with Memnode
This is the clearest first Memnode workflow: teach the agent one repo convention, recall it in a later session, and inspect the lineage so the memory is not a black box.
Why this use case works first
- The pain is obvious: coding agents forget repo-specific rules across sessions.
- The proof is short: record, recall, lineage.
- MCP puts Memnode directly inside the workflow where the pain already lives.
What the agent should remember
- Validation conventions like `use Zod in the route layer`
- Test rules like `integration tests hit a real database`
- Deploy rules, API conventions, and service boundaries
Fastest path: local MCP in Claude Code
memnode install-mcp --target claude-code --verify > remember that this repo uses Zod for request validation > what do we use to validate request payloads? > show lineage for that memory
That is the fastest believable demo because the agent, the memory tool, and the repo all live in the same workflow. It is also the easiest distribution surface through MCP listings and coding-agent communities.
Hosted path: shared memory across machines
import { MemnodeClient } from '@memnode/client'
const client = new MemnodeClient({
apiKey: process.env.MEMNODE_API_KEY,
})
await client.record({
entity: 'repo:memnox',
text: 'Use Zod in the route layer for request validation.',
source: {
kind: 'repo_convention',
path: 'app/api/users/route.ts',
},
})
const recalled = await client.recall({
query: 'How do we validate request payloads?',
entity: 'repo:memnox',
})
const lineage = await client.lineage({
nodeId: recalled.results[0].node_id,
})This is the path for hosted coding agents, shared team memory, or background jobs that need the same project conventions without relying on one local workstation.
What the proof should look like
recall[0].answer "Use Zod in the route layer for request validation." recall[0].why "Matched repo_convention memory from app/api/users/route.ts" lineage.chain observed -> canonical -> corrected
Why lineage matters
If the repo migrates from `yup` to `zod`, the problem is not only storing the new rule. The real problem is showing what changed, what superseded the old memory, and why the agent should trust the new one. That is the part black-box memory systems make hard.