ivibe

Download · Website · How it works · Hackathon checklist · Architecture · Contributing

Show the bug and talk it through. iVibe writes the fix prompt, with annotated screenshots as proof, and pastes it straight into Claude Code, Cursor or ChatGPT.

Press a shortcut, show what's wrong while you explain it, and press it again. iVibe hides secrets on your device, works out what you meant, and pastes the result into the app you were typing in. No report window, no copy-paste.

_{A recording of the interactive demo at ivibe.tech. The website draws the desktop in it, so try it there or download the real app.}

You say it, iVibe pastes it

These are the examples from the website demo.

Fix. You show the broken page and say:

I change my bio and hit Save, and nothing happens. The console says it can't read map. It should save and show a toast.

iVibe pastes this into your coding agent, with marked-up screenshots:

Save on Edit profile does nothing

Expected: saving shows a "Saved" toast and keeps the new bio.
Actual: no request is sent. Console: TypeError: Cannot read properties of
undefined (reading 'map') at saveProfile (ProfileForm.tsx:41).

Prompt. You ramble:

Uh, so I want, like, a dark mode toggle. It should remember my choice. Oh and, um, follow the system setting by default, I guess.

iVibe pastes a prompt that an AI can act on:

Add a dark mode toggle

Goal: Let people switch between light and dark themes.
Requirements:
- Follow the system setting by default
- Remember the choice across visits
Done when: The choice survives a reload

Dictate. You talk:

Hey Asha, um, the demo is, uh, the demo is ready for tomorrow. So, like, let me know what you think.

iVibe pastes what you meant to say:

Hey Asha, the demo is ready for tomorrow. Let me know what you think!

See it

Fix	Prompt	Dictate

