Make a folder mean something
Bind a local Git checkout to a canonical project ID. Give usage records, conversations and code a shared point of reference.
Project RegistryHopper Labs
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.
Local app · Public launch is not configuredWays to try Hopper →
What makes it useful
Small foundation. Fewer wrong turns.
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 while retaining its local evidence bindings. Preserve context when active work moves on.
See it in the app
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.
Useful alone. Better together.
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.
Explore the connected workflow →A closer look
See what you can do.
The capability, the action, and what it means for you.
| Feature | What you can do | Why it matters |
|---|---|---|
| Project bindings | What you can doBind a local Git checkout to a canonical project ID. | Why it mattersGive usage records, conversations and code a shared point of reference. |
| Path and repository resolution | What you can doLook up a project from a working directory or exact repository URL. | Why it mattersLet an agent establish which project it is examining before joining evidence. |
| Lifecycle | What you can doArchive a project while retaining its local evidence bindings. | Why it mattersPreserve context when active work moves on. |
| Shared identity | What you can doResolve bindings to canonical Tasks project records. | Why it mattersAvoid competing names and lifecycle states across apps. |
| Local data | What you can doStore local folder bindings on the device. | Why it mattersConnect the tools without publishing your filesystem layout. |
| Agent interfaces | What you can doCall the same schema-checked operations through SDK, CLI, HTTP and MCP. | Why it mattersReuse project resolution wherever your agent works. |
6 capabilities
Practical details
Trying the experience
Explore the connected example with fictional data. Local app setup is separate.
Project Registry
Register once. Connect the right work.
Local app · Public launch is not configuredWays to try Hopper →