@agentikos/os

Official Agentik OS CLI. Login, write host MCP config the same way /connect does, then call the same tools over HTTPS JSON.

Public package on npm. Same can() and secret-sauce hide as MCP.

Install

npx @agentikos/os --help
npx @agentikos/os install --host all
npm i -g @agentikos/os

From this repo:

npm run agentik -- --help

Local package install (after npm run build in this folder):

npm install -g ./packages/cli

Commands

agentik login                 # browser OAuth (existing /oauth/authorize + /oauth/token + PKCE)
agentik login --token agk_…   # user-scoped paid API key from /app/api (shown once there)
agentik connect               # login, then write Cursor/Claude MCP config
agentik install --host cursor
agentik os list
agentik call list_os
agentik call list_agents --arg osId=growth-os
agentik whoami
agentik logout

Auth and speed

Credentials live in ~/.agentik/credentials.json with mode 0600. The CLI never logs the raw token.

OAuth uses the live Agentik authorize and token endpoints. A long-lived key is minted on the server, bound to the signed-in user and workspace, hashed at rest, and shown once.

agentik call posts JSON to https://mcp.agentik-os.com/api/cli. That route uses the same identity check, can(), and tool dispatcher as MCP. It is faster because it skips the MCP JSON-RPC envelope. It is not a weaker permission model.

Builder OS stays hidden unless the Founder seat is signed in. The CLI also filters that id on the client. Install never writes a provider session.mcp.url.