Your agent’s identity,
everywhere it runs.
Store credentials, identity, skills, CLI tools, MCP connections, and instructions once. Load them into Claude, Cursor, or any AI runtime with one command. Switch runtimes without reconfiguring.
Install the CLI
Terminal
$ curl -fsSL myagents.sh
/install.sh | bash
Via your agent
Tell your agent:
“Go to myagents.sh /setup and install myagents for me.”
Enterprise
Custom pricingEverything in Team, plus compliance, scale, and full control over your deployment.
Unlimited seatsSSO / SAMLOn-premise vault optionSOC 2 documentationSLA guaranteeCustom data retentionDedicated support
Billing is not yet active. All features are free during the early access period.
FAQ
Common questions
How is this different from just using a .env file?
.env files live on a single machine. Every time you switch to a new machine, give access to a teammate, or move to a different AI runtime (Claude → Cursor → Codex), you have to find, copy, and paste all your secrets again. With myagents you configure once and load everywhere with one command — no copy-pasting, no secrets flying around in Slack.
Does the AI ever see my raw API keys?
Public endpoints never expose raw credentials. When you use the CLI, credentials are retrieved server-side and can be cached locally in ~/.myagents/ with 0600 permissions so your runtime can use them without repeated copy-paste. Sessions can be revoked from the dashboard at any time, and credential fetches are logged.
Which AI runtimes does myagents work with?
myagents works with any runtime that supports SKILL.md — Claude Code, Cursor, GitHub Copilot, Gemini CLI, OpenAI Codex, and others. The CLI is runtime-agnostic. If your runtime can run a shell command, it can load an agent profile.
What happens if I want to switch from Claude Code to Cursor?
Nothing changes on the myagents side. Your agent's credentials, identity, and instructions are stored in myagents, not inside any specific runtime. Run `myagents load <slug>` in your new environment and everything is available instantly — same agent, same configuration.
Can my agent update its own profile?
Yes. The CLI exposes write-back commands so agents can push memories, update instructions, log activity, and sync integration metadata without a human in the loop. This is intentional — agents that maintain their own context stay useful across long-running workflows.
Is my data safe if myagents goes down?
Your agent's credentials are stored in Supabase Vault with encryption at rest. For resilience, the CLI caches the last loaded profile locally in ~/.myagents/ so your agent can continue working even if it can't reach the server. The cached profile includes credentials from the last successful load.
What counts as an "agent"?
An agent is a named profile — a slug like dev-assistant or invoice-bot — with its own set of credentials, identity, instructions, and integrations. You might have one agent per project, one per role (coding agent, research agent, comms agent), or one per client. There is no restriction on what an agent represents.
Do I need to install anything besides the CLI?
No. The CLI is a single self-contained binary — no Node.js, no npm, no runtime dependencies. One curl command installs it. For AI runtimes that support SKILL.md, myagents auto-installs the skill file on first login so your agent already knows how to use all the commands.