Features

Everything your team said to Claude Code, ready to use again

A complete, searchable record of every Claude Code session in your company, with the controls an admin needs and none of the work for employees.

Ask Cortex Search Sessions Work board Home & profiles Stats Connect Workspaces Settings Organisation lock Access groups Roles Sync

Ask Cortex

Ask a question, get the answer your team already found

Search finds the messages; Ask Cortex reads them for you. Ask in plain words and get one answer written from your team’s Claude Code sessions, every point linked to the message it came from. Then ask the next question: the chat keeps its context.

Answers grounded in your sessions, with numbered sources you can open in place
Follow-ups keep the context: “and how did she test it?” just works
@ mention colleagues and # attach projects to ask about their work only
Only what the person asking may see: their own sessions plus their access groups
Your own Claude, OpenAI or Gemini key, chosen by your admin; secrets masked before anything is sent
Pick the model and how hard it thinks; see tokens and cost per answer
Each person’s chats are saved for them, and only them

What did we decide about retries for #payments-api webhooks, and why?Recall a decision, with the reasoning behind it.
Has anyone hit “ECONNRESET on large uploads” before? What fixed it?Don’t solve the same bug twice.
Summarise what @Ravi K. did in #mobile-app this sprint.Catch up on a colleague’s work, or write a handover.
Which approaches did we try for the slow dashboard query, and which one stuck?See what was tried before you start.
Show me the prompt that generated our OpenAPI client, I want to run it again.Reuse prompts that worked.

How did we fix the Redis lock timeout in #payments-api?

Ask Cortex

Under load the worker held the lock past its 30 s expiry, so a second worker took it 1. Rahul’s fix renews the lock every 10 s and fences each write with a sequence number 12. Priya later tuned the TTL for the queue workload 3.

1Rahul S. · payments-api · 3 weeks ago 2Rahul S. · payments-api 3Priya K. · infra-terraform

And how did @Priya K. test it?

Ask Cortex

She added a test that pauses the first worker past the TTL and checks that its late write is rejected 1

Ask a follow-up… @ a colleague, # a project

# payments-api@ All employees claude-sonnet-5-5

Find it by what it meant, not just what it said

Type a question the way you would ask a colleague. Hybrid search blends keyword matching with semantic search, so “redis lock expiry” finds the session that talked about “a second worker grabbing the mutex”.

Hybrid, meaning-only or keyword-only modes
Filter by project and by who said it: the person or Claude
Claude’s replies show the prompt they answered
“Open in chat” jumps to that exact message in its session
Quick search with ⌘K: jump to a person, project, session or page by name
Embeddings are made on the server itself; search never calls an outside AI (Ask Cortex, below, is the opt-in exception)

how did we fix the redis lock timeout?

HybridMeaningKeyword

RSRahul S.payments-apiClaude3 weeks ago0.92

The worker held the lock longer than its 30 s expiry under load, so a second worker took it. Fix: renew the lock every 10 s and fence the write with a sequence number…

PKPriya K.infra-terraformPrompt2 months ago0.81

Our Redis keeps evicting session keys at peak. Can you check maxmemory-policy and suggest settings for a queue workload?

AMAli M.web-checkoutClaudeJun 120.74

Wrapped the cart update in a short-lived lock keyed by cart id, released by token so a slow request can’t free someone else’s…

Sessions

Read every session like a clean chat

Projects on the left, sessions inside them, the whole conversation on the right. Prompts and replies, without the tool-call noise.

Open up to three sessions side by side
Give projects friendly names that show everywhere
Projects list with tokens and cost, sortable and searchable
New messages appear live while you read

Work board

Every session as a piece of work

See what your team is building with Claude the way you plan work: a table, a Kanban board or a calendar. Click any card and the session opens.

Group the board by status, last active, person, organisation, project, tag or model
Status comes from activity by itself: in progress, paused, wrapped up. Nobody has to move cards
Calendar by month or week, on the day a session started or was last active
Search and filters by person, project, organisation and dates in one compact bar
New sessions slide in live without losing your place

Home & profiles

A home page for every role, a profile for every person

Everyone starts on a home page made for them, and every person has a profile that shows their Claude work at a glance, with an activity calendar of the last year.

Admins see the company at a glance: recent sessions, active projects, people and cost
Employees see their own week first, and what their teams share with them
Profiles: sessions, prompts, active days, the projects someone works in most, and a 52-week calendar
Colleagues appear only as far as the projects your groups share with you

Stats

See where AI time and tokens go

Messages per day, the hours people work with Claude, and token use per project, person, model and session, with what it would cost at API list prices.

Input, output, cache write and cache read tokens, per day
API-equivalent cost per model, with prices you can edit
Filter by person and project (with search), organisation and any date range
People tab: Claude organisations, then employees, with the project each works in most
For company admins: how much storage the company’s data takes, for the same filters

Connect

Each person connects once. No approval queue.

People make their own Claude Code token in String Cortex and paste it into a form that Claude Code opens. From then on their conversations follow every reply, under their own name.

