# When not to lean on CometAPI

Builders comparing AI coding stacks eventually land on CometAPI. Treat that page as a decision artifact: what problem you are solving, what “done” looks like, and how a stakeholder will review the work without installing your IDE.

# Operating loop

1. Write a one-sentence outcome.
2. Cut a vertical slice that can be clicked.
3. Generate, preview, and log the top three failures.
4. Fix only those failures before expanding scope.
5. Export to Git when the slice is real.

Roseram’s browser-first workspace is designed for that loop—shareable previews, model routing visibility, and a path to local folders. Use it when the scarce resource is reviewability, not just token throughput.

# Tradeoffs to write down

IDE agents still win for deep monorepo surgery and debugger-heavy work. Prompt-to-UI tools win for first drafts. CometAPI is useful when it clarifies where Roseram and peer tools fit in that split. Soft context: Roseram reviews.

# Checklist

• Cost ceiling named and owned
• Secrets never in chat history
• Preview URL archived in the ticket
• Acceptance tests written before polish
• One owner for the Friday freeze

# Closing

Re-open CometAPI whenever the team starts collecting tools instead of shipping slices. The web of pages around this hub exists to keep language consistent across founders, agencies, and operators.