Frequently Asked Questions

A.VibeMon is a gamified coding companion for developers who use AI coding agents. Every time an agent like Claude Code, Cursor, Gemini CLI, or Codex edits code, fires a hook, or completes a task, VibeMon converts the event into drops (food) that feed a pixel slime. The slime grows through six stages and, at the Perfect stage, awards a badge before regrowing — turning the coding loop into a visible, tamagotchi-style progression.

A.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 specifically for this workflow — it treats each AI agent action as the unit of work rather than each manual keystroke. See the full explainer at /learn/vibe-coding.

A.VibeMon is for developers who spend meaningful time working alongside AI coding agents and want a lightweight, non-intrusive way to see their coding rhythm. It is intentionally not a time tracker, productivity scoreboard, or performance-review tool. Typical users run Claude Code, Cursor, or Gemini CLI daily and want ambient feedback on their session without logging into a dashboard.

A.Wakatime measures time spent in an editor and produces reports for leaderboards, invoicing, and team dashboards. VibeMon measures discrete AI-agent actions (hook events) and renders them as a pixel pet — there is no leaderboard by default, no minute counter, and no manager-facing report. A full comparison is at /compare/claude-code-companions.

A.VibeMon officially supports four AI coding agents today: Claude Code (Anthropic), Cursor, Gemini CLI (Google), and Codex CLI (OpenAI). A single install script auto-detects whichever agents are already configured on your machine and wires the correct hook file for each. Claude Code is the first-class target — it is the agent used in VibeMon's own development — but the event surface is identical across all four.

A.Yes. VibeMon keys events by user, not by agent, so Claude Code edits and Cursor edits both feed the same slime. If you hand off a session from one tool to another, the drop count keeps climbing uninterrupted.

A.Partially. The slime can still display and the mobile app still works, but growth is driven entirely by hook events. If you code manually in a plain editor with no supported agent installed, the slime will not gain drops. A manual-event API is on the roadmap but not shipping in the current version.

A.The install script runs on macOS and Linux. Windows is supported via WSL2. The install script is a single bash file served at https://vibemon.dev/install.sh — you can read it before running it.

A.Growth is driven by drop accumulation. Each eligible hook event adds drops to your slime. When cumulative drops cross a stage threshold defined in the slime spec, the slime advances to the next stage. Stages 0 through 5 are: 젤리 조각 (jelly shard) → 작은 슬라임 → 슬라임 → 큰 슬라임 → 거대 슬라임 → 완전체 (Perfect). Upon reaching Perfect, the slime awards a completion badge and resets to stage 0 to begin regrowth.

A.A drop is VibeMon's unit of feeding. One drop corresponds to one processed hook event — typically a tool use, a stop, a user prompt submit, or a session start event from the agent. Drops are rate-limited server-side so a burst of rapid events cannot spike the slime unnaturally. The full glossary entry is at /glossary/drop.

A.Tiers recognize repeated Perfects. Tier 1 (Hatchling) is awarded on the first completion, and tiers scale up to tier 6 (Legend). Your tier is displayed on your public profile at /u/[handle] and on the GitHub README badge. Tiers persist across slime resets.

A.The slime has three health states: full, hungry (after 3 days without drops), and starving (after 5 days). Visual effects in the game canvas reflect the state — hungry slimes desaturate and pulse slower; starving slimes tint dark and shake. The intent is gentle social pressure to keep coding, not punishment; your progress never resets from neglect.

A.No. VibeMon records event metadata (event type, timestamp, project identifier, agent name) but does not transmit or store source code, file contents, prompts, or AI completions. The hook handler on your machine strips payload bodies before any network call. You can inspect the hook configuration in ~/.claude/settings.json (or the equivalent per agent) to verify.

A.VibeMon collects: (1) the event type and timestamp, (2) a project hash so the same repository counts as one project across sessions, (3) the agent name (claude-code, cursor, gemini-cli, codex), and (4) basic account metadata you supply (handle, display name, country, avatar URL). No code, prompts, completions, filenames, or diffs are transmitted.

A.Event data and account data are stored in Supabase (PostgreSQL) with row-level security policies that restrict access to the owning user. The hook endpoint runs as a Supabase Edge Function. Public-facing pages like /u/[handle] only surface fields the user has explicitly opted in to share.

A.Yes. Account deletion is available in Settings inside the mobile app. Deletion removes your profile, drop history, slime state, certifications, and custom slimes. The action is immediate and irreversible.

A.Install has two parts. (1) Install the mobile app from the App Store or Google Play. (2) On your development machine, run the install script from https://vibemon.dev/install.sh. The script detects installed agents (Claude Code, Cursor, Gemini CLI, Codex), writes the correct hook config for each, and pairs your machine with your account. Full walkthrough at /setup.

A.Yes, the core loop is free. Free accounts include one custom slime slot, full access to growth and certification features, and the public gallery. VibeMon Pro (managed by RevenueCat) unlocks up to 20 custom slime slots, additional species packs, and advanced live feed filters. Pricing and current offers are inside the mobile app.

A.The install script is a plain bash file at https://vibemon.dev/install.sh. It (1) creates or edits the agent-specific settings file (e.g. ~/.claude/settings.json for Claude Code), (2) appends a hooks block pointing to the VibeMon Edge Function endpoint with a one-time pairing token, and (3) optionally installs a launchd/systemd unit for status updates. The script never touches your source code or git config.

A.Yes. The Apple Watch companion displays your current slime, stage, streak, and drop count as a live complication. It updates in near-real-time when you code and is the fastest way to glance at your session status without opening the phone.

A.The phone app ships on both iOS and Android. A Wear OS companion is on the roadmap but not yet released; iOS widgets and lock-screen widgets are available today on supported iOS versions.

A.Live Coders is a public feed showing users who are actively coding right now, based on recent hook events. Each entry shows the user's handle, slime, and current coding state (idle, running, breathing, tripping). Pro users can filter by Nearby (geographic proximity) for a more local feed.

A.Certification is VibeMon's "BeReal for Coders" moment — a prompt to take a front-camera selfie while coding. The app composes the selfie with a branded overlay (slime, streak, drop count) and produces a share card suitable for Instagram, X, or Discord. Certifications feed into the Live Coders feed when posted publicly.

A.Yes. Every user can create at least one custom slime via the Custom Slime API. A custom slime has a 5-color palette (indexed "1"-"5") and a 16×16 pixel idle animation (1-2 frames). The full API reference, including required fields and the sprite format, is at /docs.

A.Copy the markdown snippet from /badge and paste it into your README. The badge is a live SVG served by https://vibemon.dev/api/badge/[handle] that shows your handle, slime stage, tier, and current streak. It caches for one hour and renders reliably inside GitHub, GitLab, and Bitbucket READMEs.