Codex activity on Mac. Check what was observed.

NotchPop's Codex activity surface depends on supported information available on this Mac. It is not a promise to aggregate every session from every machine, browser or account. Start with an ordinary local CLI session so the dashboard has something concrete to read.

If the connection card says Codex is not signed in locally, complete your usual CLI setup rather than entering unrelated credentials into a status field. You do not need to publish the contents of ~/.codex to demonstrate a connection issue. That folder can contain material that should remain private.

1. Open NotchPop Coding and locate Codex.
2. Connect or reconnect the local CLI route when available.
3. Read the connection mode, last sync and any error.
4. Inspect sessions or usage only when the corresponding data is present, and retain the observation time for reported limits.

A plan limit is a provider observation at a time, while a session total comes from a different activity source. The two do not necessarily use the same window or definition. An unavailable value should remain unavailable rather than being replaced by a guess, and a local count is not a billing statement.

The island is useful for noticing whether the assistant is working, waiting or needs attention while your editor stays visible. Confirm the actual task result in the original tool. A session finishing or a token count changing does not establish that generated code built, passed tests or reached production.

For another assistant, read Claude Code activity rather than assuming the same data source applies. Check a local dev server independently when previewing the result, and use the CPU summary if a long-running build needs resource investigation. Each tool answers a different question about the workflow.