feat: add Dr. Claw CLI and OpenClaw integration workflow#36
feat: add Dr. Claw CLI and OpenClaw integration workflow#36Zhang-Henry merged 10 commits intomainfrom
Conversation
a16bbdd to
de28e52
Compare
|
Need to align with Dr. Claw instead of Vibe Lab. @davidliuk |
Zhang-Henry
left a comment
There was a problem hiding this comment.
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:
- Server API changes (
taskmaster.js,projects.js) - CLI package (
drclaw) - 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.
|
Thanks for the feedback. I agree with the concerns regarding PR size and code duplication. I will refine this PR and resubmit as follows:
|
…claw alias with deprecation warnings
de28e52 to
17695cd
Compare
- 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
Summary
drclawCLI surface for project, session, chat, task, workflow, digest, and notification workflowsvibelabpackage path while shifting docs and user-facing naming to Dr. ClawWhat changed
agent-harness/cli_anything/drclawas 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 helpersagent-harness/cli_anything/vibelabas a compatibility shim so existing environments and OpenClaw setups do not break during the renameagent-harness/skills/dr-clawplus installer/setup updates for easier local installation and integrationserver/index.js,server/routes/projects.js, andserver/routes/taskmaster.jsfor project creation, workflow/task control, progress/status data, and CLI-facing operationsWhy
This PR turns Dr. Claw into a practical control surface for OpenClaw and mobile assistant use cases:
Validation
agent-harness/cli_anything/drclaw/testsand the compatibilityvibelabpathfeat/openclaw-integrationFollow-ups
vibelabcompatibility path after downstream OpenClaw and user environments have fully migrated