Quick Start
Get your AI agent running in under 5 minutes.
This guide walks you through getting started with SkyKoi. By the end, you'll have a live AI assistant ready to chat.
Step 1: Create Your Account
Sign up at skykoi.com. Authentication is handled by Clerk — you can sign up with email/password or social login.
Step 2: Visit Chat
Navigate to the Chat page from the dashboard. On your first visit, SkyKoi automatically provisions a dedicated EC2 instance for you. You'll see an animated provisioning sequence:
- •🚀 Launching dedicated server — An EC2 t3.small instance boots in us-east-1
- •📦 Installing AI runtime — Node.js 22, AWS CLI v2, nginx, Koi runtime, and dependencies are installed via user-data script
- •⚙️ Configuring your agent — Agent config is generated with Bedrock model config, token auth, and workspace files
- •🔌 Starting gateway — The Gateway daemon starts as a systemd service
- •✅ Ready! — Your agent is live and ready to chat
💡Provisioning takes approximately 2–3 minutes. This includes EC2 boot, package installation (Node.js, nginx, agent runtime), TLS setup, and Gateway startup.
Step 3: Talk to Your Agent
Once provisioning completes, you're connected to your agent via WebChat over a secure WSS connection. The agent responds with the full power of Claude Opus 4.6 via AWS Bedrock, including access to tools like file operations, web browsing, shell commands, and more.
Your agent has its own workspace at /home/ubuntu/koi/ pre-seeded with:
- •AGENTS.md — Operating instructions and memory workflow
- •SOUL.md — Agent personality, tone, and boundaries
- •USER.md — Information about you
- •TOOLS.md — Tool-specific notes
- •IDENTITY.md — Agent name, theme, and emoji
Step 4: Explore
Your agent can do a lot out of the box:
- •Ask it to browse the web and research topics
- •Have it write and execute code
- •Let it manage files and projects in its workspace
- •Ask it to search the internet for information
- •Use it to manage AWS resources (via the instance's IAM role)
✅That's it! Your agent is live and responding. Explore the Architecture docs to understand what's happening under the hood.
