Claude Code and Codex for teams, on one set of rules
A team of agents on CoreSpeed is every teammate's own client, Claude Code, Codex, Cursor or claude.ai, signed in to one organization. Shared app connections, shared memory, the approval policy, spend caps and the activity trail belong to the organization, so the same rules hold whichever agent makes the call. A bot gets an identity of its own.
The job. Let each teammate keep their own agent while connections, memory, approvals, budgets and the trail are the organization's.
Paste this into Claude Code, Codex or Cursor
set up https://corespeed.io/SKILL.md (read it raw, e.g. with curl), then tell me which app connections in our organization are shared and which are mine, and which agents exist and who owns them.One prompt.Three steps.
Set up first. Each teammate adds CoreSpeed to their client once per machine and signs in to the same organization. An admin writes the approval policy in Dashboard → Approvals; a prompt cannot set it.
Everyone signs in once
Each teammate adds CoreSpeed to Claude Code, Codex, Cursor or claude.ai and signs in to the same organization.
Share what the team uses
Connect GitHub and Notion as shared, and keep Gmail private. An admin installs the Slack or Linear app for the team.
Give the bot its own key
Create an agent for the nightly job and mint it a capped key. Its held writes come to you, its owner.
The tools it calls
manage__whoami· Confirm which organization you are inmanage__accounts_list· Sort the connections: shared and yoursmanage__agents_list· List every agent and its owner