The token goes to the plugin, never to Claude, and never appears in a transcript
Bound to one Claude account: a copied token can’t be used for another
Access renews by itself; a new token or a revoke stops the old one at once
Two Claude accounts on one laptop? Each connects to its own company, and their lines never mix
See every connected Claude account, and when it was last used, in one place

Claude Code~/code/payments-api

> why does the refund job retry twice?

String Cortex: rahul@acme.example (Acme) is not connected yet. A form will open to enter your Claude Code token.

Connect String Cortex for rahul@acme.example (Acme). In String Cortex, open your avatar → Claude Code token → Generate. Paste the token below. It stays on this laptop and is not sent to Claude.

Claude Code token sct_••••••••••••••••••••••••

String Cortex: Connected as Rahul at Acme for rahul@acme.example (Acme). Your token stays on this laptop.

Workspaces

Every folder lands in the right workspace

Teams, clients or products each get a workspace. The first time someone works in a new project folder, Claude Code asks which one it belongs to. One click, and it is remembered.

Asked once per folder, and its subfolders follow
Picked up by itself when the person’s earlier conversations of that folder already went to one
Until it is chosen, the conversation waits on the laptop; nothing is lost
Change it later by simply asking Claude

Claude Code~/code/payments-api

> add retries to the webhook sender

Workspace

Which String Cortex workspace should payments-api use?

❯ 1. Payments 2. Platform 3. Mobile app

Saved: ~/code/payments-api and its subfolders will use Payments.

Sure. The sender lives in webhooks/send.ts; I’ll add a retry with backoff…

Claude Code settings

Tick what you want. Copy. Done for everyone.

String Cortex builds your company’s Claude Code managed settings from a few ticks. Your Claude admin pastes them once, and every laptop gets the plugin within about an hour.

Install the plugin on every laptop, with your server’s address; people can’t turn it off
Make String Cortex compulsory: Claude Code waits until the person has connected and chosen the folder’s workspace, and their first message goes through right after
Allow the plugin’s tools without asking, so nobody meets a permission prompt
No secret inside: each person connects with their own token

Install the plugin on every laptopAdds the plugin and this server’s address.

Make String Cortex compulsoryConnect and choose a workspace before using Claude Code.

Allow the plugin’s tools without askingNo permission prompt the first time.

Managed settingsCopy

{
  "enabledPlugins": { … },
  "env": {
    "STRING_CLAUDE_SYNC_URL": "https://cortex.stringhub.com",
    "STRING_CLAUDE_SYNC_REQUIRED": "1"
  },
  "permissions": { … }
}

Organisation lock

Only your company’s Claude accounts get in

Each company lists its Claude organisation ids. Conversations from any other Claude account, like someone’s personal plan on a work laptop, are never stored.

Checked on every push: the Claude account and organisation signed in at each turn
Switching accounts mid-day? Each turn goes only to its own account’s company; a turn with a switch in it is not sent
Refused attempts are listed, with “Add this organisation” in one click
Several organisation ids per company when you need them

Claude organisationsaccepted for Acme

xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx Acme · Teams

Refused recently

2 attempts from organisation yyyyyyyy-yyyy-… by neha@acme.example, today 09:14.

Add this organisation

Access groups & tags

Share the right projects with the right people

Employees always see their own conversations. Access groups add more: every project in the company, hand-picked projects, or every project carrying a tag.

Give an employee tags, and every project they work in carries them, now and later
Groups by tag stay live: tag a project and it joins the group at once
One employee can be in several groups; their access adds up
Chats, Search, Projects and Stats all follow it, so search spans exactly what they may see
Employees can take a tag off their own project; admins manage tags on any project

Access group	Gives	People
Backend	#backend #payments	6
Leads	All projects	3
Mobile	2 chosen projects	4

Employee	Can see
RSRahul S.	Own Backend #backend
PKPriya K.	Own Leads
AMAli M.	Own

Roles

The right view for every person

Employees see their own conversations plus whatever their access groups give them; company admins see and manage the whole company. What each role may do is configurable.

What employees and company admins can see and do by default
What they can use	EmployeeEveryone using Claude Code	Company admine.g. your engineering lead
Chats, Search, Projects, StatsRead and search conversations	Own + their access groups	Whole company
AccountsClaude users and organisations	Not included	Their company
Claude Code tokenConnect their own Claude Code	Their own	Their own
Company settingsClaude organisations, Claude Code settings, AI answers	Not included	Their company
Sync statusProjects as saved, live log	Not included	Their projects and log

Sync

Reliable by design, invisible by default

The plugin is built so nobody ever has to think about it: not the employee, and not your admin.

Never in Claude’s way

After each reply a hook hands off to a detached background process and returns at once.

Only what’s new

Just the lines added since last time, gzip-compressed, in chunks of up to 4 MB.

Catches up by itself

Server down or laptop offline? Lines wait locally and go with the next reply of any session.

No duplicates, no gaps

At-least-once delivery. The server ignores what it already has and asks for anything missing.

Resumes where it stopped

Each transcript’s position is kept on the laptop; if that’s lost, the laptop simply asks the server.

Every project, every session

Works across all of a person’s projects. Nothing is added to any repository.