Clipboard: something I copied isn't in history

Two usual suspects:

It was concealed. Password managers (including this app's own Password Manager) mark secret copies as concealed, and the Clipboard Manager deliberately skips them. Working as intended.
It looked like a secret. If sensitive-data handling is set to skip, things that match secret patterns (API keys, tokens, card numbers) are never saved. Switch the setting to flag if you'd rather keep them with a warning badge.

Also check that Developers Kit is actually running — capture only works while the app is alive (window or menu bar).

Clipboard: ⌃⌘V does nothing

Another app may have claimed the same shortcut. Check the other clipboard/launcher tools you run (Raycast, Alfred, Maccy…) and free up ⌃⌘V in whichever app you use less.

Database: connection fails

Work down this list:

Host and port right? localhost vs 127.0.0.1 matters to some servers; so does the port (5432 Postgres, 3306 MySQL, 6379 Redis, 27017 Mongo).
Is the server actually up? Check with Port Manager for local servers, or nc -vz host port in Terminal for remote ones.
Behind a firewall / private network? You probably need an SSH tunnel — most cloud databases don't accept direct connections from the internet.
Credentials. Re-enter the password in the profile; it's stored in the Keychain, so editing the profile is the way to update it.
Redis + TLS? Not supported yet — tunnel over SSH instead.

Database: "blocked by safe mode"

That's the safe-mode level doing its job. If the block is wrong for this connection, lower the profile's level (e.g. from Read-only to Confirm writes). If it's a production profile — maybe don't.

SQLite: file opens but writes fail

WAL-mode databases need their sidecar files (-wal, -shm). Grant the app access to the containing folder, not just the single database file.

Touch ID prompt doesn't appear / Mac has no Touch ID

Every Touch ID gate falls back to your macOS login password automatically. If neither appears, the auth dialog may be hiding behind another window.

Ports: process still there after Copy kill

You still need to paste and run the command in Terminal — Copy kill copies it, it can't run it (the sandbox forbids that; see Port Manager). If the process re-appears with a new PID, something is auto-restarting it (a watcher, launchd, Docker) — stop the parent instead.

Something else?

Email support@developers-kit.com with your macOS version and steps to reproduce.

Troubleshooting