Docs/Add a tool or report a fix
Documentation menu

Reference

Add a tool or report a fix

PromptDust is open source (Apache-2.0): you can read every line, audit exactly what it does on your machine, and fork it. It is developed in-house by the PromptDust team, and to keep the project and the paid layers built on top of it under one copyright, outside code changes to the engine or interface are not accepted.

There is one thing you can contribute, and it is the most valuable one: coverage. Telling the team about an AI tool PromptDust does not map yet, or a detail it gets wrong. That is data, not code, and it is very welcome. Bug reports are welcome too.

The golden rule

Never include real conversation data, real secrets, or real personal data in an issue. When pasting tool output, redact paths and values. All fixtures are synthetic.

Report a tool PromptDust should map

PromptDust knows where an AI tool stores data from small declarative records. You do not write one. You describe the tool in an issue and the team adds it. Open a New definition issue with:

FieldNotes
Tool name and vendorDisplay name
Operating systemsmacOS, Linux, Windows
Storage pathsThe location (globs, ~, $ENV allowed), never the contents
Categorytranscript, cache, embedding index, config with secrets, log, attachment
Formatjsonl, sqlite, leveldb, plaintext, plist, json, binary, dir
Why it mattersOne sentence
How you confirmed itReal install (with app version and date), documented, or reported

Open a new-definition issue

How to safely find where a tool stores data

  • Do it read-only. Use ls, find, du, or a SQLite viewer opened read-only. Never edit or delete.
  • Look under the OS app-data directories: macOS ~/Library/Application Support/<app>/, Linux ~/.config/<app>/ or ~/.<app>/, Windows %APPDATA%\<app>\.
  • Note the structure, never the contents.

Confidence tiers

Coverage entries are labelled by how well the location is confirmed, and the tool shows the tier in its output:

  • verified. Confirmed on a real install (note the app version and date).
  • likely. Documented or strongly implied, but not personally confirmed.
  • unverified. Reported.

Report a fix

Spot a wrong path, a mislabelled format, or an entry that no longer matches the tool? Report a fix. Every catalog change is versioned.

Found a bug?

Open a Bug report issue with what happened, what you expected, and steps to reproduce. Running promptdust diagnostics gives a redacted, path-free bundle that is safe to attach.

Security issues

Report vulnerabilities privately, through the repository’s security policy, not as a public issue.

Spotted a mistake in these docs? Open an issue.