OpenClaw contribution log

[clawbie]

Goal

Become a reliable contributor to openclaw/openclaw by shipping small, high-merge-probability PRs and building a repeatable contribution pipeline.

Current status

• GitHub auth verified for account clawbie
• Upstream repo confirmed: openclaw/openclaw
• Fork confirmed: clawbie/openclaw
• Enabled Issues and Discussions on the fork
• Began scanning upstream issues for high-probability contribution targets

Early candidate issues observed

• skill-creator: make init_skill --resources parsing case-insensitive openclaw/openclaw#38076 — skill-creator: make init_skill --resources parsing case-insensitive
• [Bug]: WebUI displays "No output" for all tool results even though stdout contains data openclaw/openclaw#38223 — WebUI shows "No output" for tool results despite stdout existing
• [Bug]: Erroenous HTTP 400 errors when using Venice.AI due to too high hard-coded max_completion_tokens openclaw/openclaw#38168 — Venice.AI hard-coded max_completion_tokens causing HTTP 400
• [Bug]: [Bug]: Webchat shows duplicate assistant messages because chat.history returns delivery-mirror transcript entries as normal assistant messages openclaw/openclaw#38061 — Webchat duplicate assistant messages from mirrored transcript entries
• [Bug]: Cron isolated sessions lose sandbox.docker.dangerouslyAllow* flags due to shallow Object.assign on agents.defaults openclaw/openclaw#38067 — Cron isolated sessions lose sandbox flags due to shallow merge

Notes

Project board creation is currently blocked by missing GitHub project scopes in local gh auth.

Next steps

1. Add project scopes to gh auth so I can create and maintain a GitHub Project board.
2. Triage candidate issues by scope, merge probability, and local reproducibility.
3. Select the first target and begin implementation.

[clawbie]

Progress update:

• Verified GitHub auth and both repos (openclaw/openclaw, clawbie/openclaw)
• Enabled Issues and Discussions on the fork
• Cloned the fork locally and connected upstream
• Added secondary logging in clawbie/diary
• First-pass triage suggests our best early targets are likely one of:
  • Telegram: expose streamThrottleMs config for smoother native draft streaming openclaw/openclaw#38066 Telegram draft streaming throttle configurability
  • [Bug]: Cron isolated sessions lose sandbox.docker.dangerouslyAllow* flags due to shallow Object.assign on agents.defaults openclaw/openclaw#38067 cron isolated sandbox shallow-merge bug
  • [Bug]: WebUI displays "No output" for all tool results even though stdout contains data openclaw/openclaw#38223 WebUI tool-result "No output" rendering bug
  • [Bug]: [Bug]: Webchat shows duplicate assistant messages because chat.history returns delivery-mirror transcript entries as normal assistant messages openclaw/openclaw#38061 webchat duplicate assistant messages from delivery-mirror entries

Current blocker:

• GitHub Project board creation is still blocked locally because gh still reports missing read:project scope.
• I can keep moving with Issue + Discussion + diary logs in the meantime.

Next:

1. Pick the first issue with the best mergeability/scope ratio
2. Implement locally
3. Open the first PR and continue logging progress

[clawbie]

Project board is live:

• https://github.com/users/clawbie/projects/1

Seeded items:

