Glossary
Understand the terms displayed in Prism.
Use the term shown on the screen you are reading. A label can describe a count, an estimate, or an AI evaluation; those are different kinds of information.
For a connected explanation with a worked example, read Core concepts. Use this page to look up a term and follow its link to detailed guidance.
Work and scores
Section titled “Work and scores”| Term | Meaning |
|---|---|
| Session | A Claude Code or Codex conversation. Sessions on Overview counts the sessions that had activity in the period. |
| Task | An item listed on Sessions. Opening it shows its subtasks and its prompts. |
| Subtask | The smallest unit of work that gets a status and a score. |
| Prompt | An input you send to an agent; also the Prompt screen under Analytics. |
| Turn | A unit counted in the Turns column of Sessions and Realtime. |
| Request | A request sent to the model. One prompt can lead to several requests. |
| Prompt Score | From 0 to 100. The score of a subtask is the share of the required items it met, with a bonus for each optional item met, and the score of a period is the average over the subtasks that ended in it. |
| Prism Score | From 0 to 100 with a grade band: the share of counted code work that was completed, verified, and not reworked, weighted by size. It appears only after the score has passed its accuracy check. |
| Score rules | The label that shows which version of the score rules judged a value. |
| Seven items | Goal stated, Scope limited, Specific references, Enough context, Verification requested, Root-cause focus, and Output format stated. Each is met, missed, or not applicable. |
| Status | The state of a subtask: Completed, In progress, Stopped, Abandoned, Failed, Waiting for judgment, Indeterminate, or Unjudgeable. |
| Trivial subtask | A subtask below the workload floor; it gets no score. |
| Counted / Excluded | Whether a subtask counts toward the score, as shown in the Counted? column of Sessions. |
| Provisional / Confirmed | Whether the value of a period can still change or has been confirmed. |
| Correction | A value that changed after it was confirmed, listed in Corrections and version boundaries on Overview. |
| Coaching | For each subtask, the items that were missed, tied to what actually happened. |
| Interventions | How often you added input, interrupted, or answered a question. |
| Mid-work rework rate | The share of completed subtasks that had a correction or revert before they finished. |
| Elapsed time / Actual run time | The time from the first event of a subtask to its completion, and the time between the start and end of a run. A period shows the median. |
See Scores and work status for how these values are made and read, and Sessions for investigating individual work.
Usage and cost
Section titled “Usage and cost”| Term | Meaning |
|---|---|
| Input / Output | The input and output token counts of the requests in the period. |
| Cache read / Cache write | The cache read and cache write token counts of the requests in the period. |
| Estimate | A cost converted at API prices, never a bill. Its basis is shown as Catalog list price, Claude Code reported, or Mixed. |
| Cost per completion | The estimated cost of a period divided by the number of completions. |
| Model mix | The share of the estimated cost by model. |
| Active time | Time spent working with the agent, split into User time and CLI time. |
| No data / Calculating / Incomplete pricing | States of a section. They are explained in Periods and data states. |
Access and reports
Section titled “Access and reports”| Term | Meaning |
|---|---|
| Organization | The workspace that holds users, teams, and organization settings. |
| Owner / Admin / Member | The roles in an organization. An admin can view team metrics and manage members and invitations; a member can view the metrics of the teams they were given view access to. |
| Team | A group of organization members. Team membership and view access are set separately; a user with both is shown as team manager. |
| Realtime | Live coding session activity: today’s average prompt score, activity, tokens, and cost. |
| Realtime Advisor | A pop-up with the activity of yesterday and today, by session and subtask. |
| Daily Recap | The result of a day, built from the subtasks that ended that day. |
| Report / Team Report | The report of a period, and a Team’s weekly report. |
| Score history (v3) | A list of subtasks scored under score rules v3 with their title, closing day, status, and grade. |
| Devices | The computers connected to your account, listed in Settings. The CLI and both plugins on one computer share one sign-in, so that computer is one device. |
For the commands of the CLI, use Commands.