Projects and prompt capture

One project per codebase

Each project watches its own folders, and its row shows when the repo is ahead of or behind origin. Pause monitoring, rename it, or add another project from the menu.

How a prompt finds its project

By the folder your IDE has open. Each project owns one or more folders, and the longest matching folder wins, so a repo nested inside another still files correctly. Prompts from folders no project owns are discarded.

Where prompts come from

• Cursor, Codex and Antigravity: read from the chat logs they keep in each project folder.
• Claude Desktop on macOS: captured through the Accessibility API and a listen-only Enter tap. Shift+Enter, chat switches, clears and slash-command picks are ignored.
• VS Code: prompts land in the same thread as the other tools.

Turning capture off

Monitor my IDEs is the master switch. Under it, each app can be turned off, and an app that is off does not save prompts.

To stop one project without touching the others, pause it from its ⋯ menu in the sidebar. Resuming re-seeds the change baseline, so the gap is not reported as one giant diff.

What is never indexed

Credential-shaped files are dropped unconditionally: env files, .pem and .key files, and anything named credentials or containing "secret". Dependency directories, lockfiles, minified bundles, binaries and files over 256 KB are skipped too.

Where it is stored

Prompts live in SQLite at ~/.openprompt/prompts.db and projects in a local JSON store, on your own machine. That store is not uploaded. The privacy policy covers the hosted features that do send data, and exactly what they send.

Finding a prompt again

Every captured prompt lands in one thread, with code blocks and file paths kept as they were typed. Filter by source or favourites, search, or check for file changes. A project’s prompts can also be exported to a file.

A record, not an audit log

Monitoring is best effort. OpenPrompt can miss a prompt, attribute one to the wrong project, or record a change late. Treat it as a record of your work, not an audit log.