Skip to content

feat: add Dr. Claw CLI and OpenClaw integration workflow#36

Merged
Zhang-Henry merged 10 commits intomainfrom
feat/openclaw-integration
Mar 21, 2026
Merged

feat: add Dr. Claw CLI and OpenClaw integration workflow#36
Zhang-Henry merged 10 commits intomainfrom
feat/openclaw-integration

Conversation

@davidliuk
Copy link
Copy Markdown
Collaborator

Summary

  • add the new drclaw CLI surface for project, session, chat, task, workflow, digest, and notification workflows
  • wire OpenClaw-facing skills, install scripts, and onboarding docs so OpenClaw can operate Dr. Claw from shell/CLI reliably
  • extend server APIs and project creation flow to support project bootstrapping, progress tracking, task/workflow controls, and richer status/digest outputs
  • preserve compatibility through the legacy vibelab package path while shifting docs and user-facing naming to Dr. Claw

What changed

  • introduced agent-harness/cli_anything/drclaw as the primary CLI package, including JSON-friendly output, waiting-session inspection, reply flows, digests, portfolio summaries, progress reporting, task/workflow actions, notifications, and OpenClaw push helpers
  • kept agent-harness/cli_anything/vibelab as a compatibility shim so existing environments and OpenClaw setups do not break during the rename
  • added OpenClaw skill documentation and helper scripts under agent-harness/skills/dr-claw plus installer/setup updates for easier local installation and integration
  • updated root documentation and Chinese documentation with Dr. Claw branding, install steps, OpenClaw integration guidance, and usage examples
  • expanded server support in server/index.js, server/routes/projects.js, and server/routes/taskmaster.js for project creation, workflow/task control, progress/status data, and CLI-facing operations
  • updated the project creation wizard and API helper to match the new project bootstrap flow

Why

This PR turns Dr. Claw into a practical control surface for OpenClaw and mobile assistant use cases:

  • users can inspect waiting sessions and reply without opening the web UI
  • OpenClaw can call a stable CLI surface to manage projects, sessions, digests, and workflow continuation
  • the server now exposes the missing backend capabilities the CLI needs for task control and progress reporting
  • the rename to Dr. Claw is reflected in docs and command surfaces without breaking old integrations immediately

Validation

  • pushed and exercised the branch locally through the Dr. Claw CLI and OpenClaw shell-based flows during development
  • added/updated CLI tests under both agent-harness/cli_anything/drclaw/tests and the compatibility vibelab path
  • confirmed the branch is publishable as feat/openclaw-integration

Follow-ups

  • remove the legacy vibelab compatibility path after downstream OpenClaw and user environments have fully migrated
  • clean up the OpenClaw local Feishu plugin duplication/runtime version mismatch separately so inbound bot replies are reliable end-to-end

@davidliuk davidliuk requested a review from bbsngg March 16, 2026 15:42
@davidliuk davidliuk force-pushed the feat/openclaw-integration branch from a16bbdd to de28e52 Compare March 16, 2026 19:15
@bbsngg
Copy link
Copy Markdown
Contributor

bbsngg commented Mar 17, 2026

Need to align with Dr. Claw instead of Vibe Lab. @davidliuk

Copy link
Copy Markdown
Collaborator

@Zhang-Henry Zhang-Henry left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Review Comments

Overlaps heavily with PR #44

Both PRs introduce the drclaw and vibelab Python CLI packages with identical code. These need to be coordinated — one should be the canonical source, not both.

Massive code duplication

drclaw/ and vibelab/ are identical copies. Use a single package with an alias entry point.

PR is too large to review effectively

12,553 additions in a single PR covering CLI code, server route changes, skill docs, and integration guides. Please break it into:

  1. Server API changes (taskmaster.js, projects.js)
  2. CLI package (drclaw)
  3. Documentation and skills

No deprecation plan for vibelab package

The PR body mentions "remove legacy vibelab path after downstream migration" but provides no timeline or deprecation warnings in the code/docs.

@davidliuk
Copy link
Copy Markdown
Collaborator Author

Thanks for the feedback. I agree with the concerns regarding PR size and code duplication. I will refine this PR and resubmit as follows:

  • De-duplication: I’ll keep drclaw/ as the canonical source and use a single package with an alias entry point for vibelab to eliminate identical code.
  • PR Splitting: To make review manageable, I will break the ~12k lines into three smaller PRs:
    • Server API changes (taskmaster.js, projects.js)
    • CLI package (drclaw)
    • Docs & Skills
  • Deprecation: I will add a FutureWarning to the vibelab entry point and include a clear removal timeline in the documentation.

@davidliuk davidliuk force-pushed the feat/openclaw-integration branch from de28e52 to 17695cd Compare March 20, 2026 19:49
davidliuk and others added 4 commits March 20, 2026 22:55
- Fix workflow_resume passing images= instead of attachments= to send_message
- Add missing ctx parameter to openclaw notification tests
- Narrow warnings.filterwarnings to DeprecationWarning only
- Internationalize _recommend_project_attention hardcoded Chinese strings
- Fix duplicate DrClaw import in core/__init__.py (export VibeLab)
- Replace bare except with except Exception
- Move mid-file base64/mimetypes imports to top of file
@Zhang-Henry Zhang-Henry merged commit b5fcfc0 into main Mar 21, 2026
1 check passed
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.

3 participants