Knows what's stale before work starts

bowline status flags stale bases, missing env, and degraded sync before work starts. It is a per-project view across your ~/Code: which projects are synced, which are a few commits behind, and which are working from a base that has gone stale.

The point is to catch the expensive mistakes early. A stale base is how an agent burns an hour editing the wrong tree; missing env is how pnpm dev fails three commands in. Surfacing both up front turns a wasted run into a one-line warning you see before you start.

It runs underneath the folder rather than in a dashboard you have to remember to visit. On macOS the menu-bar app shows the same status ambiently, so the health of your workspace is glanceable without opening anything or context-switching out of your terminal.

Because status understands the workspace (source, env, and sync together), it can tell you the difference between 'behind but fine to run' and 'do not hand this to an agent yet.' That is the signal you actually want before a run, not after it.