Skip to content

fix(status): clarify bootstrap summary wording#492

Open
BingqingLyu wants to merge 1 commit into
mainfrom
fork-pr-43614-fix-status-bootstrap-wording
Open

fix(status): clarify bootstrap summary wording#492
BingqingLyu wants to merge 1 commit into
mainfrom
fork-pr-43614-fix-status-bootstrap-wording

Conversation

@BingqingLyu

@BingqingLyu BingqingLyu commented Apr 27, 2026

Copy link
Copy Markdown
Owner

Summary

  • clarify the openclaw status agent summary when no workspace is actively bootstrapping
  • stop describing mature workspaces without BOOTSTRAP.md as having no bootstrap files
  • add regression coverage for the steady-state wording

Problem

status was using bootstrapPendingCount === 0 to print no bootstrap files, but that signal only means no workspace is currently in the one-shot bootstrap phase. Mature workspaces can still inject AGENTS.md, SOUL.md, TOOLS.md, and related files normally.

Testing

  • G:\Rust\openclaw\node_modules\.bin\vitest.cmd run src/commands/status.test.ts --reporter=dot -t "prints formatted lines otherwise|describes mature workspaces as not actively bootstrapping"

Linked Issue

Transparency

  • AI-assisted: implemented with Codex

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

[Bug]: status says "no bootstrap files" when only BOOTSTRAP.md is absent

1 participant