• Joined on 2026-05-03
null pushed to dev at null/Pipeline 2026-05-20 22:20:55 -05:00
5637c41d1a fix (ui): settings page
null pushed to dev at null/Pipeline 2026-05-20 22:04:04 -05:00
4c5264d2ed feat(admin): gateway restart, config edit, logs, provider credentials (batch 6, #35)
null closed issue null/Pipeline#35 2026-05-20 22:03:26 -05:00
Phase 4 · Batch 6: Admin Controls — Gateway Restart, Config Edit, Logs, Docker
null commented on issue null/Pipeline#35 2026-05-20 22:03:23 -05:00
Phase 4 · Batch 6: Admin Controls — Gateway Restart, Config Edit, Logs, Docker

Verified. Issue #35 accurately reflects Batch 6 (Admin Controls) scope from the runtime usage dashboard plan:

  • All admin control candidates correctly listed (gateway restart, logs, config…
null pushed to dev at null/Pipeline 2026-05-20 21:32:52 -05:00
4e40323e71 feat(gateway-ops): memory, cron, and health panels (batch 5, #34)
null closed issue null/Pipeline#34 2026-05-20 21:27:40 -05:00
Phase 3 · Batch 5: Memory, Cron, and Health Panels
null commented on issue null/Pipeline#34 2026-05-20 21:27:37 -05:00
Phase 3 · Batch 5: Memory, Cron, and Health Panels

Verification complete. Bishop flagged that the original issue body was missing three test requirements from the plan: path traversal rejection tests (memory), missing-file/schema drift tests…

null pushed to dev at null/Pipeline 2026-05-20 21:08:24 -05:00
16b23eef2e feat(runtime-activity): live feed and activity correlation (batch 4, #33)
null commented on issue null/Pipeline#33 2026-05-20 21:07:53 -05:00
Phase 2 · Batch 4: Live Feed and Activity Correlation

Verification Complete

Batch 4 scope verified against docs/runtime-usage-dashboard-plan.md.

Implementation matches plan:

  • Frontend: Runtime tab in activity/page.tsx with…
null closed issue null/Pipeline#33 2026-05-20 21:07:53 -05:00
Phase 2 · Batch 4: Live Feed and Activity Correlation
null pushed to dev at null/Pipeline 2026-05-20 20:55:11 -05:00
1a847133ce feat(runtime-usage): add provider usage scrapers as optional local adapters (batch 3, #32)
null closed issue null/Pipeline#32 2026-05-20 20:54:44 -05:00
Phase 2 · Batch 3: Provider Usage Scrapers as Optional Local Adapters
null commented on issue null/Pipeline#32 2026-05-20 20:54:42 -05:00
Phase 2 · Batch 3: Provider Usage Scrapers as Optional Local Adapters

Verification Complete

Batch 3 scope verified against existing implementation.

What the issue requested:

  • Parser module under backend/app/services/openclaw/usage_scrapers.py
null pushed to dev at null/Pipeline 2026-05-20 20:45:15 -05:00
609d04095d feat(runtime-usage): dashboard cards, session enrichment, and regenerated API client (batch 2, #31)
null commented on issue null/Pipeline#31 2026-05-20 20:44:43 -05:00
Phase 1 · Batch 2: Dashboard Cards and Session Enrichment

Verification complete. Issue #31 accurately reflects the Batch 2 scope from runtime-usage-dashboard-plan.md:

Frontend updates to dashboard/page.tsx Frontend client regeneration from…

null closed issue null/Pipeline#31 2026-05-20 20:44:43 -05:00
Phase 1 · Batch 2: Dashboard Cards and Session Enrichment
null pushed to dev at null/Pipeline 2026-05-20 20:15:15 -05:00
9edaa5eb41 feat(runtime-usage): add read-only usage core service, schemas, and API endpoint (batch 1, #30)
null closed issue null/Pipeline#30 2026-05-20 20:14:21 -05:00
Phase 1 · Batch 1: Read-only Usage Core — runtime usage service, schemas, API endpoint
null commented on issue null/Pipeline#30 2026-05-20 20:14:18 -05:00
Phase 1 · Batch 1: Read-only Usage Core — runtime usage service, schemas, API endpoint

Verification complete. Issue #30 accurately reflects the Batch 1 scope from docs/runtime-usage-dashboard-plan.md. All files listed, data contract matches, open questions captured, dependencies…

null opened issue null/Pipeline#35 2026-05-20 19:49:16 -05:00
Phase 4 · Batch 6: Admin Controls — Gateway Restart, Config Edit, Logs, Docker