Your monthly building wallet
Planning, model work, and verification can use credits. Atlass estimates a build before it starts and records actual usage afterward. Editing code or design directly in Atlass uses no model credits.
ATLASS
Build limits without the mystery.
Credits are your included building wallet. Pace limits protect a long session from burning through it accidentally. Session capacity protects answer quality. They are three different things, and Atlass shows each one separately.
Plain-language policy · updated July 14, 2026
A safety rail, not a lockout
There is no ordinary daily build limit. During an unusually heavy five-hour or seven-day burst, Auto can temporarily choose the cheapest capable model. Capacity returns continuously as older usage leaves the window.
Context health, not billing
This meter shows how much working context the current chat carries. If it gets high, Atlass moves the checklist, project memory, and a compact summary into a fresh session. Your files and history stay intact.
A protected first impression
Your account’s first completed build keeps full-quality Auto routing through pace limits. It is one quality guarantee—not three “free builds”—and exists so planning cannot consume the whole experience before you see working software.
What happens as you use Atlass?
Normal usage
Odyssey selects the best cost-aware model for each task and applies the same engineering, design, platform, and verification rules.
Heavy recent burst
Auto enters Economy temporarily. You can keep working, see why the mode changed, and wait for full routing to return automatically. A manually selected model never disables Odyssey’s validators or review gates.
Monthly wallet empty
New model work pauses. If a build is running, Atlass finishes the current safe checklist step, saves every file, and leaves a Continue button. You can upgrade or wait for the next allowance.
Session nearly full
Atlass refreshes the AI context—not the project. The refresh itself uses a lightweight internal model, and the product records how soon it happened so unusually early refreshes can be fixed.
What does not spend model credits?
- Editing and saving code in the built-in file editor.
- Changing supported colors, spacing, typography, or text in the Design editor.
- Running available deterministic Project Health checks.
- Browsing file history, restoring a version, or downloading your project.
Rollover and unexpected charges
Pro and Max carry unused subscription credits into the immediately following billing cycle, capped at one plan allowance. Carried credits are used first and expire at the next renewal; the Plan & usage screen shows the balance and exact date. Free credits refresh rather than accumulate. Purchased add-on credits will remain valid for 12 months when credit packs launch.
No surprise overage: if Atlass later offers pay-as-you-go, it will be off by default and require both an explicit opt-in and a user-set spending cap.
Why can two similar requests cost differently?
A small copy change and a repository-wide feature are different jobs. Cost varies with project size, files read, model chosen, tool work, retries, and verification. Atlass reduces unnecessary work with lightweight classification, reusable project memory, direct file tools, and a review cadence matched to the build’s risk. Quality rules stay active; simple work simply avoids heavyweight passes it does not need.
Still unsure?
Open your avatar menu and choose Plan & usage for balances, rollover, reset dates, pace limits, and model rates. The Cost tab keeps the current project’s build receipts. Atlass also shows an estimate before a build whenever “Show cost first” is enabled. Questions are welcome at hello@atlass.build.