convez.ai
MCP ServerAutomaçãoAvançado
withvibe

WithVibe

withvibe/withvibe

Ambiente compartilhado de IA self-hosted com gates automatizados de QA

Ver no GitHub
BomPluginScore · de 0 a 100

Ambiente de IA compartilhado e self-hosted para times de P&D. Permite criar ambientes isolados com um clique, desenvolver com assistência de IA, compartilhar com o time e fazer deploy automatizado com gates de agentes especializados (segurança, código, testes, conformidade).

Instalação

$npx convez-ai withvibe/withvibe

1 comando no terminal: detecta o formato do repositório (marketplace ou plugin avulso) e instala via Claude Code. Requer Node 18+ e o Claude Code instalado.

Métricas

Estrelas
10
Forks
1
Acompanhando
0
Saúde
100%
Último commit
há 3 semanas
Versão
v0.4.9
Issues abertas
7
Contribuidores
2

Casos de uso

  • Desenvolvimento colaborativo em equipes de P&D com assistência de IA
  • Code review automatizado com agentes especializados antes de produção
  • Prototipagem rápida em ambientes isolados com controle de versão integrado

Veredito

Solução robusta para times que querem acelerar desenvolvimento com IA mantendo rigor de QA. Requer infraestrutura Docker e conhecimento técnico, mas oferece fluxo end-to-end bem pensado — do ideation ao deploy automático.

README

A tradução para o português deste README ainda está na fila.

WithVibe

A self-hosted, shared AI environment for R&D teams. A teammate spins up an isolated env with one click, vibe-codes with AI, shares it with the team, and ships once automated agent checks and human review pass.

🌐 withvibe.dev  ·  📦 CLI on npm  ·  📖 Docs  ·  ✉️ Contact

License: AGPL-3.0 CLI: Apache 2.0 Node pnpm Website

Try it in 30 seconds

npm install -g withvibe       # Node 20+, Docker 24+ required
withvibe doctor               # sanity-check your machine
withvibe init -y              # one-click install + start

When init finishes, it prints the URL — open it, sign in, you're running. For options and details, see the CLI README.

Flow

flowchart TD
    A([💡 Team member has an idea]) --> B[🖱️ One click — spin up an isolated env]
    B --> C[🤖 Vibe-code with AI]
    C --> D[👥 Share the env with the team]
    D --> E[Teammates join the same AI session & review]
    E --> F{Human approval?}
    F -->|Needs work| C
    F -->|Approved| G[Pre-production agent gate]

    subgraph GATE [🛡️ Automated agent gate]
        direction LR
        H[🔒 Security review]
        I[🔍 Code review]
        J[🧪 Test & quality]
        K[📋 Policy / compliance]
    end

    G --> H & I & J & K
    H & I & J & K --> L{All checks pass?}

    L -->|Flagged| C
    L -->|Clean pass| M([🚀 Deploy to production])

    classDef start fill:#1e90ff,stroke:#0a0a0a,color:#ffffff;
    classDef ship fill:#22c55e,stroke:#0a0a0a,color:#ffffff;
    classDef decision fill:#f59e0b,stroke:#0a0a0a,color:#0a0a0a;
    class A start;
    class M ship;
    class F,L decision;

The idea

  • One click to start. No infra setup — the team member gets an isolated env seeded with the existing code.
  • Vibecode with AI. The AI is the primary collaborator inside the env.
  • Share, don't fork. The env is shared with the team; anyone can jump in and interact with the same AI session.
  • Automated gate before prod. Once humans approve, specialist agents (security, code review, tests, policy) run as a final gate. Anything flagged loops back to the env.
  • Ship. Clean pass → merge to main → production.

Repository layout

This is the server-stack monorepo (pnpm). The CLI that installs and runs the stack lives in a separate, Apache-2.0 repo.

.
├── apps/
│   ├── web/        # Next.js 16 frontend + auth + REST proxy (@withvibe/web)
│   ├── api/        # NestJS backend, Docker orchestration, terminal WS (@withvibe/api)
│   └── qa-browser-extension/  # Chrome MV3 ext for the QA agent (@withvibe/qa-browser-extension)
├── packages/
│   └── db/         # Prisma schema + generated client (@withvibe/db)
├── docs/           # architecture and operator notes
├── scripts/        # release + GHCR publishing
└── LICENSE         # GNU AGPL-3.0

Develop the codebase

