☕ Hire Seemo in one line
No interview. No salary negotiation. No onboarding deck. Paste this into a terminal on macOS or Linux:
curl -fsSL https://kiqr.dev/install.sh | sh
On Windows, in PowerShell:
irm https://kiqr.dev/install.ps1 | iex
Then open http://127.0.0.1:4040, paste your website's address, and go make that coffee. By the time you're back, Seemo has read the whole site.
KIQR runs in the background and starts when you log in, so there is nothing to keep open. kiqr status says whether it is running, and kiqr start, kiqr stop and kiqr restart do what they say.
docker run -d -p 4040:4040 -v kiqr-data:/data --env-file .env ghcr.io/kiqr/kiqr
Put ANTHROPIC_API_KEY or OPENAI_API_KEY in .env, or a subscription token from claude setup-token as CLAUDE_CODE_OAUTH_TOKEN.
What you need: a Claude or ChatGPT plan you already pay for (through Claude Code or Codex), or an API key. That's the brain. KIQR itself is free.
Staying current: KIQR tells you when a new version is out, in Settings and in kiqr status. Click Update in Settings or run kiqr update. Running the installer again does the same. To have it install new versions on its own, as on a server, run kiqr update --auto on or switch on Updates in Settings.
✨ How it works
Think of Seemo as a senior marketer who joined this morning and read your whole website before the first meeting.
And it keeps a rhythm. Say "every Monday at 9, review last week and tell me what to change" once, and it does, every Monday.
Why on your machine?
- Your data stays yours. Everything is plain files in a folder on your computer. No KIQR account, no database in someone else's cloud. The one thing KIQR sends us is an anonymous usage ping (version, OS, which marketplace abilities);
kiqr telemetry off stops it (what it holds).
- Your AI, your bill. It runs on the Claude or ChatGPT plan you already have. No extra subscription.
- Teach it like a colleague. "Here's how we write a product update." Write it once in plain words and Seemo does it that way every time. Or install abilities from the marketplace: Google Analytics, Search Console, Plausible, WordPress, email and more.
👀 A look inside
💬 Try saying
What do you know about us?
What should we focus on this quarter?
Write two Facebook posts for Halloween, with images.
How did last week go?
The full walkthrough is in Your first project.
🛠 Contribute to KIQR
KIQR is one Rust binary: a daemon with the React UI embedded, a CLI that talks to it, and an MCP server so Seemo runs as a Claude Code session with KIQR's own tools and nothing else. Issues and pull requests are welcome.
Build from source
You need Rust (stable) and Node.js.
cd web && npm ci && npm run build && cd .. # the UI, embedded into the binary
cargo build
KIQR_HOME=/tmp/kiqr-dev ./target/debug/kiqr daemon # a throwaway home
npm run dev in web/ serves the UI with hot reload and proxies /api to a daemon on port 4040. Preview UI changes without a daemon through the demo build: npx vite build -c vite.demo.config.ts, then open web/dist-demo/index.html?demo.
For crawl tests, serve a folder of HTML files with python3 -m http.server 8099 and run ./target/debug/kiqr project add http://127.0.0.1:8099/ --watch.
Releases
Versions follow semver. Before 1.0, a minor release (0.x.0) brings new features and may change the ~/.kiqr layout or the API, and a patch release (0.x.y) only fixes things. To cut one from an up-to-date main:
scripts/release.sh minor --dry-run # see the version and changelog entry
scripts/release.sh minor # or patch, major, rc, or an exact 0.4.0-rc.1
The script bumps Cargo.toml, rebuilds web/dist, moves "Unreleased" in CHANGELOG.md under the new version (or lists the commits since the last tag when it is empty), commits Release vX.Y.Z, tags and pushes. The tag starts the release workflow, which builds Linux (x86_64, arm64, static musl), macOS (Intel, Apple silicon) and Windows (x64, arm64) and publishes a GitHub Release with the archives, SHA256SUMS and latest.json, the manifest the installers and kiqr update read. An -rc.N version becomes a pre-release that installs and updates skip unless asked for (KIQR_VERSION=v0.4.0-rc.1).
Find your way around
| Where | What |
|---|
crates/kiqr-core | Storage (files + git), events, the crawler, the profile, providers, Seemo's tools, the plan, metrics |
crates/kiqr-daemon | The axum API, server-sent events, the embedded UI, publishing, the scheduler |
crates/kiqr | The kiqr binary: CLI, kiqr daemon, kiqr mcp |
web/ | React + Vite + TypeScript |
abilities/ | The abilities that ship in the binary. Everything else lives in kiqr/marketplace |
seemo/PERSONA.md | Seemo's standing instructions |
Read docs/PLAN.md for the architecture and the decisions behind it, DESIGN.md before touching web/, docs/abilities.md for the ability format, and CLAUDE.md for the house rules.
This is the beginning of the README. Read the rest at the original. Read the full README ↗
