/day

AI Business OS

/day is the start-of-day briefing. It brings your workspace up to date with your remote repository, reads every open project from your project register and shows you what has moved recently, what has gone quiet and what to work on next.

When to Use It

Run /day at the start of each working session, before you ask Claude for anything else. It is also the quickest way to get an overview after time away from the workspace.

How to Run It

Open your workspace in VS Code and open the Claude Code panel.
Type /day in the message box at the bottom of the Claude Code panel and press Enter.
Read the briefing, then tell Claude what you want to focus on today.

What It Does

Syncs and gets the date. Claude runs git pull origin main to fetch changes made on other machines, then reads the date and day name from your computer.
Gathers data. In one pass, Claude reads the projects in .claude/state/state.json whose status is anything other than archived, groups client projects by company, checks which files changed in the last seven days, reads the git history for the last 48 hours and checks .claude/config/integrations.json for enabled integrations.
Checks your calendar. If a calendar is enabled in integrations.json and its connector is available to Claude, Claude fetches the next seven days of events, and otherwise leaves this section out without comment.
Writes the briefing. Claude shows the sections described below.

Projects come from the project register, so /day finds a project wherever its folder sits, whether in a domain or a client folder.

The Briefing

The briefing opens with a greeting and today’s date, then shows these sections.

Section	What it shows
Active Projects	Every open project, most recently worked first, with a traffic light status
Active Clients	Client projects grouped by company. Left out if you have none
Recent Activity	A short summary of the git commits from the last 48 hours
Upcoming Events	Calendar events for the next seven days. Left out if no calendar is configured
Suggested Priorities	Up to three suggestions, starting with the most recent or most urgent work

The traffic lights use the date each project was last worked on.

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

Follow-Up Actions

After the briefing, you can change a project’s status by asking in plain words. 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`, and sets `lastWorked` to today
“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`
“add project Spring Workshop”	Runs `/newproject`

“Resume” here changes a project’s status. It is a different action from the /resume command, which brings back the context of an earlier session.

Archiving from /day changes the status only. To move the project folder into Archive/ as well, archive it from /status.

What It Reads and Writes

File or source	Read or write
Your remote repository	Read, through `git pull origin main`
`.claude/state/state.json`	Read for the briefing. Written only by the follow-up actions
`.claude/config/integrations.json`	Read
Git history	Read
Your calendar	Read, when configured
`.claude/state/backups/`	Written by the follow-up actions, one backup file per day

Example

/day

## Good Morning

**Today:** Wednesday, 14 October 2026

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

### Suggested Priorities
1. Finish the agenda for P012 Spring Workshop
2. Decide whether P009 Supplier Review should be paused

What would you like to focus on today?