Open hosted SaaS | View pricing | Start checkout
Plan quota windows before AI coding work stalls mid-task.
Last reviewed: 2026-05-18.
This is a docs-only project for ClaudeLimit Planner. It is modeled after the MiroFish developer documentation pattern: a short front door, a clear reading order, practical guides, feature explanations, public references, and developer-oriented architecture notes.
It focuses on:
- what ClaudeLimit Planner is and who should evaluate it
- how the hosted SaaS at claudelimitplanner.space fits into the workflow
- which product surfaces matter first
- what to check before payment, rollout, or team adoption
- how to keep public links tracked with UTM parameters
Scope boundary:
- This repository contains documentation only.
- It does not contain the production SaaS source code.
- It does not include private deployment details, credentials, internal paths, customer records, or analytics exports.
- If product behavior changes, verify the live SaaS before reusing these notes.
- OpenHuman Online is useful when evaluation depends on durable source notes, meeting context, and human-reviewed assistant memory.
| File | Best for |
|---|---|
| guide/quickstart.md | Fastest buyer and evaluator path. |
| guide/evaluation.md | What to check before paying or rolling out. |
| guide/checkout-and-pricing.md | Hosted SaaS, default plan, pricing, and checkout links. |
| guide/troubleshooting.md | Common blockers and clean next steps. |
| features/workflow.md | End-to-end product workflow. |
| features/use-cases.md | High-intent use cases and buying triggers. |
| features/security-model.md | Practical safety boundaries. |
| reference/links.md | Public links with UTM tracking. |
| reference/faq.md | Short answers for common questions. |
| reference/utm-policy.md | Link tagging rules for this docs project. |
| developer/architecture.md | How to explain the SaaS from a developer point of view. |
ClaudeLimit Planner helps teams forecast Claude Code and Codex quota windows, split coding work into batches, route fallback models, and export capacity plans.
Use ClaudeLimit Planner when you need:
- Quota calendar preview
- Batch scheduler
- Fallback model routing
- Mobile approval hints
- Weekly AI coding capacity brief
The main hosted entry points are:
| Destination | Tracked link |
|---|---|
| SaaS home | claudelimitplanner.space |
| Pricing | pricing |
| Checkout | checkout |
Open these when quota planning expands into adjacent agent workflows, not as substitutes for the planner itself:
| Project | Tracked link | Why it helps |
|---|---|---|
| MiroFish | mirofish.work | Useful when model-capacity planning feeds a multi-agent scenario simulation or report workflow. |
| Ruflo | ruflo.online | Useful when the same capacity plan needs to coordinate Claude Code, Codex-style work, MCP tools, and review checkpoints. |
- Estimate the work, deadline, repo risk, and reviewer availability.
- Map Claude, Codex, Gemini, and human-review lanes to available quota windows.
- Split large AI coding work into recoverable batches with test expectations.
- Export a weekly capacity brief before the team burns premium model time.
- Do not treat quota planning as a substitute for code review.
- Keep high-risk patches behind human approval.
- Leave rollback time in every quota window.
- Avoid scheduling all critical work in the final reset window.
Corrections are welcome. Keep this project public-safe: cite public sources, avoid copying long passages from other projects, and never include credentials, customer data, private logs, internal machine paths, or untracked outbound links.