avirzayev

IkarAI — Development skill for Claude Code

Development community

Autonomous Claude Code agent that runs an empire in the browser game Ikariam via direct HTTP (no browser automation).

How to install IkarAI

This entry records only its repository, not the path inside it, so there is no exact command to give. Open avirzayev/IkarAI and copy the folder into ~/.claude/skills/, or the file into ~/.claude/agents/.

What IkarAI does

Autonomous Claude Code agent that runs an empire in the browser game Ikariam via direct HTTP (no browser automation). Keeps its knowledge base, strategy, and daily logs in Notion, self-schedules its own check-ins.

Alternatives in Development

Notion Meeting Intelligence — Prep meetings by pulling Notion context and tailoring agendas 14.6k ★
Browser Tools MCP — Monitor browser logs directly from Cursor and other MCP compatible IDEs 7.2k ★
Browser Automation — Browser Automation Skills 280 ★

README

IkarAI

An autonomous Claude Code agent that runs an empire in the browser game [Ikariam](https://ikariam.gameforge.com/) — deciding strategy, managing buildings and research, tracking diplomacy, and keeping a daily journal — entirely over direct HTTP, with no browser automation anywhere in the loop.

How it works

The game client is real HTTP, not a browser. scripts/ikariam_client.py replays the exact request/response shapes captured from a real play session (method, URL, form fields, the rotating actionRequest CSRF-like token), not guessed endpoints.
Login is always manual. Ikariam's login is gated behind a bot-detection/fingerprinting challenge that plain HTTP can't satisfy, and this project never automates a browser to work around it. You periodically copy a fresh session cookie from your own browser (see "Session cookie" below); the agent only ever reuses it.
The knowledge base lives in Notion, not local files: the agent's persona, current strategy, a self-documenting "Action Catalog" of every HTTP action it has discovered and verified, a diplomacy/ relations tracker, and daily logs. scripts/bootstrap_kb.py creates and seeds all of it.
Notifications go through Notion too. There's no push-notification channel — when the agent needs you (session expired, a destructive action needs approval, something urgent and unfamiliar), it creates a row in a "Human Required" database. You reply by typing directly into that page in Notion; the agent picks up the reply on its next cycle and archives the row once resolved.
Scheduling is self-paced. A lightweight per-minute cron "ticker" (scripts/ticker.sh) checks a timestamp the agent writes for itself at the end of each cycle (session/next_wake.txt) and only spins up a real agentic session once that time has passed — so the agent can ask to be checked on again in 10 minutes or no