One settings block. Every laptop covered.

From sign-up to searchable in seven steps

Example: Acme uses Claude for Teams, and Rahul works there.

1. Acme signs up on StringHub

   Its admin creates the organisation, turns String Cortex on and gives it to the team.

2. The admin adds Acme’s Claude organisation

   Company → AI platforms. Only conversations of accounts in this organisation are kept.

3. The admin ticks the settings

   Company → Claude Code settings: install the plugin, make String Cortex compulsory if you want. Copy the settings that follow.

4. They go into Claude’s managed settings

   claude.ai → Organization settings → Claude Code → Managed settings. Once, for everyone. Within about an hour every laptop has the plugin.

5. Rahul connects once

   He makes his own Claude Code token in String Cortex and pastes it into the form Claude Code opens. It stays on his laptop and never reaches Claude.

6. He picks a workspace per folder

   In a new project folder Claude Code asks which of his workspaces it is for. One click, remembered for that folder and everything under it.

7. Every reply is saved and searchable

   Within seconds, in the right workspace. Rahul searches his own history; his admin sees the company’s.

{
  "extraKnownMarketplaces": {
    "string-tools": {
      "source": { …filled in for you… },
      "autoUpdate": true
    }
  },
  "enabledPlugins": {
    "string-claude-sync-plugin@string-tools": true
  },
  "env": {
    "STRING_CLAUDE_SYNC_URL": "https://cortex.stringhub.com",
    "STRING_CLAUDE_SYNC_REQUIRED": "1"
  },
  "permissions": {
    "allow": ["mcp__plugin_string-claude-sync-plugin_cortex"]
  }
}

• enabledPlugins turns the plugin on for everyone; employees can’t turn it off.
• autoUpdate brings new plugin versions automatically.
• The server address comes from managed settings, so it can’t be changed on a laptop.
• STRING_CLAUDE_SYNC_REQUIRED (optional) makes String Cortex compulsory: Claude Code waits until the person has connected and chosen the folder’s workspace.
• No secret in the block: you tick the options in the app and copy it. Each person connects with their own token.

How a reply gets from a laptop to search

Built for real networks: flaky Wi-Fi, sleeping laptops, servers being upgraded.

• Right account: before each prompt and after each reply the plugin notes which Claude account is signed in. Only lines between two notes of the same account are sent, to that account’s company.
• Stop hook: when Claude finishes a reply, the hook marks the session and starts a detached sender. Claude carries on immediately.
• Only new lines: the sender reads from where it stopped last time and sends complete lines, gzip-compressed, up to 4 MB per request.
• Server check: the server knows how far it has each session. Already have it? Ignored. A gap? It tells the laptop where to resume.
• Queue and workers: accepted chunks are queued and written by workers, one writer per session, so nothing is duplicated.
• Searchable: each prompt and reply gets an embedding for meaning search, and shows up live in the web app.

10:41:58 payments-api › 5f1c…: Waiting for a workspace for ~/code/payments-api. Claude Code will ask on the next prompt in this folder.
10:42:31 payments-api › 5f1c…: Sent 1.8 MB for rahul@acme.example (Acme).
11:07:40 Cannot reach server: timeout
11:09:02 payments-api › 5f1c…: Sent 96 KB for rahul@acme.example (Acme).
11:09:02 web-checkout › a9e0…: Sent 12 KB for rahul@acme.example (Acme).

Every message the plugin writes is plain language, so troubleshooting takes a glance, not a support ticket.