Troubleshooting

OSINT is a licensed product and needs to be activated before its tools unlock. Check that you have activated it, and see the Licensing page for what each license state means. If the app reports that the licensing service could not be reached, wait a moment and try again; if it says the license belongs to a different machine, it was activated elsewhere.

First check whether the tool is a network tool, its page tells you. A network tool needs a working connection, and if it talks to a service that expects your own key, that key has to be set in Settings. A local tool that returns nothing usually means the input was not what it expected; re-check the format the tool's page asks for.

Use the command palette rather than hunting through the sidebar. Start typing what you are after and OSINT fuzzy-matches across the whole library. If you are not sure of the exact name, type the subject, a domain, a hash, a username, and see what comes up.

Check which model the assistant is set to use in Settings. A local model has to be running on your computer for the assistant to reach it; a hosted model needs its connection configured. The assistant shows the tools it runs, so if it stalls mid-task, the visible call history tells you where.

The MCP server is off until you turn it on. Confirm it is enabled in Settings, then point your other tool at it. If it was working and stopped, check that the server is still enabled.

Cases live on your machine, so make sure you are on the same computer where you built the case. A finding only enters a case when you send it there, running a tool alone does not file its result. See Cases & dossiers.