Connect GitHub and keys once. Every agent can use them.

Add GitHub, Vercel, API keys, tools and skills to Connections once, and your agents on the machines you choose can use them, sealed so only your machines can unlock them.

  • In the web appStarter and Cloud

With Miko Starter and Miko Cloud

How it works.

  1. Open Connections

    Open Connections in the top bar, or from the menu at the top right on a phone, and press Connect.

  2. Add it once

    Sign in to GitHub and pick repositories, paste a Vercel access key, add an API key under the name agents see, or add a tool or a skill.

  3. Choose where it goes

    It goes to All my agents, unless you narrow it to a project or pick which of your machines can use it.

  4. Agents pick it up

    New agents get it right away, and running agents after a restart. If an app can't use it yet, its card says so.

What you can connect

GitHub, Vercel, keys, tools and skills.

Press Connect and pick what to add. You add each one once, and it's there for every agent you choose.

  • GitHub: Miko shows a code, Open GitHub copies it, and you sign in on GitHub and Pick repositories. Or press Use a token instead and paste a fine-grained access key. Agents can then push with git.
  • Vercel: make an access key in Vercel's Account Settings, paste it and press Save.
  • A key: give it the Name agents see, for example STRIPE_API_KEY, ending like _KEY, _TOKEN or _URL. The key is never shown again; Replace key changes it.
  • A tool by its link, such as an MCP server at an https:// address. It may need no key, a key sent with each request, or a link that holds the key itself. With a key, agents use the tool through Miko on your machine, and the key stays out of their reach.
  • More tools: add tools you start with a command, tools that ask you to sign in, and add-ons.
  • A skill: choose its folder, with a SKILL.md inside, or add it from a link, and agents on your machines get a copy. Skills work in Claude Code and hold up to 300 text files and 4 MB.

Which agents

You decide who gets what.

A new connection goes to All my agents. Narrow it whenever you like, down to one project or some of your machines.

  • When you add a key, you can pick one project under Which agents instead.
  • Later, open the connection and choose Only some places, or Turn off in… a project.
  • Under Machines, choose which of your machines can use it. On a computer, you can also drag a card onto All my agents, a project or an agent.
  • Giving a key or GitHub to more agents or machines asks for your passkey.

How it's kept

Sealed on your device.

Connections are sealed on your device. Miko's servers store them locked, and only your machines can unlock them.

  • If a connection changes without your account's confirmation, you see Connections need a quick check. Your machines keep using the earlier version until you press Review and confirm with your passkey.
  • If a skill lets agents run things without asking, Miko lists them and asks for your passkey.
  • Your data export lists your connections, with no keys and no passwords.

Good to know

Your AI accounts stay separate.

Your AI accounts aren't connections. Each one signs in under Accounts on each machine, in the app's own sign-in, and your sign-in stays on that machine.

  • Credentials already on a machine are never read or imported: each account signs in fresh, in its own private profile.
  • Sign-ins never move between machines. Use Sign in on… on the account card to add another machine.
  • Also separate: Miko Connect, which adds your own Linux server, VPS or PC to Miko with one command.
  • Connecting needs one of your machines online.

FAQ

Questions about Connect once.

More in the docs and the full FAQ.

Is Connect once the same as Miko Connect?

No. Miko Connect adds your own Linux server, VPS or PC to Miko with one command. Connect once is Connections: the GitHub access, keys, tools and skills your agents use. Both are part of Starter and Cloud.

Can I connect MCP servers?

Yes, with Starter and Cloud. Add one by its link: give it a name and its https:// address, answer “Does it need a key?” and press Add tool. You can also add tools you start with a command, tools that ask you to sign in, and add-ons.

Which apps can use a connection?

With Starter and Cloud, Claude Code, Codex and OpenCode can use GitHub, Vercel, keys and tools, and skills work in Claude Code. If one of your apps can't use a connection yet, its card says so, for example “Not in Codex yet”.

Can I add my Claude or OpenAI key as a connection?

No. Keys for an AI account can't be added as connections. Sign in under Accounts on each machine instead.

Can other agents on the same machine read my key?

On Ubuntu, Miko checks which agent asks before it hands a key over, so only the agents you pick can use it. This is on by default. Where that check is off, for example on Debian 12 by default, any agent on the same machine could read a key if it tried. Open a connection and look under What agents can see to see which applies.

Can I sign in to GitHub instead of pasting a key?

Yes. Choose GitHub: Miko shows a code, Open GitHub copies it, and you sign in on GitHub and Pick repositories. To paste a key instead, press Use a token instead and use a fine-grained access key.