Just want to run WithVibe? Use the withvibe CLI — see the Try it in 30 seconds section above. This section is for contributors working on the server stack itself.

Prerequisites

  • Node.js ≥ 20
  • pnpm ≥ 9
  • PostgreSQL ≥ 14 (local or remote)
  • Docker + Docker Compose (for environment containers)
  • gh CLI (recommended; used by withvibe env for repo cloning)

Local dev setup

# 1. Install
pnpm install

# 2. Configure environment
cp apps/web/.env.example apps/web/.env
cp apps/api/.env.example apps/api/.env
# Then edit both files — see the env reference below.

# 3. Generate Prisma client and apply schema
pnpm --filter @withvibe/db generate
pnpm --filter @withvibe/db db:push

# 4. (optional) Seed initial data
pnpm --filter @withvibe/db db:seed

# 5. Run web + API in parallel
pnpm dev

The web app boots at http://localhost:3000, the API at http://localhost:4000/api.

Run individual apps

pnpm dev:web     # Next.js dev server
pnpm dev:api     # NestJS in watch mode

Build / verify

pnpm build       # build every workspace package
pnpm typecheck   # tsc --noEmit across the workspace
pnpm lint        # eslint (web app)

Environment variables

The web app is the frontend only — it never touches the database. All DB access, auth, and third-party credentials live in the NestJS API. The web server forwards the user's session cookie to NestJS over a same-origin path.

apps/web/.env

VarPurpose
API_BASE_URLURL the web server uses to reach NestJS (dev only — same-origin in prod)

apps/api/.env

VarPurpose
API_PORTPort the NestJS server listens on (default 4000)
DATABASE_URLPostgres connection string
INTERNAL_JWT_SECRETSigns user-session JWTs (cookie) and the legacy bridge JWT
REPO_BASE_DIRAbsolute path on disk where cloned repos live
API_PUBLIC_URLPublic URL of the API — used to build the Google OAuth callback
WEB_PUBLIC_URLPublic URL of the web app — where Google OAuth lands after login
ANTHROPIC_API_KEYWorkspace-level Anthropic fallback when no per-workspace key is set
GOOGLE_CLIENT_ID / GOOGLE_CLIENT_SECRETOAuth (leave empty to disable Google login)
COOKIE_SECUREtrue to mark the session cookie Secure (auto in production)
COOKIE_DOMAINSet when API + Web are on different subdomains

Related repositories

RepoLicenseWhat it is
withvibe/withvibe (this repo)AGPL-3.0The server stack — api, web, db, QA-browser extension
withvibe/withvibe-cliApache 2.0The withvibe CLI — installs and manages the stack, runs envs locally
withvibe/withvibe-skillsApache 2.0Claude Code skills — first-time installer guide + plugin scaffolder
withvibe/withvibe-roadmapApache 2.0Roadmap plugin — a per-env implementation board (Postgres-backed) with an MCP server the AI orchestrator drives
withvibe/withvibe-voterApache 2.0Example plugin — turns any env into a team-voted workspace: the AI opens proposals the team votes on before they're built
withvibe/vibe-aquariumApache 2.0Demo app — a minimal 3D aquarium you reshape live by chatting with the running app

Links

Contributing

See CONTRIBUTING.md. For security issues, see SECURITY.md.

License

Source code in this repository is open source under the GNU Affero General Public License v3.0 (AGPL-3.0). See LICENSE for the full text.

Plain-language summary

This summary is not a substitute for the LICENSE — it's just meant to make the common cases easy to understand.

✅ Free to use, modify, and self-host — including for internal use inside your organization (running it for your own team, customizing it, fixing bugs, contributing patches back).

✅ Free to fork and build on, under the same AGPL-3.0 terms.

⚠️ If you offer a modified version to others over a network (e.g. as a hosted service), the AGPL requires you to make your modified source available to its users under the same license.

Commercial licensing

The hosted WithVibe offering is provided by us under a separate commercial license. If the AGPL doesn't fit your use case — embedding WithVibe in a proprietary offering, or running it as a service without the source-sharing obligation — reach out and we'll work out a commercial license agreement: withvibe.dev/contact.

Contributor License Agreement

External contributions require agreeing to our CLA, which licenses your contribution to us broadly enough to keep dual licensing (open source + commercial) possible. The CLA check runs automatically on your first pull request.


Copyright © 2026 WithVibe · withvibe.dev

Ver o original no GitHub

Bom para

Relacionados