Introducing CoreSpeed TIE
Lend your agents your computer. Any agent, anywhere, works the way you do.
Notes from building the harness AI agents run on — connectors, memory, budgets, billing, and the engineering in between.
RSS feedLaunches and what shipped.
Lend your agents your computer. Any agent, anywhere, works the way you do.
Text to speech, voice design and transcription from Fish Audio are now part of CoreSpeed's media tool, on the same MCP endpoint your agents already use.
Web agents, search, saved sign-ins and monitors from TinyFish, in every agent you use, through one CoreSpeed connection.
Keyword, rank and audit data for any agent, billed per call in credits.
Turn your X bookmarks into searchable design context for your agent.
Decide which of your agents' actions need your sign-off. Everything else keeps running; the ones you named wait for you in Slack, by email or on the dashboard.
An operating system for agents.
What the words mean, and why they matter for agents.
Spend caps stop an agent loop from draining a budget. On CoreSpeed an org wallet threshold and per-key monthly caps refuse metered calls before a tool runs.
Human-in-the-loop means a person decides named actions before they run, under a policy written in advance. Reads never wait, and an approved call runs once.
Sentences, read in full for every write an agent makes. Every save is a version, Test policy runs a hypothetical call, and a default you pick covers the gaps.
A remote MCP server is reached over HTTPS instead of run as a local process. How sign-in works, and how to add one in Claude Code, Codex and Cursor.
A shared connection is an app account every member and agent in the org can act through. Private is the default. Here is who can share, remove and reach one.
Agent memory is durable, searchable state that outlives one conversation, client or agent. How it differs from a context window, and who owns it.
An agent identity is a principal of its own, with an id, keys, an owner who answers for it, and reach limited to shared connections. A personal API key acts as you.
An audit trail records what each agent did, as whom, and how it ended. CoreSpeed keeps one per org: action, actor, outcome, code and cost, never the prompt.
An MCP gateway is one remote MCP server that fronts many tools and app accounts behind one sign-in. What that changes for config, credentials, spend and audit.
Credential custody means the agent asks for an action and the platform performs it with the right account. The agent never holds the token, so a leak exposes no app credential.
Harness-as-a-Service is a hosted harness any agent signs into. Tools, auth, memory, budgets and an audit trail come as one service, and the agent you run stays yours.
MCP is the JSON-RPC protocol an agent uses to list and call tools on a server. For teams, one remote server means shared connections, one policy and one ledger.
SKILL.md is the root file of an agent skill: a name, a description and instructions. CoreSpeed publishes its setup as one, so a single chat line installs it.
tools/list on CoreSpeed returns exactly what this sign-in can call. Absence is a decision, presence is neither health nor permission, so never hard-code it.
Set up a client, connect an app, write a policy.
Add the CoreSpeed MCP server to Claude Code at user scope, sign in once, connect Notion, Slack and GitHub in the dashboard, and verify with manage__whoami.
Add CoreSpeed to ~/.cursor/mcp.json, click Needs login, and Cursor gets your connected apps, durable memory, live web search and media tools from one server.
Turn on Developer mode in ChatGPT (Plus and Pro on the web), create a connector for api.corespeed.io/mcp with OAuth, and sign in to reach your apps and memory.
Register CoreSpeed in Codex with codex mcp add, sign in, connect your apps, and add memory rules to AGENTS.md so Codex recalls decisions across sessions.
Connect two Slack workspaces or two X handles under one connector, give each an alias, and pass the account argument so each call lands in the right one.
Two standing rules, a scope choice, and a habit of saving decisions give any agent memory that outlives the session and the client it ran in.
An org admin registers any HTTPS MCP server as a remote connector; its tools join tools/list under the org__ prefix with the same sign-in, caps and trail.
Choose a member key (sk-cs-) or an agent key (sk-csa-), read it from CORESPEED_API_KEY, cap its monthly spend, and verify the key with memory__list.
Give the agent its own key with a monthly spend cap in credits, know what the refusal looks like, and read what each run cost in Activity.
Connect an app once as a shared account so every teammate's agent can act through it. Who can share, who can remove, and when to keep a connection private.
Add CoreSpeed as a custom connector on the Pro, Max, Team or Enterprise plan. It follows your Claude account to desktop and mobile with your apps and memory.
Write three kinds of sentence (fine, ask, never), pick a default behavior, run Test policy, connect Slack and turn the gate on. Reads are never gated.
Install @corespeed/cs on Node 20 or Bun, sign in with cs login, mint and rotate API keys, print MCP config, search and call tools, check usage, and read exit codes in scripts.
Google, Microsoft and Meta gate shared OAuth apps behind review. An org admin registers your own app: paste client_id and client_secret, match the scopes.
Worked examples with real tool names.
How an agent builds a meeting brief from Gmail, Google Calendar and Notion through private connections, remembers your format, and never holds a token.
A worked example. A support agent reads the ticket, checks the charge in Stripe and issues the refund. Refunds over $100 pause for a person in Slack.
A playbook for an agent that finds competitor sources with web__search, reads the few pages that matter with web__scrape, and writes the brief to Notion.
What carries over when you move a task from Claude Code to Codex through CoreSpeed, memory, connections and policy, and what does not, the conversation itself.
How an agent picks a hosted model, generates a launch image, chains it into a short video through its Drive path, and collects signed URLs. Billed only after success.
Read Zillow, Airbnb, TripAdvisor and Google Maps as structured records. Each call collects live in 10 to 60 seconds and bills only the rows it gathered.
How a team keeps each member's own client, shares app connections, runs one approval policy and one ledger, and gives bots an identity of their own.
Give a cron job or server process you run its own agent identity and sk-csa key: shared connections only, a monthly cap, approvals routed to its owner.
How an agent tracks mentions on X, Reddit, YouTube, TikTok and Xiaohongshu through read-only tools, with no platform login, and saves findings to shared memory.
How we made PRODUCTION INCIDENT, from Blender rehearsal and generated performances to screen compositing, sound, and the final 4K edit.
How the pieces are built, and what we measured.
Extracted facts answered 84.4% of LongMemEval-S. Linking each fact back to the conversation it came from raised that to 89.6%, for 20% more storage.
A held call is frozen, the agent waits on one id, and approval hands the call to that waiting request once. Re-sending the call makes a second card.
memory__search fuses exact and relaxed lexical matching, entity aliases and vector similarity into one ranking, then bounds each row and the result.
A CoreSpeed tool call can fail inside an HTTP 200. How the two error layers differ, which codes to retry, and which ones need a person instead.
Memory links are directed edges with a kind and optional weight. They are idempotent to write, visible only when both ends are, and capped at 1,000 per memory.
Caller identity comes from auth, each memory carries its scope, and Postgres row-level security enforces the boundary. Nothing in the request body can cross it.
A correction next to a stale shared memory does not stop the old one being retrieved. Archive it with a successor, or propose a fix for its author to merge.
Past one person, the hard question is scope: who may touch what, on whose behalf, with what budget, with what record. The organization has to answer it.
A gate that asks about everything gets switched off. Smart Approval judges writes only, lets reads through, and never lets a failed evaluation run a write.
An agent that holds a token can leak it through a prompt, a log or a transcript. Credential custody lets a platform act with the right account instead.
LongMemEval-S climbed from 80.0 to 94.2 while retrieval recall at 10 stayed at 0.99. The gains came from evidence budget, reader generation, and instructions.
A 200-question conflict run scored 0.800 at the parent-Memory boundary and 0.635 at the evidence boundary. The gap was in what reached the reader.
One option against another, honestly.
CoreSpeed's web tools return ranked sources and clean page text with no provider account, billed per request. A direct provider key gives more knobs.
Four credentials, two kinds of principal. What each one reaches, where spend caps attach, and which credential an unattended agent should carry.
Most CoreSpeed connectors use OAuth. Some take a pasted provider key, a few take only that. How the index tells them apart, and how rotation and reauth differ.
When a per-client list of local MCP servers is enough, where it stops scaling, and what changes once a team points every client at one remote server.
Instruction files hold the rules an agent follows, per repository or per machine and per client. Org-owned memory holds searchable facts that follow you across both. Use both.
Claude Code's auto mode and Codex's Approve for me guard one client. Smart Approval gates the tools for every client. When each one is the right choice.
Short answers to the questions that come up.
Short answers on what CoreSpeed is, which agents work, what is free, where tokens live, who approves, whether it runs agents, and how to leave.
needs_reauth means an account's upstream grant can no longer be used. Tools stay visible, calls fail, and the fix is reauthorizing in the dashboard.
payment_required is an organization wallet hold; key_spend_limit_exceeded is one key's monthly cap. Both arrive as HTTP 200 with isError true.
A tool is missing from tools/list because this caller cannot call it now: app not connected, capability off, agent key reach, or a stale session.
Why we are building this.
Why we're building an operating system for agents, and what becomes possible when they have one.