thinqOSAsk thinqOS
Menu

Platform

Connect one tool. Test one useful job.

Choose preview access, connect your workflow and verify the result in a fresh session.

Request access or sign in

thinqOS is in private preview. Use Request access if you are new. If your account already has access, use Sign in. A request is not an immediate account approval or a paid engagement.

Begin with a harmless sample and one result you can recognize. There is no need to upload your whole business to find out whether the first workflow helps.

Connect a coding assistant

For Claude Code or Codex, the thinqOS CLI can install the capture and recall hooks. It detects an existing thinqOS registration when available; you need valid preview credentials. Install uv using its official guide below, then install the thinqOS CLI. If uv reports that its bin directory is missing from PATH, run uv tool update-shell and open a new terminal. Run the installer from the environment where you use the assistant.

Use the commands below to connect those two clients and inspect connectivity. Review the installer’s output and restart or reconnect the client as directed. A successful connectivity check does not prove the next answer will recall the right fact.

Check memory end to end

State a simple test preference and ask the assistant to save it. Allow any asynchronous capture to finish. Open a new session and ask a question that should use it. Inspect the retrieved context and the answer.

Then correct the preference and repeat. Check deletion or retraction separately. This tests capture, retrieval and use, which are distinct steps.

Start a business workflow

Choose a repeated job, its manager and the source records. Explain decisions and exceptions. Test the first outputs against those records before allowing the agent to act beyond preparation.

Agree who keeps the instructions and connections current. Review time, error rates and verified completion alongside any time saved.

Run your own infrastructure

A separate self-hosting guide covers the installation token, Docker Compose, authentication, storage, updates and recovery. This is a different setup from connecting your coding assistant to the hosted service.

Your infrastructure team owns the operating environment. Review the prerequisites and release controls before installation.

Commands

Install the CLI (requires uv)

uv tool install thinqos

Connect Claude Code and Codex

thinqos install --client both

Check the connection

thinqos doctor
Continue exploring

Take the next step.

Run thinqOS on infrastructure you control.

Ask thinqOS

Answers grounded in the thinqOS website, with a page-search fallback
Current contextThe thinqOS website

What would you like to understand?

thinqOS tries to answer with cited sources. If it can't, you'll see relevant pages instead - never presented as an AI answer.

Your conversation stays in this tab for 30 minutes and is not linked to you across visits. Optionally keep your last question on this device for 30 days - that alone is not AI memory.