Connect one tool. Test one useful job.

Put an agent on your website

Use the website embedding guide at /embed-your-agent for guided owner setup, complete copyable snippets, published-site checks and platform paste locations. Choose an agent you own; visitors use its real Mind and configured capabilities.

Pick your path

These steps are not a sequence, and most people need only one of them. Everyone starts at access. After that: connect Claude if you want it to remember you across chats; connect a coding assistant if you want your project decisions to survive between Claude Code or Codex sessions; start a business workflow if you want an agent preparing a recurring job for your approval.

Each path below has its own prerequisites and its own way to check that it worked. Read the one that matches your job and skip the rest.

Request access or sign in

Private preview means one thing: you cannot sign yourself up. Access is approved first. It is not a cut-down trial or a sandbox. Some parts of the platform are more mature than others, so we agree the workflow you will use and check that it works for you.

The trade is that it is early and it moves. The product changes daily, so expect rough edges and behaviour that shifts under you. The trust page and the terms set out plainly what that means for your data before you put anything real into it.

Use Request access if you are new, or Sign in if your account already has access. Then 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 Claude

Claude on the web, desktop and mobile reaches thinqOS as a connector. There is nothing to install. You need a thinqOS account with preview access.

In Claude, open Customize, then Connectors, then Add, then Add custom connector. Name it thinqOS and set the server URL to https://app.thinqos.com/mcp. Select Add, then Connect. A thinqOS window opens: sign in, review what Claude is asking for, and select Authorize. Claude lists the thinqOS tools once the connection is made, and you can revoke it at any time from your thinqOS settings.

Then try it. Ask Claude to remember something true about you or your work, such as the hours you keep or a rule you follow. Open a new chat and ask a question that depends on it, for example what your rule is for a given case, or to draft a message in your usual style. Claude calls thinqOS for questions about you and your work, and answers general questions on its own.

Connect a coding assistant

First, decide which thinqOS install you are connecting to. Using the default hosted app? No flag is needed; the connect command below uses it automatically. Using an existing installation your organization runs instead? Add --base-url <your-install-url> to the connect command (or set the THINQOS_BASE_URL environment variable) so setup, doctor, and verify all point at the right place. Before sending any key, each command first confirms that URL is a real, reachable thinqOS install and tells you plainly if it is not.

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.

Connecting to more than one thinqOS install from the same machine? Every install is labeled. See thinqOS accounts list and thinqOS switch <label> in the CLI README.

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

The first supported workflow is buyer follow-up, ready for approval: one Sales and Key Accounts agent prepares a sourced account brief and reply draft, and a person on your team reviews and sends every reply. Request access and tell us about the queue you want help with; the For business page describes the pilot.

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.