Everything you need to ship with VibeAssist.

VibeAssist is a workspace that turns rough product ideas into clean, AI-ready backlogs — then helps you ship them with whatever coding tool you love (Lovable, Bolt, Cursor, Replit, Claude Code, you name it).

1. 1

   Get access

   Subscribe from pricing or request Free Beta access. Once approved or paid, use the emailed sign-in link to reach your dashboard.

2. 2

   Create your first project

   Click New Project, paste your app idea in plain English, and save. One paragraph is plenty.

3. 3

   Generate a backlog

   Open the AI panel and ask it to draft tasks from your idea. Accept the ones you like — reject the rest.

Projects are the unit of organization in VibeAssist. Each one keeps its tasks, knowledge documents, GitHub link, and AI settings separate. You can have as many as you want and switch between them from the sidebar.

What lives inside a project

• App idea. The original brief — editable any time.
• Backlog. Epics and tasks, the heart of the workspace.
• Knowledge base. Persistent context the AI reads from.
• Integrations. GitHub repo link, webhook endpoints, etc.

Each project's backlog is organized into Epics (broad themes) and Tasks (atomic units of work). Click any task to open the edit dialog — change the title, description, status, or add implementation notes like commit URLs or decisions.

Task statuses

VibeAssist's LLM sees what's already in your backlog before suggesting anything, so it avoids duplicates and respects the work you've done. Every AI suggestion arrives as a proposal — nothing changes until you accept it.

Tidy your backlog

• Merge proposals. Combine overlapping tasks into one.
• Delete proposals. Retire tasks that are no longer relevant.
• Re-prioritization. Suggested ordering based on dependencies.

VibeAssist is algorithm-first. Most of what it does is plain rules — fast, free, and private, with no AI call at all. AI only steps in for genuinely creative or judgment work (like generating a backlog or reviewing code), and only when you've connected some AI of your own.

Two ways a feature gets done

• Plain logic — no AI, no key. Linking commits to tasks, turning a task's acceptance criteria into test cases, drafting a sprint from your backlog. Instant, free, and works without any AI connected.
• Your connected assistant. Connect a coding assistant like Claude Code and it does the AI work for you — no key needed, because it's already your AI. This is how AI runs in VibeAssist.

What if you haven't connected any AI?

Everything the plain-logic features do still works. When you click something that genuinely needs AI, you'll see a friendly note — not an error — telling you to connect your assistant (Project configuration → Claude connection). Nothing breaks; you just connect once and the AI features light up.

Connect a repository to a project to unlock automatic task tracking. From a project, open the GitHub panel, authenticate via OAuth, and pick a repo.

Scan Repository

