[good-first-issue scan] 2026-08-16

[vivekchand]

Today's candidates (4)

All 4 are from vivekchand/clawmetry-cloud. The main clawmetry and clawmetry-landing repos returned 0 candidates after filtering (see rejection summary below).

No open PRs reference any of these issues. No bot or claim activity detected in comments.

---

clawmetry-cloud#321: [P1] Compaction markers with expandable summary

Scope: Session transcript renderer in routes/sessions.py (via OSS blueprint) - roughly 50-100 LOC for a horizontal divider element + collapsible card component at each compaction event
Why safe: Pure UI addition to the existing transcript view; no auth/billing/daemon/gateway/proxy touch; concrete acceptance criteria (divider at compaction point, collapsed card reading token count, click to expand markdown summary); zero open PRs; no bot or claim signals in comments
Apply command: gh issue edit 321 --repo vivekchand/clawmetry-cloud --add-label "good first issue"

---

clawmetry-cloud#322: [P2] Full conversation replay with time scrubber

Scope: Session detail template + clawmetry/static/js/app.js - roughly 150-300 LOC for the scrubber widget, timestamp-filter logic, and play-button auto-advance
Why safe: Frontend-only addition to the session view; no auth/billing/daemon/security touch; concrete acceptance criteria (drag scrubber filters messages by timestamp, right panel shows cost "as of T", play button advances automatically); zero open PRs; no bot activity
Apply command: gh issue edit 322 --repo vivekchand/clawmetry-cloud --add-label "good first issue"

---

clawmetry-cloud#323: [P2] Memory / RAG inspector

Scope: New 'Memory' tab endpoint + template in routes/components.py (or a new routes/memory.py) - roughly 100-200 LOC; reads ~/.openclaw/memory/main.sqlite via the existing local_store/DuckDB layer
Why safe: Additive new tab with no side-effects on existing routes; no auth/billing/daemon/security touch; concrete acceptance criteria (stats panel, file browser, FTS5 search returning snippets); zero open PRs; no bot activity
Apply command: gh issue edit 323 --repo vivekchand/clawmetry-cloud --add-label "good first issue"

---

clawmetry-cloud#324: [P2] Flow-runs dashboard

Scope: New 'Flows' tab endpoint + template, similar shape to #323 - roughly 100-200 LOC; reads ~/.openclaw/flows/registry.sqlite via the existing data layer
Why safe: Additive new tab, no auth/billing/daemon/security touch; concrete acceptance criteria (list of flow runs with goal/status/step/duration, per-flow step breakdown, blocked summary, state JSON dump); zero open PRs; no bot activity
Apply command: gh issue edit 324 --repo vivekchand/clawmetry-cloud --add-label "good first issue"

---

Rejected close calls

• clawmetry#503 "Mutiple channels" - failed on clear done-state: two-sentence body with no acceptance criteria, plus needs-info label present.
• clawmetry#4784 "discovery: find OTel-emitting apps" - body explicitly places work inside clawmetry/sync.py (sync daemon, excluded by rule).
• clawmetry-cloud#308 (security dashboard) - touched RBAC/compliance/credential vault paths (security-sensitive, excluded by rule).

---

Scan covered 67 issues in clawmetry, 80 in clawmetry-cloud, 45 in clawmetry-landing. Both clawmetry and clawmetry-landing returned 0 candidates: the clawmetry tracker is dominated by bot planning digests and epics touching dashboard.py or the sync daemon; landing's open issues are CFP/conference trackers and internal automation digests.