Frequently Asked Questions

VibeMon is a pixel garden that grows while you code with AI agents. What Claude Code, Codex, Cursor and Gemini CLI do for you — edits, commits and passing tests — becomes energy for the garden. A sprout-headed jelly slime and its gardener friends spend that energy to plant, water, prune, harvest and build decor on their own, and you pick a focus: grow, decor or harvest.

Resting never hurts: nothing wilts and nothing punishes you.

Vibe coding is a term coined by Andrej Karpathy in February 2025 for a style of programming where developers prompt an AI agent in natural language and review the intent of the output rather than the syntax. VibeMon is built for this workflow: it reads what your agent does — edits, commits, passing tests — instead of counting keystrokes. See the full explainer at /learn/vibe-coding.

Developers who spend meaningful time working alongside AI coding agents and want a gentle, ambient reflection of that work. VibeMon is intentionally not a time tracker, productivity scoreboard or performance-review tool. If you run Claude Code, Codex, Cursor or Gemini CLI daily, the garden simply grows in the background.

WakaTime measures time spent in an editor and produces invoiceable reports and team dashboards. VibeMon watches what your AI agent does and shows it as a garden. The Vibe coding activity tab does show coding time, commits, tests, files, languages, AI tools and projects, but it is a mirror for you, not an invoice. A full comparison is at /compare/claude-code-companions.

Your coding is the only thing it needs. Activity from your AI agents — edits, commits and passing tests — becomes energy, and commits and passing tests count far more than plain edits. Your slime gardeners spend that energy to plant, water, prune, harvest and build decor on their own. See garden energy in the glossary.

A sprout-headed jelly slime and its gardener friends do the work. You pick their focus — grow, decor or harvest — and make the garden yours with ten slime colors, hats, outfits, weapons, eye styles and decor. See gardener focus.

Nothing bad. Resting never hurts: nothing wilts and nothing punishes you.

The garden has four seasons and weather. The more kinds of plants you grow, the more butterflies, bees and birds visit. Seasons are scenery, not a competition.

Every day of AI coding is planted as a tree in the record forest, and longer sessions grow bigger trees. It is your own record to look back on, and it can be shared as a forest card. See record forest.

A live view of your own work: coding time today, a 24-hour wave, your live agent sessions, and an alert when a session is waiting for you. It also shows commits, tests, files, languages, AI tools and projects, the last 7 days and a calendar. See vibe coding activity.

XP and species unlocks still exist as a shop currency in the app, but they are not what the product is about — the garden is. See XP for the history of the term.

VibeMon supports four AI coding agents: Claude Code (Anthropic), Codex (OpenAI), Cursor and Gemini CLI (Google). The installer detects the agents on your machine and configures the ones it finds. Each agent exposes its own set of events, so what VibeMon can see differs a little from tool to tool.

Yes. Activity is tied to your account, not to a single agent, so a Claude Code session and a Cursor session both feed the same garden.

The garden is fed by activity from supported AI agents. If you code by hand in an editor with no agent connected, VibeMon has nothing to count.

macOS and Linux use a shell script served at /install.sh. Windows uses a PowerShell script at /install.ps1. Both redirect to a pinned release in a public repository, so you can read exactly what you are about to run. The page that creates your command, /devices, shows the right one for your system.

No. VibeMon never uploads your source code, your shell commands or tool output. What the one-command installer syncs from your machine is metadata about the work plus the conversation: your prompts and the agent's replies, with secrets redacted. The same wording appears on /devices, the page that creates your install command, and the installer itself is open to read at /install.sh and /install.ps1.

Three kinds. (1) Metadata about the work: which agent, which session, and the activity that feeds the garden — edits, commits and passing tests. (2) The conversation: your prompts and the agent's replies, with secrets redacted. (3) Basic account details you supply (handle, display name, country, avatar URL). Never source code, shell commands or tool output.

Machines that still run the older VibeMon hook client send narrower event metadata instead — event type, timestamp, agent name, the path of the file being edited, repo, branch and commit SHA, and by default the first line of your commit message — and no prompt text. The new installer replaces that client only after its first successful sync.

Account and garden data are stored in Supabase (PostgreSQL) with row-level security policies that restrict each row to its owner. A public garden shows only what the owner chose to share: a display name and a summary of the record forest, with no project names, paths or code.

Yes. Account deletion is available in Settings inside the mobile app. It immediately revokes your login and removes your public profile from view. This is a soft delete — your account is marked deleted rather than the underlying activity records being physically purged right away.

Install has two parts. (1) Install the app from the App Store or Google Play. (2) On the machine where you code, run one command: sign in and open /devices, which creates a one-time token and shows the exact command for macOS, Linux or Windows. The installer then connects that machine to your account and configures the agents it detects. Full walkthrough at /setup.

It runs the installer from /install.sh (macOS and Linux) or /install.ps1 (Windows), which installs the AttemptDB connector, links the machine to your account with the one-time token, configures the AI agents it detects, and keeps syncing in the background. The token is used once; the device key it becomes stays on that machine. Existing local settings are preserved, and older VibeMon hooks are replaced only after the first sync succeeds.

This site does not publish prices. Plans and any current offers are shown inside the mobile app, which is the source of truth.

Yes. VibeMon has an Apple Watch app, plus iOS widgets and a lock-screen widget.

The phone app is on both iOS (App Store) and Android (Google Play). The Apple Watch app, iOS widgets and the lock-screen widget are Apple features; this page does not list a Wear OS app.

Three ways: a forest card, a public garden page at /u/<handle>, and a README badge for GitHub — copy the snippet from /badge. A garden is shown publicly only if you make it public.

Yes, in two places. The team workspace runs on the web at /workspace, with a demo at /workspace/demo, and public gardens can be viewed at /u/<handle>.

The Custom Slime API lets you define your own color palette for a slime; the shape stays VibeMon's shared slime. The reference is at /docs.