Click Scan Repository and VibeAssist will fetch recent commits from your default branch, compare them against open tasks, and propose which ones look done. Approve to move the task to Completed (the AI's justification is appended to its notes). Reject to leave it untouched.

The GitHub webhook is the bridge that keeps your backlog in sync with what's actually happening in your repo — no manual copy-paste, no stale statuses. When GitHub fires an event (a push, an issue closing, a comment), it pings VibeAssist, which verifies the request and updates the right tasks automatically.

What it does

• Reacts to commits on your default branch. Pulls the diff via GitHub's compare API, runs AI analysis on the changed code, updates the backlog, and refreshes the “Synchronised” badge.
• Closes the loop on AI-ready issues. When an issue tagged vibeassist-ready is closed, VibeAssist finds the matching implementation batch, extracts its TECH NOTES, appends them to the batch, and marks tasks as pending review or completed.
• Captures issue comments. New comments on vibeassist-ready issues are appended to the batch notes and queued for review.
• Auto-installs on request. Once the right token scopes are granted, VibeAssist can install or update the webhook on GitHub for you — no manual copy-paste required.
• Health check. A live status badge shows the last delivery time and event, so you know the connection is healthy at a glance.

Token permissions required

To let VibeAssist list repos, push issues, and manage the inbound webhook, your Personal Access Token needs one of these permission sets:

• Fine-grained PAT. Contents: Read & Write, Issues: Read & Write, and Webhooks: Read & Write for the repository.
• Classic PAT. repo plus admin:repo_hook.

Setting it up

1. 1

   Open project settings

   Go to your project, then Settings → GitHub.

2. 2

   Save a PAT with webhook scope

   Create the token as described above, paste it into VibeAssist, and save.

3. 3

   Link a repository

   Select the repo VibeAssist should watch.

4. 4

   Install the webhook automatically

   Click Install / update webhook automatically. VibeAssist will create or update the webhook with the correct URL, secret, and events.

5. 5

   Or add it manually on GitHub

   If you prefer, go to Settings → Webhooks → Add webhook in the repo. Paste the Payload URL shown in VibeAssist, set Content type to application/json, and select the Push, Issues, and Issue comments events.

6. 6

   Verify

   GitHub sends a ping and the health badge flips to Live. Push a commit or close an issue to see activity roll in.

What happens when an issue closes

When an issue with the vibeassist-ready label is closed (typically by a coding agent that finished its batch), VibeAssist:

• Finds the implementation batch. Matches the issue to the batch it represents.
• Extracts TECH NOTES. Parses the agent's structured completion notes.
• Appends them to the batch. So you have a permanent record of what shipped.
• Updates task statuses. Tasks are marked pending review, then completed by the AI parser if confidence is high.

If anything is ambiguous, the batch stays in pending review so you can confirm before it lands.

Claude Code is the AI assistant you chat with in a terminal (you start it by typing claude). Connecting it to VibeAssist lets it read and update your backlog directly — create tasks, mark work done, even run a whole sprint — and it's the keyless way to use AI features (see "How VibeAssist uses AI").

Option A — One-click sign-in (recommended)

No keys to handle, and the connection refreshes itself. Needs a recent Claude Code.

1. 1

   Add the connection (in a terminal)

   Run this — --scope user makes it available in every folder (leave it off and it only exists for the current folder — a common gotcha):

   claude mcp add --transport http --scope user vibeassist https://vibeassist.app/api/public/claude/mcp

2. 2

   Sign in (in Claude Code)

   Adding it only saves the connection — it doesn't sign you in. Start Claude Code with claude, then type /mcp to it, pick vibeassist (shown as needs authentication) → Authenticate. Restarting Claude Code also triggers it.

3. 3

   Allow (in your browser)

   A "Connect Claude Code — Allow / Deny" page opens. Click Allow. Done — connected, no key pasted.

Option B — Paste a token (fallback)

For CI, headless setups, or older Claude Code. In the VibeAssist web app go to Claude Connection → Generate token and copy it, then in a terminal:

claude mcp add --transport http --scope user vibeassist https://vibeassist.app/api/public/claude/mcp --header "Authorization: Bearer YOUR_TOKEN"

The token is saved in your local Claude Code config and sent only to VibeAssist — never to the AI. Regenerate or revoke it from the same screen any time.

What you can do once connected

Just talk to Claude Code naturally — it reads and writes your backlog live:

• List work. "List my VibeAssist projects" / "…my tasks."
• Create tasks. "Create a task for X under epic Y."
• Update status. "Mark this task done" / "set it to in progress."
• Check the sprint. "What's blocking the current sprint?"

Changes appear in VibeAssist immediately.

Two different things in VibeAssist both say “connect”, and one even says OAuth — so they're easy to mix up. They do completely different jobs. The trick is to ask: which way does the wire point?

1. Assistant auto-connect — wires a person to the assistant

A tiny .mcp.json signpost committed to your repo means anyone who opens that project in Claude Code is offered a one-click browser sign-in to VibeAssist — no token to paste, no setup command to remember. It's the same connection covered in “Connect Claude Code (MCP)” above, just made automatic for everyone who opens the repo.

• It signs YOU in. Each person who opens the project connects as themselves, with their own VibeAssist account.
• No secrets in the file. The .mcp.json holds no token or password — just the address of the VibeAssist connection. It's safe to commit.
• Nothing connects silently. Claude Code always shows a “trust this server?” prompt first — you approve it before anything is wired up.

2. GitHub App — wires VibeAssist to GitHub

The GitHub App integration points the other way: it gives VibeAssist itself a server-side credential to reach GitHub, so the platform can open pull requests and read your commits (for Ghost Sync) using its own key instead of a personal access token you'd otherwise have to create, paste, and rotate.

• It's the platform's key, not yours. You install the app once; VibeAssist uses its own credential from then on — no PAT to hand-carry.
• Powers PRs & commit tracking. Opening the sprint PR on your behalf and matching commits back to tasks both run on this connection.

The Knowledge Base is where you keep the durable context the AI needs every time it generates or critiques tasks. Add documents manually, or pull them in from your linked GitHub repo.

Add a document manually

1. 1

   Open Knowledge Base

   From your project sidebar.

2. 2

   New document

   Title, category, content. Markdown supported.

3. 3

   Save

   It's instantly available to every AI feature.

Import from GitHub

If your repo has READMEs or a /docs folder, click Import from GitHub, tick the files you want, and import. Each file becomes its own knowledge document using the filename as the title.

Generate a docs prompt

Click Generate Docs Prompt and VibeAssist reads your epics and tasks to assemble a ready-to-use prompt. Copy it into ChatGPT, Claude, or Gemini to draft user-facing docs from what you've actually shipped.

The sidebar is your home base. It collapses to icons on narrow screens and groups every feature by intent. Here's what each group contains.

Workspace

• Projects. All projects in your workspace. Click to switch or create a new one.
• Current project. Jumps straight to the backlog of the project you're viewing.
• Switch project. Quick dropdown to hop between projects without leaving the current view.

Project tools

Project-scoped actions that operate on the current project. Each one opens a dialog or dedicated page.

• AI jobs. Generative work queued for your connected assistant — watch it drain.
• Knowledge. Open the project knowledge base — including GitHub doc sync.
• QA settings. Toggle auto test-case generation and configure the test-results webhook.
• Health check. Find and clean up stale sprints and orphaned tasks.

Project configuration

• Project settings. Edit the project name, description and AI model.
• GitHub connection. Connect, change or disconnect the tracked repository and PAT.
• Vibe-coding tool. Pick which vibe-coding tool prompts are tailored for (Lovable, Bolt, v0, …).
• Re-sync architecture. Re-read the repo tree, package.json and README, then rewrite the architecture brief. Does not change tasks.

Footer

• User guide. This page.
• Global settings. Your account and interface preferences.
• Billing. Your plan, project usage and subscription management.
• Sign out. End your session.

• Keep your knowledge base current. Richer context = smarter AI.
• Scan repos regularly. Fastest way to keep statuses honest.
• Review every proposal. They're suggestions, not commands.
• Mobile triage. The layout is built for between-meeting cleanup.

Keyboard shortcuts