Project Registry
In development
For developers whose tools must agree on which project they mean.
Not available to use yet.
Register once. Connect the right work.
Your checkout, repository reference and project name should point to the same project. Give apps and agents a reliable place to resolve that identity—without scattering folder mappings across tools.
Small foundation. Fewer wrong turns.
Make a folder mean something
Link a Git checkout on your computer to one project ID. Give usage records, conversations and code a shared point of reference.
Resolve before you act
Look up a project from a working directory or exact repository URL. Let an agent establish which project it is examining before joining evidence.
Keep the history connected
Archive a project and keep its links to local evidence. Preserve context when active work moves on.
Also in Project Registry
Use one project authority
Each project resolves to its one project record in Tasks. Avoid competing names and lifecycle states across apps.
Keep device paths local
Folder links stay on your device. Connect the tools without publishing your filesystem layout.
Build it into your tools
Call the same schema-checked operations through SDK, CLI, HTTP and MCP. Reuse project resolution wherever your agent works.
Your tools need to agree on which project you mean.
A registered project gives local paths and repository references a common identity. That lets usage and code tools join the right evidence.
Follow your AI work from allowance to implementation.
Start with recorded usage. Resolve the project, open its work sessions and trace the source behind a feature. One connected investigation, with evidence you can inspect.
AI CapacityKnow your usage and remaining allowanceProject RegistryResolve the project identity
AI EffectivenessFind the sessions behind the workProject UnderstandingExplore the code and possible impact
Project Registry
Register once. Connect the right work.
In development
Not available to use yet.