/status

AI Business OS

/status produces a status report for the whole workspace. It lists every project in your project register with a traffic light, summarises your client work and the last seven days of activity, and checks whether the engine files that keep your workspace safe are still intact.

When to Use It

Run /status when you want the full picture, for example at the end of a week or before you plan new work. /day shows only open projects and suggests priorities for today. /status also shows archived projects, client totals, the engine version and the engine health check.

How to Run It

Type /status in the message box at the bottom of the Claude Code panel and press Enter.
Read the report, then ask for any follow-up action you need.

What It Does

Claude gathers the following, in one pass.

Data	Source
Every project with its status, last worked date and folder path	`.claude/state/state.json`
Client projects counted per company	`.claude/state/state.json`
Files changed in the last 14 days	Your workspace folder
Projects archived in the last 30 days	`.claude/state/state.json`
Commits from the last seven days	Git history
Engine version	`.claude/engine-manifest.json`
Engine health	`bash Infrastructure/Scripts/update-engine.sh --health`

Projects come from the project register, so /status finds a project wherever its folder sits.

The Report

Section	What it shows
Header	The date and the engine version
All Projects	Every project with a traffic light status, sorted Active, Stale, Needs attention, Paused, then Archived. Only the last ten archived projects are shown
Client Work	Each client company with its number of active projects and last activity. Left out if you have no client projects
Recent Activity	Commits from the last seven days, grouped by day
Engine Health	The result of the engine health check
Quick Actions	Reminders of `/newproject`, `/newclient`, `/sync` and `/update`

The traffic lights are the same as in /day.

Light	Status shown	Meaning
Green	Active	Worked on within the last 7 days
Amber	Stale	Not worked on for 7 to 27 days
Red	Needs attention	Not worked on for 28 days or more, or overdue
Orange	Paused	Deliberately on hold
White	Archived	Completed or closed

The Engine Health Check

Some engine files control how the workspace protects and updates itself. The manifest marks them as critical, and /update always replaces them with the upstream copy. The health check compares each critical file in your workspace with the upstream copy for the engine version you run. It changes no files, though it adds the upstream remote if your workspace does not have one.

The Engine Health section shows one of three results.

Result	Meaning
All critical files intact.	Every critical file matches the upstream copy
Warning: locally modified critical files	One line follows for each file that differs or is missing, with what the next update will do to it
Not checked	The upstream copy for your version could not be reached, for example because you are offline

.claude/settings.json is a special case. Claude Code adds your approved permissions to it, and /update merges it, so the check passes as long as the file still holds every engine permission and hook.

Follow-Up Actions

You can ask for these changes after the report. Claude backs up state.json before each change and validates it afterwards.

You say	What Claude does
“archive P012”	Sets the status to `archived`, clears `stoppedAt` and `lastAction`, sets `lastWorked` to today, moves the project folder into `Archive/` and updates its `path`
“pause P012”	Asks you for a reason, then sets the status to `paused` with that reason
“resume P012”	Sets the status back to `in-progress` and clears the pause reason and `stoppedAt`
“new project”	Runs `/newproject`
“new client”	Runs `/newclient`
“update priorities”	Asks for your immediate, this week and upcoming priorities and records them in `state.json`

Archiving from /status moves the folder as well as changing the status. Archiving from /day changes the status only.

Example

/status

# Status Report

**Generated:** Thursday, 15 October 2026 | **Engine:** v3.0.2

## All Projects
| | Project | Status | Last Modified | Notes |
|---|---------|--------|---------------|-------|
| | P012 Spring Workshop | Active | 13 Oct | |
| | P009 Supplier Review | Stale | 22 Sep | |

## Engine Health
All critical files intact.