Documentation
Task-based guides and product reference for prompts, drafts, checks, and published previews.
Getting started
Everything you need to go from idea to first build.
Go to the setup page and choose your path — beginner, quick start, or advanced. Describe your idea, set preferences, and DriftLess will create the first build target instead of treating the whole product as one giant request.
Start onboarding→Free and Pro use hosted credits, so no provider key is required. Team and platform-admin accounts can open Settings → AI providers to add OpenAI, Anthropic, Gemini, or other supported keys.
Open settings→Open Build, describe what you want to build, and DriftLess will create a draft, improve it, and check the result. Draft preview shows progress; the published preview waits until checks pass.
Open Build→Working with your project
Day-to-day tasks as you build and iterate.
When a build finishes, DriftLess shows the active task, changed files, reviewer notes, proof status, and preview state. Approve, reject, or steer the output, then leave feedback that improves future builds.
Drift means the draft moved away from the active task or original goal. When DriftLess detects it, it explains what changed and gives you options: keep the changes, adjust the plan, or ask for a narrower next pass.
Connect your GitHub account under Account → GitHub, then use Send to GitHub after a trusted build. DriftLess asks whether you want a pull request or a direct push to the default branch before it commits. For trust gates, rate limits, auto-created repos, and how plan limits apply, see the GitHub handoff FAQ.
GitHub handoff FAQ→After each build, a feedback prompt appears. Rate the quality and add notes about what worked or didn't. This feedback trains DriftLess to match your preferences over time.
When DriftLess asks for input
DriftLess stays out of your way except when a real decision matters.
Draft moved off target
The project grows too far from the original goal.
Review what changed and decide: keep, adjust, or revert.
Budget exceeded
Cost goes above the limit you set.
Pause the session and raise your cap or trim scope.
Final approval needed
A human sign-off is required before completion.
Review the output and approve or request changes.
Feedback requested
After a session, DriftLess asks you to rate the output quality.
Rate the session and leave a short note on quality.
Changes predicted
Based on how things are going, your project may start going off track — DriftLess warns you early.
Check the prediction and tighten constraints if needed.
Project idle
When a project goes quiet, a gentle reminder keeps momentum alive.
Resume the project or archive it if complete.
Features reference
Everything DriftLess creates, tracks, and persists for you.
Build goal
Clear goals, audience, and success criteria saved for every project.
Build plan
Large requests are split into the next version and a backlog so each build stays focused.
Decision log
Every choice the AI makes is saved so you can retrace your steps.
Alignment warnings
Warnings when the draft moves away from what you asked DriftLess to build.
Credit tracking
Hosted credits and approximate build capacity shown for each session — no surprises.
Session history
Full timeline of every session with outputs, decisions, and progress.
Your feedback
Rate each session and DriftLess learns what quality means for your project.
Saved preferences
Remembers your preferences so results stay consistent over time.
Early warnings
Spots when your project might go off track, before it actually does.
Check-in reminders
Gentle reminders when a project goes quiet — keeps things moving.
Prompts
Ready-made starting points for common websites, apps, dashboards, and workflows.
Behind the scenes
DriftLess plans, edits, reviews, and asks Design Lab for media when your project needs a richer public page.
GitHub handoff
Connect in Account, then push builds as PRs or to your default branch; Pro adds repo-import onboarding. Webhooks fire on reviews.
Linear tickets
Start builds from tickets, auto-update status, and close the loop from idea to code.
Railway deploy
Auto-deploy after successful builds with status tracking and preview URLs.
Draft and published preview
Drafts show progress while DriftLess builds. Published previews are trusted only after checks pass.
Design Lab media
Public-facing sites get image and UI-element guidance by default; internal tools stay quieter and more utilitarian.
Onboarding reference
Quick explanations for each project setup question.
Your project goal
Describe your idea, who it's for, and what "done" looks like. This keeps everything on track.
Project rules
Choose how strict or flexible your project should be — from solo to team-level controls.
How the AI assistants work together
Choose how independently the planner, writer, and reviewer should operate.
How many reviews before asking you
Set how many review rounds happen before DriftLess asks for your input.
When to warn you about changes
Set how much the project can change before DriftLess warns you.
AI spending limit
Set an optional cost cap so AI usage never surprises you.
Quality checks
Choose which quality checks are required before a session can be considered complete.
Adding new features
Choose when new work can be added and when your approval is needed.
Rules that can't be broken
List the rules that must never be broken — your non-negotiables.
Required records
Choose which records must always be saved and whether completed records can be edited.
How DriftLess improves over time
Choose what feedback is needed and how repeated issues are handled.
Questions? Contact us.