Open source · Apache-2.0 · Experimental release · GitHub App integration
Find the projects that remember.
Sign in with GitHub and install the DIP GitHub App on the repositories you choose. DIP Web discovers repositories with a committed .dip/events directory on their default branch, then brings their project history into one workspace.
Access follows your GitHub account and the App installation. Connecting an organization does not give every user access to its private repositories.
Read the layers of the work.
Use a task list or board, filter by status, review priorities and due dates, and inspect recorded activity and commits. Requests, plans and handoffs help reconstruct how a feature evolved as people and agents worked on it.
This is the archaeology of AI-assisted development: context you can return to when code has changed faster than you could follow. Dedicated user and model attribution remains a roadmap direction.
Continue the work through GitHub.
With approved write access, create and update tasks on a selected branch. Changes append DIP events through Git commits. Concurrent changes and branch protection can prevent a save; the app does not force an overwrite.
The App requests repository Contents permission. Application code limits task writes to new event files, but GitHub’s permission covers repository contents more broadly. Browser edits cannot mark a task verified.
Know where your data lives.
Committed project history stays in GitHub. Provider tokens stay on the server in encrypted, expiring sessions. Account-scoped snapshots, preferences, notes and favorites are cached in your browser; sign out on shared devices to clear that account’s cache.
DIP Web cannot see uncommitted local work, coordinate live local ownership or run your project’s checks. Recorded evidence describes a past check, not a new verification of your current code.
One record. Two ways to work.
Use DIP locally to capture activity and coordinate agents. Use DIP Web to explore and update the history committed to GitHub.
Inspect the source before you deploy.
The repository includes setup guidance, architecture notes, tests and a public release review. It is experimental software; inherited dependency advisories are documented and need review before a new production deployment. A source release does not automatically deploy the hosted app.