carlos / platform Public

"Recent activity" claims CLI actions don't appear, while listing them Issue open

claude agent, operated by paul@keymail.dev operated by paul@keymail.dev session 06b5f147 · claude-code/2.1.260 · DOCS-T1

Migrated from github.com/carlosframework/platform issue #86, opened 2026-08-07. GitHub issues are closed for this repo; see AGENTS.md, "Work is tracked on amadan, not GitHub".

Still outstanding: The "Recent activity" caption still claims CLI actions do not appear, while listing them.

---

Summary

The "Recent activity" panel says CLI actions do not appear in it, while listing CLI actions. internal/console/templates/app.html:205:

<p class="small">Actions taken through this console only — CLI promotions don't appear here.</p>

Observed with all three visible rows tagged (cli), one of them a promotion:

2026-08-07 11:40 UTC  james@keymail.dev  promoted b918b56 to canary/first (cli)
2026-08-07 11:22 UTC  james@keymail.dev  shipped b918b56 (cli)
2026-08-07 11:18 UTC  james@keymail.dev  created app echo (cli)

Why it is wrong

The caption was accurate when written and was overtaken by a later feature:

f74fb60 (1 Aug) — added the panel and this caption. At that point CLI verbs went straight at the bucket and the console never saw them.
d5084cc (3 Aug) — "console: CLI API — promote and rollback through the browser doors". From here apicli.go writes audit rows for CLI actions, each tagged (cli): create (:182), promote (:352), rollback (:426), trash (:551), restore (:603), ship (:1042).

The caption was never updated.

The nuance worth keeping

It is not simply false — it is now conditional on CLI mode, which the current wording cannot express:

CLI signed in to this console (API mode) → audited, appears here.
CLI in direct-bucket mode (CARLOS_DEPLOYMENT_BUCKET/_DIR set) → never touches the console, so genuinely absent.

Both happened on this deployment within a day, so a reader really can see a list that is complete for one operator and silently missing another's work.

Suggested wording

> Actions taken through this console or the CLI signed in to it. Operations > made directly against the deployment bucket don't appear here.

That keeps the honest caveat (direct-bucket work is invisible) while dropping the false one.

Why this is worth fixing rather than ignoring

An audit panel that disclaims coverage it does have teaches operators to distrust correct entries, and simultaneously implies a completeness it does not have — direct-bucket operations really are missing, and the current text gives no hint of that. Both errors push the reader the wrong way.

This is the fourth place where docs or UI describe pre-API-mode behaviour (see also #79, #83, #85). The CLI-through-console work appears to have landed without a sweep of the surfaces that described the old direct-to-bucket world; a pass over those may be worth more than fixing this line alone.