From your first app idea to a clean, AI-maintained backlog wired into the tools you already use. Pick a topic below — or search for what you need.
Get access, land in the dashboard, and ship your first idea in under five minutes.
ReadEvery project is an isolated workspace with its own backlog, knowledge base, and integrations.
ReadEpics group themes. Tasks are the atomic units. Statuses move work from idea to shipped.
ReadGenerate tasks from an idea, then let the AI keep the backlog tidy — without making any changes you didn't approve.
ReadBring your own key from any supported provider. We store it encrypted and use it only for your projects.
ReadLink a repo, then let VibeAssist detect completed work straight from your commits.
ReadLet GitHub tell VibeAssist when code lands or issues close, so your backlog updates itself.
ReadPersistent context — architecture, personas, brand, decisions — that keeps the AI grounded.
ReadA guided tour of every group and link in the left sidebar — what each one does and when to reach for it.
ReadPlan a focused work block, log the prompts and lessons as you go, and export the result as markdown.
ReadVibe Templates, architectural constraints, and the design patterns and libraries that drive the Cheat Sheet.
ReadA read-only, at-a-glance reference of the design patterns, libraries and constraints chosen for this project.
ReadScan the linked repo for UI pattern deviations and approve AI-proposed fixes.
ReadPer-project breakdown of token consumption and estimated cost across every AI model you've used.
ReadSmall habits that compound: keep context fresh, scan often, trust your reviews.
ReadThe most common gotchas and how to clear them in under a minute.
ReadGet access, land in the dashboard, and ship your first idea in under five minutes.
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).
Get access
Subscribe from pricing or request Free Beta access. Once approved or paid, use the emailed sign-in link to reach your dashboard.
Create your first project
Click New Project, paste your app idea in plain English, and save. One paragraph is plenty.
Generate a backlog
Open the AI panel and ask it to draft tasks from your idea. Accept the ones you like — reject the rest.
Write like you'd brief a teammate
Mention the user, the core flow, and the constraint. "A timer app for sales reps that tracks calls per account" beats "a timer app" every time.
Every project is an isolated workspace with its own backlog, knowledge base, and integrations.
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.
Epics group themes. Tasks are the atomic units. Statuses move work from idea to shipped.
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.
Notes are your future self's best friend
When a task ships, paste the commit URL and any gotchas into the notes field. Three months later you'll thank yourself.
Generate tasks from an idea, then let the AI keep the backlog tidy — without making any changes you didn't approve.
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.
You're always in control
Reject anything that doesn't fit. Your backlog stays exactly the way you want it.
Bring your own key from any supported provider. We store it encrypted and use it only for your projects.
VibeAssist is BYOK (bring-your-own-key). Open Settings → AI Provider, pick a provider, paste your key and choose a default model. You can change provider or model any time — your data stays put.
Every provider below is wired into the same AI features (backlog generation, task cleanup, scan repository, prompt drafting, knowledge import, etc.). Pick whatever you already pay for.
Get a key
Each provider links straight to its API-keys page from the picker in Settings.
Paste & save
Drop it into the AI Provider section in Settings. It's encrypted at rest and never leaves your project.
Pick a default model
The dropdown filters to models your chosen provider supports.
Limits to expect
Every AI feature surfaces its output as a proposal — review before accepting. Larger models cost more per call; smaller ones (gpt-4o-mini, gemini flash, llama 8b) are usually fine for cleanup and scoring, while frontier models earn their keep on backlog generation and scan repository runs.
Link a repo, then let VibeAssist detect completed work straight from your commits.
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.
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.
Default branch only
GitHub issues created by the workflow only auto-close when commits land on the repo's default branch (usually main) and the message contains Resolves #<number>.
Let GitHub tell VibeAssist when code lands or issues close, so your backlog updates itself.
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.
To let VibeAssist list repos, push issues, and manage the inbound webhook, your Personal Access Token needs one of these permission sets:
Without Webhooks: Read & Write the auto-installer will fail
You can still add the webhook by hand from GitHub, but the one-click install/update button requires the webhook scope. If you see a 403, re-issue the PAT with the missing scope.
Use the production webhook URL
Preview URLs are protected and GitHub deliveries to them can fail with a 302 redirect. The GitHub dialog now shows the stable production Payload URL, even when you're using the preview editor.
Open project settings
Go to your project, then Settings → GitHub.
Save a PAT with webhook scope
Create the token as described above, paste it into VibeAssist, and save.
Link a repository
Select the repo VibeAssist should watch.
Install the webhook automatically
Click Install / update webhook automatically. VibeAssist will create or update the webhook with the correct URL, secret, and events.
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.
Verify
GitHub sends a ping and the health badge flips to Live. Push a commit or close an issue to see activity roll in.
Default branch matters
Push-driven sync only runs on commits to the repo's default branch (usually main). Work on feature branches is picked up after it's merged.
Security
Every request is verified with an HMAC signature (x-hub-signature-256) against your project's stored secret — even though the endpoint is public, only events signed with your secret are processed.
When an issue with the vibeassist-ready label is closed (typically by a coding agent that finished its batch), VibeAssist:
If anything is ambiguous, the batch stays in pending review so you can confirm before it lands.
Persistent context — architecture, personas, brand, decisions — that keeps the AI grounded.
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.
Open Knowledge Base
From your project sidebar.
New document
Title, category, content. Markdown supported.
Save
It's instantly available to every AI feature.
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.
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.
Plan a focused work block, log the prompts and lessons as you go, and export the result as markdown.
Sessions are short, scoped work blocks attached to a project. Open Sessions in the sidebar to start one. Each session captures its brief, the prompts you sent to your coding tool, the diffs or notes that came back, and the lessons you want to remember — all in one place so you can review or export it later.
The brief you fill in (goal, current task, technical constraints) is stitched into every prompt the session generates, so the model stays on-rails instead of inventing its own scope. Lessons learned written at the end roll forward into the project's context briefs, so the next session starts smarter than the last one.
Start a session
From the project sidebar, click Sessions and create a new one. The form requires goal, task and constraints — that's the brief the AI will reuse.
Log as you work
Paste prompts, snippets and outcomes into the session as you bounce between VibeAssist and your coding tool.
Capture lessons
When you finish, write down what worked, what didn't, and any follow-ups. These feed future context briefs.
Export to markdown
Click Export markdown on the session page to download a single .md file containing the brief, prompts, outcomes and lessons.
One session per shipped batch
Keeping sessions narrow (one feature, one bug, one refactor) makes the export far more useful when you come back to it.
Vibe Templates, architectural constraints, and the design patterns and libraries that drive the Cheat Sheet.
Open Configuration from the sidebar to record decisions that should follow this project everywhere. These values are injected into AI prompts and rendered on the Cheat Sheet.
Treat it as living documentation
Update Configuration whenever the project takes a new direction — the AI's suggestions only stay sharp if its constraints stay current.
A read-only, at-a-glance reference of the design patterns, libraries and constraints chosen for this project.
The Cheat Sheet renders whatever you've recorded in Configuration into a clean, scannable page. Use it as the one-stop reference when you (or a teammate) are about to write a prompt, open a PR, or onboard onto the project.
Click Edit in the top right to jump back into the Configuration screen. Nothing on the Cheat Sheet is editable in place — it's intentionally read-only so it can be linked and shared without fear of accidental changes.
Scan the linked repo for UI pattern deviations and approve AI-proposed fixes.
UI Review scans the connected codebase for visual and component-level inconsistencies — a button using a raw color where a token should be used, a dialog with the wrong spacing scale, a section with hardcoded dark-mode classes. The AI proposes specific fixes; you approve or reject each one.
Uses your AI provider
Scans call your provider and consume tokens. Run them after notable UI changes rather than on every push.
Per-project breakdown of token consumption and estimated cost across every AI model you've used.
Open AI usage from the Workspace group in the sidebar to see how tokens have been spent on this project. The table groups by model and feature (task generation, repo scan, deep ingest, UI review, embeddings, …) and shows running totals so you can spot the expensive ones early.
Estimates, not invoices
Costs are computed from public per-token pricing for each model. Your provider's actual bill is the source of truth.
Small habits that compound: keep context fresh, scan often, trust your reviews.
| ? | Open keyboard shortcuts |
| / | Focus search |
| N | New task in the current backlog |
| GthenD | Go to dashboard |
| GthenS | Go to settings |
| Esc | Close dialogs |
The most common gotchas and how to clear them in under a minute.
Resolves #<number>.