Skip to content

Google Analytics, Vercel Web Analytics, Leadsy, the Ship or Die traffic check, the TikTok Pixel, the OpenAI Ads Measurement Pixel and Behavly stay off until you accept. The help chat starts once you have chosen. The scheduling button starts once you have chosen. Read our Privacy Policy.

StellarFirmStellarFirm
Mission manual
Esc

Type a word to search every page. Try , or .

Module 07 · Credits and usage

Usage

The Usage screen shows what your assistants have used. Learn what it lists and how clear goals and house rules keep usage down.

Last updated

View as Markdown
On this page

The Usage screen is where you check what your assistants have used. Open it any time you want to know where your credits went.

What the screen shows#

Usage lists the work your assistants did, one row at a time.

You seeWhat it tells you
The assistantWhich assistant did the work, such as the Coder.
The job or conversationWhat the work was part of.
What was usedCredits, when StellarFirm ran the work for you.
SizeHow much went in and how much came out.
What it ran onWhether StellarFirm ran it, or a connection of your own.

Calls that ran on a connection of your own are listed without credits, so the record is complete.

Note

An empty list is normal on a new account. Rows appear after an assistant has done some work.

Read it in three steps#

  1. Open Usage.
  2. Find the assistant and job you are curious about.
  3. Compare it with what you asked for. A large row for a small request usually means the goal was open ended.

If the screen does not load, check your connection and try again with Refresh. If it keeps failing, contact the Support page.

Keep usage down#

Clear goals and house rules save more than anything else.

Do thisWhy it helps
Name the place and the finish lineThe assistant does not have to explore.
Ask for one change per goalSmall jobs are quick to review and quick to redo.
Say what not to touchIt keeps the assistant out of unrelated code.
Put standing rules in your company briefYou stop repeating them in every message.
Reject a step that is off trackStopping early ends the spend early.
Ask for a plan before a big jobYou can cut scope before work begins.
PromptA tight goal

Coder, on [repository], fix [one specific problem] in [file or area]. Do not change anything else. Run the related tests and open a pull request for review.

PromptPlan before spending

CEO, for [large goal], propose the smallest first step that gives me something I can review. Do not start until I agree.

PromptAsk what drove usage

CEO, which of my recent jobs used the most, and how could I have asked for them more tightly?

Next#