_{Scenes from the website's interactive demo.}

The real desktop app

_{Windows screenshots of the app. History shows sample data.}

Download

iVibe 0.1.5 is out for Windows, macOS and Linux. Get it from the latest release:

The installers aren't code-signed yet, so your computer asks once before opening iVibe:

• Windows: if SmartScreen says "Windows protected your PC", click More info, then Run anyway.

• macOS: the quickest way is one line in Terminal, which installs the latest version into Applications and opens it, with no security prompt:

  curl -fsSL https://raw.githubusercontent.com/nikylogic/ivibe/main/scripts/install-mac.sh | bash
  

  Or open the .dmg and double-click iVibe: it offers to move itself to Applications. If macOS says it can't verify iVibe, open System Settings → Privacy & Security and click Open Anyway.

• Linux: sudo apt install ./iVibe-<version>-linux-amd64.deb, or chmod +x the AppImage and run it.

iVibe keeps itself up to date. On Windows and Linux it downloads updates in the background and installs them when you restart; on macOS it tells you when a new version is out.

Three modes

Every shortcut can be changed in Settings. On Windows, hold Caps Lock to talk, or double-press it for hands-free. Results land where you were typing: screenshots are pasted as images into chat apps and Claude Code, and as file paths into other terminal agents. If you switched apps meanwhile, the result waits on the clipboard and pastes into the next text field you click, or with Ctrl + Alt + V.

Fix and Prompt record for up to 60 seconds, and Dictate for up to 5 minutes. In Dictate you can also select text in any app and say what to change, such as "make this more formal" or "translate to Hindi".

Plans

A credit is one cent of Meta usage. A dictation costs a fraction of a credit and a Fix report a few credits.

How it works

flowchart LR
  A["Shortcut<br/>screen + voice"] --> B["On your device<br/>OCR · secrets painted over"]
  A --> C["Live captions<br/>Muse Voice Transcribe"]
  B --> D["Muse Spark 1.3<br/>transcript + redacted frames<br/>→ fix prompt + proof picks"]
  C --> D
  D --> E["SAM 3.1<br/>snaps highlights<br/>to the UI element"]
  E --> F["Pasted into your app<br/>text + annotated screenshots"]

1. Record. A shortcut captures the screen under your cursor and your microphone. Captions appear as you talk.
2. Protect. Every keyframe is read with on-device OCR (PP-OCRv5). API keys, tokens, .env lines and password managers are painted over before a frame can leave the recorder.
3. Write. One Muse Spark call reads your narration, the redacted keyframes and their text, and returns the prompt and which frames prove the bug. Prompts are built from layers: fixed rules, the mode, the app you're pasting into, and what you told iVibe about yourself.
4. Prove. SAM 3.1 snaps each highlight to the exact button or error; the screenshots are annotated on your device.
5. Paste. iVibe pastes into the app you were in, each screenshot after the sentence about it, and keeps a copy in History.

Built on Meta's models

All of this runs on the Meta Model API, and Muse Spark calls are sent with store: false. Runs on your own key and on Pro use muse-spark-1.3. Free trial runs use muse-spark-1.3-contributor, and Meta may use those requests to improve its models; iVibe tells you this when the trial starts. Muse Spark Open (an open-weight engine for iVibe Cloud) and Muse Wonder (optional deep analysis) are planned, not shipped.

Privacy

• Secrets are hidden on your device. Only redacted frames and your narration are sent for analysis. packages/redact has its own tests, and the app's developer self-test records a fake app showing a planted GitHub-style token, to exercise OCR and redaction end to end.
• The free trial is the exception on training. Meta may use trial requests to improve its models (see above). Use your own key or Pro to avoid that.
• Your key stays yours. A Meta API key is encrypted with your system keychain and used only by the app's main process.
• History stays on your device. The last 200 results and their screenshots are kept locally, can be turned off, and can be cleared in Settings.
• Backups are end-to-end encrypted. Pro backups are encrypted on your device with a recovery key that only you hold; iVibe can't read them.

Meta hackathon checklist

Every rule from the Meta AI Developer Hackathon participant guide, and where iVibe stands. Checked Nov 2, 2026. Unticked boxes aren't done yet.

The build

The submission (due Nov 4, 2026, 9:00 PM EST, which is Nov 5, 7:30 AM IST)

Optional extras

Status

Updated Nov 3, 2026. The latest release is 0.1.5. iVibe is being built in public for the Meta AI Developer Hackathon (Oct 27 – Nov 4, 2026). The full breakdown is in docs/architecture.md.

Shipped

• Fix, Prompt and Dictate, with live captions, personal settings and per-mode shortcuts
• On-device OCR and secret redaction, annotated proof screenshots with SAM 3.1
• Paste into the app you were in, click-to-paste and History
• Installers for Windows, macOS and Linux, with automatic updates
• iVibe Cloud: GitHub sign-in, free trial credits, iVibe Pro and encrypted backups
• ivibe.tech: website, docs and an interactive demo for desktop and phone

Being verified by hand

• macOS and Linux on real machines (they build and pass tests in CI)
• Image paste into Claude Code and ChatGPT (text paste is confirmed)

Next

• Evaluation suite: voice cases and a set of 20 recorded bugs
• Code signing for Windows and macOS
• After the hackathon: Vibes, where everything is a vibe, even Fix, Prompt and Dictate, and you can describe a new one instead of coding it (plan)
• Then: the note taker, built as a vibe

Development

Prerequisites: Node.js 24+ and pnpm 12+.

git clone https://github.com/nikylogic/ivibe.git
cd ivibe
pnpm install
pnpm ocr:fetch    # download the on-device OCR models (13 MB, hash-checked)
pnpm check        # lint, format check, typecheck, tests and the dependency license check
pnpm --filter @ivibe/desktop dev   # run the desktop app

Add your Meta Model API key in the app under Settings → Meta API key. The experiments in spikes/ read it from .env instead: copy .env.example to .env, set META_API_KEY, then for example:

pnpm spike spikes/meta/s10-models.ts

Releasing: set the version in apps/desktop/package.json, commit, and push a matching tag (git tag -a v0.1.1 -m "iVibe 0.1.1" && git push origin v0.1.1). GitHub Actions builds every installer into a draft release; publishing the draft is what the app's updater sees.

Repository layout

apps/desktop   Electron app: recorder, pill, app window, tray, updater, OS helpers
apps/api       iVibe Cloud on Cloudflare Workers: sign-in, credits, Pro billing, backups
apps/web       ivibe.tech: the website, docs, blog and interactive demo
apps/demo-bug  A small React app with a planted bug, for demos
packages/      capture · vision · ocr · redact · encode · imageops · bundle · agent · ui · config · types · engine (Meta API, prompts, proof)
logo/          every logo file, generated from one mascot drawing (logo/README.md)
spikes/        experiments that verify API and platform facts before building on them
docs/          architecture, spike results, the Vibes and prompts plan, README images
scripts/       repository tooling (OCR model download, dependency license check)

Every package's role and the decisions behind it are in docs/architecture.md; spike results are in docs/spikes.md.

Contributing

Contributions are welcome. Please read CONTRIBUTING.md and the Code of Conduct. Contributors sign a Contributor License Agreement once, on their first pull request.

Found a security issue? Please report it privately; see SECURITY.md.

License

iVibe is free and open-source software, licensed under the GNU Affero General Public License v3.0.

Want to modify iVibe or embed it in a product without the AGPL's obligations? Commercial licenses are available.

The iVibe name and logo are not covered by the code license; see TRADEMARKS.md.