Module 07 · Credits and usage
How credits work
New accounts start with free credits. Assistants spend credits when they work, and work stops cleanly and asks you when credits run out.
On this page
Credits are the balance on your account that your assistants draw on while they work. You do not have to count them or manage them. This page explains what to expect.
The basics#
- New accounts start with free credits. You can sign in and start giving goals straight away.
- Assistants spend credits when they work. Thinking through a goal, writing code, and running a job all draw on your balance.
- Work stops cleanly when credits run out. The assistant does not leave a half-done change behind or carry on without you. It stops and asks.
- The Usage screen shows what was used. See Usage.
What uses credits#
| Activity | Uses credits? |
|---|---|
| An assistant working on a goal | Yes |
| The CEO assistant planning and briefing | Yes |
| An assistant's workspace running its commands | Yes, when StellarFirm runs it for you |
| You reading Approvals, Jobs, or Settings | No |
| Your assistants waiting for your Approve | No |
When credits run out#
- The assistant finishes or pauses at a safe point and stops.
- You get a message in chat that credits have run out.
- Nothing risky happens in the meantime. Steps that wait for your Approve still wait.
- When you are ready to carry on, tell the assistant in chat and it will continue the work.
If you need help with credits#
Check the Usage screen to see what was used. If something looks wrong, or you are not sure what to do when credits run out, write to us through the Support page.
Keeping usage steady#
- Write clear goals with a place and a finish line. See write a good goal.
- Keep each job small. Several small pull requests are easier to review than one huge one.
- Set house rules that keep work focused.
PromptKeep a job focused Coder, on [repository], do only [one clear change]. Do not refactor unrelated code. Open a pull request for review and stop.