• Progress log issue (OpenClaw contribution log #1 in clawbie/openclaw)
• Telegram: expose streamThrottleMs config for smoother native draft streaming openclaw/openclaw#38066 Telegram draft streaming throttle configurability
• [Bug]: Cron isolated sessions lose sandbox.docker.dangerouslyAllow* flags due to shallow Object.assign on agents.defaults openclaw/openclaw#38067 cron isolated sandbox shallow-merge bug
• [Bug]: WebUI displays "No output" for all tool results even though stdout contains data openclaw/openclaw#38223 WebUI tool-result "No output" bug
• [Bug]: [Bug]: Webchat shows duplicate assistant messages because chat.history returns delivery-mirror transcript entries as normal assistant messages openclaw/openclaw#38061 webchat duplicate assistant messages bug

I’ll use this as the active pipeline board going forward.

[clawbie]

Decision recorded: contribution work will now run as a continuous pipeline rather than only on explicit user nudges.

Working mode:

• Maintain exactly one active main task at a time
• Use the GitHub Project board as the active queue
• Keep progress synced to:
  • Project board
  • clawbie/openclaw issue OpenClaw contribution log #1
  • clawbie/diary log file
• Continue autonomously unless blocked by:
  • missing permissions/resources
  • risky external action requiring explicit confirmation
  • unclear technical direction that needs a user call

Immediate next phase:

1. Clean up duplicate PR lines
2. Pick the strongest surviving mainline PR
3. Continue implementation/review follow-up from there

[clawbie]

Watchdog update (2026-03-07 08:44 CST)

• Audited the current contribution state across the project board, progress-log issue, fork PR queue, and diary.
• Cleared duplicate PR clutter so each duplicate bug line has one surviving fork mainline PR:
  • closed fix(ui): show tool stdout when toolResult content is nested #2, fix(webui): render tool_result nested text output #4, fix(webui): render tool_result content output #7 in favor of fix(ui): render tool_result content blocks in tool cards #8 for issue [Bug]: WebUI displays "No output" for all tool results even though stdout contains data openclaw/openclaw#38223
  • closed fix(webchat): hide delivery-mirror transcript entries #9 in favor of fix(chat.history): hide delivery-mirror transcript entries #10 for issue [Bug]: [Bug]: Webchat shows duplicate assistant messages because chat.history returns delivery-mirror transcript entries as normal assistant messages openclaw/openclaw#38061
• Remaining fork PRs are now the smaller mainline set: fix(ui): render tool_result content blocks in tool cards #8, fix(chat.history): hide delivery-mirror transcript entries #10, fix(systemd): treat user-bus unavailable as not enabled #11, fix(config): accept agents.list[].runtime in schema #6, fix(dotenv): expand env references from .env #5, fix(nextcloud-talk): avoid importing src/infra/abort-signal #3.

Current blocker:

• Upstream PR creation is still blocked for this GitHub account (User is blocked (createPullRequest)), so progress can be staged in the fork but not promoted upstream automatically.

Next action:

• Pick exactly one surviving PR as the active main task and keep pushing that line only, instead of spawning new parallel work.

[clawbie]

Watchdog update (2026-03-07 08:54 CST)

• Chose exactly one active main task: issue openclaw onboard --install-daemon broken on v2026.3.2 (works on v2026.3.1) openclaw/openclaw#38379 / fork PR fix(systemd): treat user-bus unavailable as not enabled #11 fix(systemd): treat user-bus unavailable as not enabled.
• Why this line: it is the smallest surviving fork PR (2 files, focused regression fix, direct user-facing onboarding breakage, clean branch state).
• Verified current fork PR state: clawbie/openclaw#11 is open, merge state CLEAN, with no pending checks reported on the fork branch.
• Verified local patch scope against fork main: only src/daemon/systemd.ts and src/daemon/systemd.test.ts change.
• Concrete blocker: local repo does not currently have dependencies installed, so test execution could not be completed here (pnpm exec vitest ... failed because vitest is unavailable without install).
• Separate standing blocker remains unchanged: this account still cannot create upstream PRs automatically (User is blocked (createPullRequest)), so the work can be prepared in the fork but not promoted upstream from automation.

Next action:

1. Keep openclaw onboard --install-daemon broken on v2026.3.2 (works on v2026.3.1) openclaw/openclaw#38379 / fix(systemd): treat user-bus unavailable as not enabled #11 as the only active main task.
2. If/when dependencies are available, run the targeted systemd test to strengthen confidence.
3. Otherwise keep the line staged and avoid starting new implementation while this task still has a clear next step.

[clawbie]

Watchdog update (2026-03-07 08:59 CST)

• Re-checked the single active main task: upstream issue openclaw/openclaw#38379 (openclaw onboard --install-daemon broken on v2026.3.2).
• Re-checked mainline state for that issue: upstream now has multiple active PRs (#38397, #38407, #38424), so our fork-side PR clawbie/openclaw#11 was no longer reducing uncertainty; it was duplicate clutter.
• Converged the queue by closing fork PR #11 and leaving the issue itself as the tracked active task on the project board.
• Current strongest visible mainline candidate is openclaw/openclaw#38424:
  • all substantive CI checks passed
  • only the routine secrets job failed
  • includes the targeted systemd.test.ts coverage path
• Precise blocker is now external to our fork:
  • upstream already has competing/follow-up PRs on the same fix line
  • this GitHub account is still blocked from creating upstream PRs (User is blocked (createPullRequest))
  • so there is no distinct, non-duplicate code action to take on this task right now from this account

Next action:

1. Keep #38379 as the only active main task.
2. Monitor for upstream resolution/merge on #38424 (or another surviving upstream PR on the issue).
3. Do not start new implementation while this task is still active but externally blocked.

[clawbie]

Watchdog update (2026-03-07 09:04 CST)

• Re-checked the single active main task: upstream issue openclaw/openclaw#38379 (openclaw onboard --install-daemon broken on v2026.3.2).
• Re-audited the upstream PR field for that issue: #38397, #38407, #38424.
• Strongest visible mainline candidate remains openclaw/openclaw#38424:
  • all substantive CI checks passed
  • only the routine secrets job failed
  • includes the targeted systemd.test.ts coverage path
• Confirmed fork duplicate cleanup holds: clawbie/openclaw#11 is closed, so there is no extra fork-side PR clutter on this line now.
• Synced this state into clawbie/diary as well.

Precise blocker:

• upstream already has competing/follow-up PRs on the same fix line
• this GitHub account is still blocked from creating upstream PRs (User is blocked (createPullRequest))
• so there is no distinct, non-duplicate code action to take on this task right now from this account

Next action:

1. Keep #38379 as the only active main task.
2. Monitor upstream resolution/merge on #38424 (or another surviving upstream PR on the issue).
3. Do not start new implementation while this task remains externally blocked.

[clawbie]

Watchdog update — 2026-03-07 09:19 CST

Re-checked the single active main task: openclaw/openclaw#38379.

Current upstream PR state

• Fix systemd daemon install failing when user session bus not active openclaw/openclaw#38424 — strongest mainline candidate
  • all substantive CI checks passed
  • only routine secrets failed
  • clean, targeted fix; no obvious unrelated payload
• fix(daemon): treat systemd bus connection failure as 'not enabled' during onboard openclaw/openclaw#38397 — weaker than Fix systemd daemon install failing when user session bus not active openclaw/openclaw#38424
  • CI mostly green, but review noted the added test does not actually exercise the new bus-failure path
• fix: handle 'failed to connect to bus' in isSystemdServiceEnabled openclaw/openclaw#38407 — currently noisy / not a good mainline candidate
  • includes unrelated WHEELJACK_LOG.md
  • also has a failing check job in addition to secrets

Decision

Keep openclaw#38379 as the only active main task and treat openclaw#38424 as the current mainline PR to watch.

Precise blocker

External blocker, not a coding blocker:

• upstream already has competing PRs on the same fix line
• this account still cannot create upstream PRs (User is blocked (createPullRequest))
• starting another implementation now would just create duplicate clutter

Next action

Do not start new work yet. Wait for upstream convergence on #38424 (or another surviving PR on #38379 if maintainers redirect).

[clawbie]

Progress update — 2026-03-07 09:24 CST

• Active main task: upstream issue openclaw/openclaw#38379 (openclaw onboard --install-daemon fails when systemd user bus is unavailable during first-run provisioning).
• Project board state: item is already correctly marked In Progress.
• Mainline PR to watch: openclaw/openclaw#38424.
  • Scope is the cleanest of the open contenders.
  • CI is broadly green; the only visible red is the usual secrets noise.
  • Automated review note is minor parity follow-up, not a blocker.
• Competing PRs:
  • #38397 also looks viable, but its added test appears not to exercise the new branch correctly per review.
  • #38407 is cluttered by an accidental WHEELJACK_LOG.md commit, so not the PR to rally behind.
• Fork-side clutter: my duplicate fork PR clawbie/openclaw#11 is already closed.

Clear next action: keep attention on openclaw/openclaw#38424 and wait for upstream maintainer review/merge rather than spinning up new work.

Precise blocker: no maintainer decision yet on the upstream PR set for #38379.

This keeps the project on a single active main task and converges on one mainline PR instead of growing more duplicates.

[clawbie]

Watchdog update — 2026-03-07 09:40 CST

• Re-checked the single active main task: upstream issue openclaw/openclaw#38379 remains the only In Progress item on the GitHub Project board.
• Re-checked upstream PR state linked to that issue:
  • #38424 is still the strongest mainline candidate.
  • #38397 remains viable but weaker because its test-coverage concern is still unresolved.
  • #38407 remains the noisier line because it still carries unrelated payload and a failing check job.
• Fresh signal on the current lead PR #38424:
  • Greptile flagged a small parity gap: the patch handles "failed to connect to bus" but not the sibling string "failed to connect to user scope bus" that is already recognized elsewhere in the same file.
  • That is not a merge blocker, but it is the only concrete follow-up note visible on the lead PR right now.

Decision:

• Keep #38379 as the only active main task.
• Keep #38424 as the mainline PR to watch.

Precise blocker:

• no maintainer merge/review decision yet on the upstream PR set for #38379
• this account is still blocked from creating upstream PRs (User is blocked (createPullRequest))
• so starting another implementation now would only recreate duplicate clutter

Next action:

• Wait for upstream convergence on #38424 (or maintainer redirect to another surviving PR on #38379).
• Do not start new work while this active task still has a clear next step.

[clawbie]

Watchdog update — 2026-03-07 09:44 CST

• Single active main task remains openclaw/openclaw#38379 (openclaw onboard --install-daemon broken on v2026.3.2).
• Current upstream PR state still converges on one mainline candidate:
  • openclaw/openclaw#38424 remains the strongest line to watch.
  • All substantive CI checks passed.
  • Only the routine secrets job failed.
  • Review signal is minor (failed to connect to user scope bus parity note), not a blocker.
• Competing PRs remain weaker:
  • #38397 is viable but weaker than #38424.
  • #38407 still has a failing check job and extra clutter, so it is not the line to rally behind.
• Duplicate fork clutter remains reduced:
  • clawbie/openclaw#11 is already closed.

Clear next action

Keep exactly one main task (#38379) and wait for upstream maintainer convergence on #38424 (or explicit redirection to another surviving PR on the same issue).

Precise blocker

No distinct non-duplicate code action is available from this account right now because:

1. upstream already has multiple active PRs on the exact fix line, and
2. this account is blocked from opening upstream PRs (User is blocked (createPullRequest)).

[clawbie]

Watchdog update 2026-03-07 09:49 CST

• Re-checked the single active main task and project board state. openclaw/openclaw#38379 remains the only In Progress item.
• Re-checked competing upstream PRs for that task:
  • openclaw/openclaw#38424 remains the strongest mainline candidate: broad CI green, only routine secrets red.
  • openclaw/openclaw#38397 remains viable but weaker.
  • openclaw/openclaw#38407 remains the weakest line due to an additional real check failure.
• No clear non-duplicate implementation move exists from this fork right now, so the correct action is still to hold the line on #38379 and wait for upstream convergence on #38424.
• Precise blocker:
  • no maintainer merge / direction yet on the upstream PR cluster for #38379
  • account clawbie still cannot create upstream PRs directly (User is blocked (createPullRequest))
• Duplicate/obsolete PR clutter remains converged: fork-side duplicate PR #11 stays closed, and no new duplicate line was opened.

[clawbie]

Watchdog update 2026-03-07 09:54 CST

• Re-checked the single active main task on the project board: openclaw/openclaw#38379 remains the only In Progress item.
• Re-audited the upstream PR cluster for that issue:
  • openclaw/openclaw#38424 is still the clear mainline candidate: all substantive CI is green; only the routine secrets job is failing.
  • openclaw/openclaw#38397 remains weaker because automated review correctly noted the added test does not actually exercise the new bus-failure branch.
  • openclaw/openclaw#38407 remains non-mainline because it still carries accidental WHEELJACK_LOG.md clutter and also has a real failing check job.
• No new duplicate fork cleanup was needed this pass; clawbie/openclaw#11 remains closed.
• Precise blocker is unchanged: upstream maintainer convergence is still pending on the existing #38379 PR set, and this account is still blocked from opening upstream PRs directly (User is blocked (createPullRequest)).

Next action stays the same: keep #38379 as the only active main task and wait for upstream convergence on #38424 (or explicit maintainer redirection).

[clawbie]

已记录新的执行要求：

• 内部巡检频率：从每 5 分钟改为每 10 分钟一次
• 用户状态汇报频率：从每 30 分钟改为每 1 小时一次
• 从现在开始，所有汇报内容与日志内容统一使用中文

这包括：

• GitHub 进展日志
• diary 里的项目日志
• 定时状态汇报
• 后续与该项目相关的工作记录

[clawbie]

巡检更新 2026-03-07 10:19 CST

• 已按最新执行要求切换为中文日志模式；后续该项目的进展记录、diary 和定时汇报统一使用中文。
• 重新核对 GitHub Project、clawbie/openclaw#1、clawbie/diary 三处事实源后，状态没有漂移：
  • openclaw/openclaw#38379 仍然是唯一主任务，也是看板上唯一的 In Progress 项
  • openclaw/openclaw#38424 仍然是当前最强的主线 PR 候选
• 当前主线判断维持不变：
  • #38424：实质性 CI 仍全绿，只有例行 secrets 失败；现有评审意见只是小的同类错误字符串补齐提示，不足以另开新线
  • #38397：仍次优，主要问题还是测试没有真正命中新增分支
  • #38407：仍非主线候选，原因是包含无关文件且 check 任务失败
• 精确阻塞点不变：
  • 上游已在 #38379 这一修复线上有多个活跃 PR
  • clawbie 账户仍无法直接创建上游 PR（User is blocked (createPullRequest)）
  • 所以当前没有新的、非重复的代码动作可做

下一步：继续只保留 #38379 这一条主任务，继续观察 #38424 的上游维护者收敛/合并结果，不启动新的重复实现。