Promty Collector

Promty turns completed AI coding sessions into durable, reviewable Project Memory. The collector connects an explicitly selected Git repository to Promty, captures structured session activity from supported coding tools, and keeps a local queue so hook execution does not depend on the service being online.

Install

Requirements: Node.js 20+, Python 3.12+, and a Git repository.

Run the setup command inside the repository you want Promty to remember:

npx promty-collector@latest init --tool codex-cli --profile prod

For Claude Code:

npx promty-collector@latest init --tool claude-code --profile prod

Setup opens Promty sign-in, stores a revocable collector credential on your machine, installs repository-local hooks, and starts the background uploader. Check the installation with:

npx promty-collector@latest doctor --tool codex-cli --profile prod

The public setup supports Codex CLI and Claude Code. Other adapters are experimental and are not exposed by the setup command.

After Project Memory has been generated and reviewed, read it from the connected repository or expose it to an MCP-compatible agent:

npx promty-collector@latest context --profile prod
npx promty-collector@latest context --profile prod --format json

{
  "command": "npx",
  "args": ["-y", "promty-collector@latest", "mcp", "--profile", "prod"]
}

The MCP server provides get_project_context for the latest approved memory and search_project_context for owner-scoped search across approved memory nodes and safe file references. Both tools are read-only; search results never include raw prompts, responses, or patch bodies.

Collection and privacy boundaries

• Collection starts only in a repository where you explicitly run init.
• Promty receives session events needed to build Project Memory, including prompts, AI responses, file-change metadata, commit metadata, timestamps, and statuses.
• Sensitive prompt, response, and unified-diff text is encrypted at rest after upload. Local queued events remain on your machine until upload or removal.
• Project Memory is reviewable, and the MCP bridge is owner-scoped and read-only.
• External AI processing for Project Memory generation is optional and requires a separate confirmation. Do not submit secrets, credentials, regulated personal information, or third-party data you are not authorised to process.

Promty is not a general-purpose secret store. Initialise each additional repository separately, and remove hooks when you no longer want collection there:

npx promty-collector@latest uninstall-hooks --tool codex-cli

Learn more

• Collector documentation
• Privacy policy
• Project Memory architecture
• Agent Context and MCP guide
• Source code and issues

For account or privacy help, use Promty Support or email [email protected]. Report security issues privately to [email protected], not in a public issue.