Me, Today, Now

cmd/crewship/cmd_quickactions.go ships three composite commands. Each fans out to 2-4 endpoints with sync.WaitGroup + best-effort error handling, so one slow endpoint never blocks the rest of the screen — partial views are preferred over blank ones. Partial errors land on stderr as [partial] <label>: <err> lines after the main render.

`crewship me`

“What’s on your plate right now.”

Endpoint	Used for
`GET /api/v1/missions?assignee=me`	Missions assigned to you
`GET /api/v1/approvals?status=pending&assignee=me`	Approvals waiting on you
`GET /api/v1/runs?actor=me&limit=10`	Your recent runs

crewship me
crewship me --format json

All three quick-action commands require an authenticated login and selected workspace. The CLI sends the requests concurrently and keeps successful data when one endpoint fails: partial failures are printed to stderr as [partial] ... and do not discard the rest of the view. If every workspace request fails with the session-invalid 401 response, the command exits non-zero and asks the user to authenticate again. --format json and --format yaml return an object with the collected sections plus an errors array; human-readable mode renders the same partial data.

`crewship today`

Today’s runs + spend across the workspace. Useful for retrospectives and standups.

Endpoint	Used for
`GET /api/v1/runs?limit=100`	All recent runs, filtered to today (UTC) client-side
`GET /api/v1/paymaster/top-spenders?range=24h&limit=5`	Cost summary

Output groups runs by status (completed × 12, failed × 1, …) plus a one-line cost teaser pointing at crewship cost for the full breakdown.

crewship today
crewship today --format json

`crewship now`

Live status board.

Endpoint	Used for
`GET /api/v1/runs?status=RUNNING&limit=20`	Currently-running runs
`GET /api/v1/agents`	Agent inventory; classified into idle vs busy by `status`
`GET /api/v1/approvals?status=pending`	Pending approvals across the workspace
`GET /api/v1/runtime/capacity`	Container starts held by host admission control

crewship now
crewship now --format json

Output:

Now  14:02:17 UTC

Running missions/runs: 2
  r_abc • agent=viktor  started=2026-05-19T14:00:11Z
  r_def • agent=petra   started=2026-05-19T13:58:42Z

Agents: 4 idle, 2 busy

Pending approvals: 1
  appr_xyz • Deploy frontend v2.3

Held for capacity: 1
  alpha  held 42s  reason=host_memory  host has 900 MiB available, 3072 MiB needed for one more agent container
  (these runs are queued, not hung — `crewship capacity` for the thresholds)

The Held for capacity block appears only when something is actually held. It is the one line on this screen that explains why the numbers above it are not moving: a container start waiting for host memory otherwise looks exactly like a run that has hung. crewship capacity has the thresholds and the full list.

Getting started

Sessions & identity

Agents & conversations

Crews, projects & workspaces

Missions & routines

Issues & triage

Skills & integrations

Inbox & notifications

Memory & journal

Observability

Cost & paymaster

Approvals & hooks

Configuration & system

Utilities

Me, Today, Now

Me, Today, Now

`crewship me`

`crewship today`

`crewship now`

See also

​Me, Today, Now

​crewship me

​crewship today

​crewship now

​See also

Me, Today, Now

`crewship me`

`crewship today`

`crewship now`

See also