Tracemoor

Maintaining context

projectdocs, Docs View, sharing an exploration, reference projects.

  • projectdocs: bug reports, reviews and notes as Markdown files, grouped in phases and anchored to code symbols.
  • Phases and entries: You create phases and entries in the projectdocs dashboard.
  • Anchors: An anchor links a projectdocs entry to a code symbol (a function, a class, a type) or to a git commit.
  • Bug reports: A bug report is a projectdocs entry of type bugreport.
  • The projectdocs dashboard: The dashboard shows the projectdocs of the open exploration: the masterplan, the phases with their entries, a timeline and a search.
  • projectdocs and the AI: The AI in the chat panel reads and writes projectdocs through the projectdocs_* tools of the Tracemoor MCP server.
  • Docs View: The Docs View reads and edits Markdown documents in a WYSIWYG editor: architecture notes, guides, a README.
  • Share an exploration: An exploration is a folder next to the project.
  • Reference projects: A reference project is another project that Tracemoor has already analyzed and that is attached to the current exploration for lookup.
  • Attach and manage references: Reference projects are managed in Project Settings, section
  • Calls between linked projects: A call graph of one project ends where a call leaves the process: an HTTP request, a message to a webview, a command, a Tauri invoke.
  • Compare states and reference sets: The dialog Reference Sets has two tabs.
  • References and the assistant: Each reference project that is set up on this machine gets its own read-only tool server in the chat.