Project intelligence
Explore project relationships, architectural communities, evidence, and durable project knowledge inside Rope Notes.
Rope Notes can build a project-local model of the workspace so you can inspect how files, symbols, documentation, tests, tools, and subsystems relate. It is designed to help both the developer and the agent understand the project beyond the currently open file.
Explore the project graph
Open Embedded Graph from the project Explorer when the graph is available. The graph view supports:
- Search across files and symbols.
- Reports for project health, hubs, communities, and architectural clusters.
- Path exploration between related nodes.
- Follow-up neighbors and repository-scoped queries for larger workspaces.
- Export to HTML, GraphML, Cypher, a graph bundle, or a readable graph wiki.
The graph is built locally and stored with the project under .rope_notes/graph/. It can scan Dart, Rust, Markdown, text, links, and project metadata. Web builds do not provide native graph scanning.
Ask with evidence
Project intelligence brings together the evidence that is available for the question:
- Embedded graph relationships and repository scope.
- Dart analyzer facts and current diagnostics.
- Read-only Git status and history.
- Project Markdown documentation.
- Optional on-device cognitive memory.
- User-approved project knowledge.
- Saved sessions, plans, and change-set evidence when present.
Reports identify their sources, freshness, confidence, uncertainty, and evidence that was not consulted. A missing graph or analyzer result is shown as unavailable rather than treated as proof that no relationship exists.
Keep project knowledge with the code
Project knowledge is for decisions and intent that source extraction cannot reliably infer. Capture requirements, invariants, terminology, hazards, procedures, and rejected alternatives, then review their status and link them to files, symbols, tests, commits, graph nodes, sessions, or plans.
Knowledge is user-approved project data. It is stored locally, written safely, and kept separate from observed code facts so the agent can distinguish “the code says this” from “the project owner decided this.”
Privacy and limits
The graph and evidence services do not require a hosted model. An agent request may use the available project context according to the active provider and workspace permissions. Review the Privacy Policy and the provider boundary before enabling cloud work.
Graph relationships are an aid for navigation and investigation, not a replacement for reading the code or running validation. Unsaved editor buffers, stale indexes, unavailable adapters, and unrun tests remain distinct in the evidence shown to you.
Related guides
- Mobile workspace — Project Pulse exposes graph/index availability and architecture signals on Android.
- AI agent — Ask questions, plan, execute, and review proposed changes.
- Language server — Dart diagnostics and navigation.
- Preferences — Configure project and agent behavior.