Pepkio Cloud
Getting started
Two steps: create a project and start a cloud server, then connect a remote agent over SSH. Pick Option A or B for step one — both require a Pepkio account.
Step 1 — Create project and cloud server
Choose Option A or Option B — use a local AI agent or the web console (GUI):
Provision and manage cloud servers from your laptop or desktop using Cursor, Claude Code, Codex, Grok, or any MCP + Agent Skills client.
Create your project, start a cloud server, and upload datasets directly in your browser with zero local setup.
Step 2 — Connect a remote agent
After your cloud server is Running, the project page shows Host / User. Complete Step 2 there — this page is a read-only mirror.
Before analysis, browse the public reference dataset catalog on www for curated names; agents read references/datasets/ inside the Cloud skill for versions and downloads. Public reference datasets
npx skills add pepkio/cloud --skill pepkio-cloud-remote
- 1
Add your SSH public key
Register a public key once in Cloud → SSH Keys (or paste it on the project page). The same key works for every project. Each project still needs its own Host alias — run that project's setup script or copy its SSH config.
- 2
Cursor — Connect via SSH
File → New Window → Connect via SSH. Choose this project's Host alias from your local SSH config (for example pepkio-cloud-alpha) — not a previous project's alias. Then open the project folder on the cloud server.
- 3
Install the remote Cloud skill
On the cloud server run `npx skills add pepkio/cloud --skill pepkio-cloud-remote`. Do not add-mcp the public HTTP endpoint with user OAuth — MCP is `pepkio-agent-runtime mcp` with credentials already at ~/.pepkio/cloud/credentials.json. Install Claude Code, Codex, or another agent on the box if needed.
When approvals appear
Starting a cloud server over budget, requesting large memory, deleting original data, or similar risky actions pause until you approve them in Cloud → Approvals.
Disconnect a local agent
Open Cloud → Local agents and revoke the connection. Tokens last about seven days.
API reference
Machine-readable contracts live in the console. Human setup is on Get started.
Troubleshooting
- The client never opened a browser
- Paste the URL-only MCP config if add-mcp missed your app, then use Needs login, /mcp, or mcp login. Ask the helper to retry if the login expired.
- The helper says it has no project
- Create a project in Cloud or ask the helper to create one, then run use_project before upload or workspace calls.
- An approval is waiting but nothing happens
- Open Approvals in the browser and approve or reject. The helper polls until you decide.
- A narrow connection cannot see other projects
- You approved one project only. Reconnect with all projects in your team, or stay on that single project.
- Only use the official Cloud host
- Approve access only on your real cloud.* URL. Phishing sites may ask for the same consent.