Plateforme de bounty debugging reliant les Vibe Coders (juniors boostés à l'IA) à des seniors capables de débloquer les bugs typiques causés par l'IA.

The fastest path to a working @zimb in VS Code. No clone, no build, no Node.js.

# One command — assumes you have VS Code 1.94+ with `code` on your PATH
code --install-extension https://github.com/Zimb/zimb/releases/download/v0.1.0/zimb-vscode-0.1.0.vsix --force

Then in VS Code:

1. Reload the window — Ctrl/Cmd + Shift + P → "Developer: Reload Window"
2. Open a folder that's a git clone of a GitHub repo you own (any repo works)
3. Open Copilot Chat — Ctrl/Cmd + Shift + I
4. Type: @zimb /bounties — you should see existing bounties (or an empty list)

That's it. The sidebar Zimb icon (left activity bar) shows your bounties + a persistent notifications badge.

No GitHub OAuth? The extension prompts you to sign in when you first use a command that needs it (/post, /status).

Honest status — what's shipped and what's vapourware.

TL;DR — the only thing that actually works end-to-end today is creating GitHub issues from VS Code. Everything else is code on a shelf waiting for infrastructure.

zimb/
├── packages/
│   ├── extension/   # @zimb/extension — VS Code / Copilot @zimb chat  ✅ ACTIVE
│   ├── worker/      # @zimb/worker — Cloudflare Worker (api.zimb.app) 🟡 code only, not deployed
│   ├── app-web/     # @zimb/app-web — Flutter Web Kanban             🟡 frozen, not deployed
│   └── landing/     # @zimb/landing — Astro landing                   🟡 code only, not deployed
├── SPECIFICATIONS.md # Tech & product spec (exhaustive)
├── docs/
│   └── CHAT_COMMANDS.md  # Slash command reference
├── recettes/         # Gherkin test scenarios
├── FOUNDER_NOTES.md  # Original founder notes
└── .github/
    ├── agents/       # 8 specialised Copilot agents
    ├── ISSUE_TEMPLATE/
    ├── PULL_REQUEST_TEMPLATE.md
    └── workflows/    # CI

See ⚡ Try it in 30 seconds above.

If you want to compose a bounty (not just look at them), the flow is:

1. @zimb /redact <your problem in plain English or French> [-l en] [-u high] [-b 50] → see a structured preview, nothing posted yet
2. @zimb /post → publishes the preview to GitHub on your current repo

Try it on a throwaway repo first.

Only needed if you want to modify the extension or the Worker.

• Node.js 20+ (nvm use 20 if you use nvm)
• npm 10+
• Git
• VS Code 1.94+ (for extension development)
• A GitHub account with a repo you can push to

gh repo clone Zimb/zimb
cd zimb
npm install                # monorepo root
npx turbo run build        # build every package

npm run dev -w @zimb/worker      # api.zimb.app → http://localhost:8787
npm run dev -w @zimb/landing     # zimb.app → http://localhost:5173

# Extension:
code packages/extension          # opens in a new VS Code window, press F5 to launch the Extension Dev Host

# Flutter Web Kanban:
cd packages/app-web && flutter pub get && flutter run -d chrome

The Worker needs API keys to talk to Stripe / Airtable / GitHub. For local dev:

cp packages/worker/dev.vars.example packages/worker/.dev.vars
# Edit and fill in:
#   STRIPE_SECRET_KEY (test mode)
#   AIRTABLE_API_KEY
#   GITHUB_APP_ID + GITHUB_PRIVATE_KEY
#   JWT_SECRET

The extension uses VS Code's built-in GitHub authentication — no secrets needed in dev.

Once installed, try each slash command. See docs/CHAT_COMMANDS.md for the full reference.

Le projet utilise 8 agents custom (.github/agents/) qui orchestrent le travail :

Voir .github/agents/README.md pour les détails.

# Lint + type-check + tests sur tous les packages
npm run lint
npm run type-check
npm test

# Formatage
npm run format

# Audit de la documentation (recettes) — utiliser l'agent QA & Recette

Voir SECURITY.md pour signaler une vulnérabilité (security@zimb.app).

• RGPD : conformes, droit à l'effacement via DELETE /me
• GitHub access : ephemeral via @zimb-bot (jamais d'accès permanent)

Phase : préparation / scaffolding
Complétude : ~70 % de la préparation, ~0 % du code en prod
Roadmap : voir SPECIFICATIONS.md §7

UNLICENSED — proprietary, all rights reserved.