Changed module resolution from Node16 to Bundler (with ESNext module) to
properly resolve openclaw/plugin-sdk type exports. This fixes build errors
where OpenClawPluginApi and jsonResult types were not being found.
The Node16 module resolution was not following the re-exports in openclaw's
plugin-sdk index.d.ts correctly. Bundler resolution is more compatible with
modern package.json exports.
Co-Authored-By: Claude Sonnet 4.5 <noreply@anthropic.com>
First stable release of DevClaw, transforming OpenClaw into a
complete dev team management system.
Key features:
- Autonomous multi-project development pipeline
- Intelligent tier-based model selection (Junior/Medior/Senior)
- Token-free scheduling with work_heartbeat
- 60-80% token savings through tier selection and session reuse
- GitHub/GitLab integration with atomic operations
- Comprehensive tooling and documentation
Co-Authored-By: Claude Sonnet 4.5 <noreply@anthropic.com>
Major changes:
- Add autoconfigure_models tool for intelligent model assignment
- Implement LLM-based model selection using openclaw agent
- Improve onboarding flow with better model access checks
- Update README with clearer installation and onboarding instructions
Technical improvements:
- Add model-fetcher utility to query authenticated models
- Add smart-model-selector for LLM-driven model assignment
- Use session context for LLM calls during onboarding
- Suppress logging from openclaw models list calls
Documentation:
- Add prerequisites section to README
- Add conversational onboarding example
- Improve quick start flow
Co-Authored-By: Claude Sonnet 4.5 <noreply@anthropic.com>
## Changes
### lib/templates.ts (AGENTS.md template)
- Added 'Critical: You Do NOT Write Code' section to orchestrator instructions
- Listed what orchestrator CAN do (planning, analysis, status checks)
- Listed what MUST go through workers (code, git ops, tests)
- Added 'Never write code yourself' to Safety section
### README.md
- Added 'The orchestrator's role' section explaining the workflow boundary
- Table showing what goes through workers vs orchestrator
- Explained why: audit trail, tier selection, parallelization, QA pipeline
### docs/ARCHITECTURE.md
- Updated scope boundaries diagram to show 'planning only' for orchestrator
- Added key boundary note about planner/dispatcher role
Addresses issue #133
Enhanced the DevClaw onboarding flow to address real-world usability issues
discovered during testing.
Changes:
1. Model Selection Improvements (Step 2):
- Added explicit prompt to check user's available models first
- Changed 'Default Model' table to 'Suggested default' to emphasize flexibility
- Added model selection guidance with class descriptions:
* junior/tester: Fast, cheap (Haiku-class, GPT-4-mini)
* medior/reviewer: Balanced (Sonnet-class, GPT-4)
* senior: Most capable (Opus-class, o1)
- Emphasized guiding users to configure finer-grained mappings
- Added warning that defaults are suggestions, not requirements
2. Telegram Group Setup Guidance (New Step 4):
- Added comprehensive section on project isolation best practices
- Explains the one-group-per-project model clearly
- Provides rationale:
* Clean issue backlogs per project
* Isolated worker state
* Clear audit trails
* Team-specific access control
- Documents mention requirement (@botname command)
- Includes single-project mode option with strong warning
- Provides tip for getting group ID from bot
3. Improved Flow:
- Renumbered steps (Project Registration is now Step 5)
- Added group ID discovery tip
- Maintained conversational tone while being more explicit
Impact:
- Prevents configuration failures from using unavailable models
- Guides users toward sustainable multi-project setup
- Reduces support burden by proactively explaining best practices
- Still allows single-project mode for solo developers
Addresses issue #132
Replaced dense inline-linked paragraphs with a short intro sentence
per pillar followed by bullet points. Each bullet is one concept with
one link. Removed the ASCII parallelization diagram.
https://claude.ai/code/session_01R3rGevPY748gP4uK2ggYag
Trimmed the chat transcript: removed separate "You jump in" section,
inlined a single human message within the webapp group flow, dropped
Linear sync in favor of GitHub issue creation. Shorter, tighter.
https://claude.ai/code/session_01R3rGevPY748gP4uK2ggYag
Auto-chaining was removed from the codebase. All docs now describe the
scheduling model: work_finish transitions labels, the heartbeat's tick
pass (which also fires immediately after every work_finish) detects
available work and fills free slots. Removed autoChain config references.
Files updated: README.md, README2.md, docs/TOOLS.md, ARCHITECTURE.md,
ROADMAP.md, MANAGEMENT.md, ONBOARDING.md, lib/templates.ts
https://claude.ai/code/session_01R3rGevPY748gP4uK2ggYag
Single unbroken group-chat transcript now flows from autonomous work,
through human planning/steering, syncing issues to Linear, and back
to autonomous execution — showing everything happens in the same
conversation.
https://claude.ai/code/session_01R3rGevPY748gP4uK2ggYag
Manual interaction example now shows creating issues, sequencing work,
and parking tasks in Planning — all in the same conversation where
autonomous execution happens.
https://claude.ai/code/session_01R3rGevPY748gP4uK2ggYag
Show two projects running overnight with heartbeat-driven dispatch,
auto-chaining, QA failures cycling back to DEV, and different developer
levels — all without human involvement. Manual mode shown as secondary.
https://claude.ai/code/session_01R3rGevPY748gP4uK2ggYag
- Bundle task management: issue tracker integration, creating/updating/commenting,
custom instructions per project — all in one section
- Add automatic scheduling section: heartbeat service, auto-chaining, execution
modes, with full config snippets and settings table
- Remove standalone "Parallel everything" section (folded into scheduling)
- Simplify team tables: Level / Assigns to / Model columns
https://claude.ai/code/session_01R3rGevPY748gP4uK2ggYag
Complete from-scratch rewrite of the README with an OpenClaw user perspective:
- Opens with a concrete group chat interaction showing the full flow
- Frames the problem as "babysitting the thing you built to avoid babysitting"
- "Meet your team" section makes the model mapping fun and relatable
- Pipeline explained as a story, not a spec
- Behind-the-scenes section covers session reuse, heartbeat, auto-chaining
- Issue tracker integration framed as "your issues, your tracker"
- Onboarding shown as a natural conversation
- Tools framed as guardrails, not API endpoints
https://claude.ai/code/session_01R3rGevPY748gP4uK2ggYag
- Add "Why DevClaw" paragraph explaining the gap between raw OpenClaw and development orchestration
- Rename "Shared sessions" to "Session re-use (context preservation)" in token savings
- Add "External task state" benefit covering GitHub/GitLab integration and pluggable IssueProvider
- Simplify installation to conversational onboarding with full example dialogue
- Move "How it works" and "Session reuse" diagrams to ARCHITECTURE.md (keep reference)
- Add Architecture section with link to detailed technical documentation
- Explain tools as guardrails that encode operations as deterministic code
https://claude.ai/code/session_01R3rGevPY748gP4uK2ggYag
Complete documentation rewrite to match the current codebase:
- README: add benefits section (process consistency, token savings with
estimates, project isolation, continuous planning, feedback loops,
role-based prompts, atomic operations, audit trail), task workflow
with state diagram, model-to-role mapping tables, installation guide
- New TOOLS.md: complete reference for all 11 tools with parameters,
behavior, and execution guards
- New CONFIGURATION.md: full config reference for openclaw.json,
projects.json, heartbeat, notifications, workspace layout
- Fix tool names across all docs: task_pickup→work_start,
task_complete→work_finish
- Fix tier model: QA has reviewer/tester levels, not flat "qa"
- Fix config schema: nested models.dev.*/models.qa.* structure
- Fix prompt path: projects/roles/ not projects/prompts/
- Fix worker state: uses "level" field not "model"/"tier"
- Fix MANAGEMENT.md: remove incorrect model references
- Fix TESTING.md: update model config example to nested structure
- Remove VERIFICATION.md (one-off checklist, no longer needed)
- Add cross-references between all docs pages
https://claude.ai/code/session_01R3rGevPY748gP4uK2ggYag
Problem:
The work_start tool was automatically running a 'tick' after picking up
an issue, which filled parallel worker slots by dispatching additional
workers for other issues without explicit instruction.
Example: Picking up #123 also auto-dispatched QA for #121 via tickPickups.
Root Cause:
work_start called tickAndNotify() which ran projectTick() to fill free
worker slots in parallel execution mode. This behavior was automatic and
not controllable.
Solution:
- Disabled the auto-tick functionality in work_start
- Commented out the tickAndNotify call
- Removed tickPickups from the response
- Updated documentation to reflect the change
Impact:
- work_start now picks up ONLY the explicitly requested issue
- No automatic worker dispatch for parallel slots
- For filling worker slots, use work_heartbeat instead
- Gives more control over worker assignments
Changes:
- lib/tools/work-start.ts:
* Commented out tickAndNotify call
* Removed tickPickups from output
* Updated file header comment
* Updated tool description
Addresses issue #125
- Updated WorkerState type to use 'level' instead of 'tier'.
- Modified functions related to worker state management, including parseWorkerState, emptyWorkerState, getSessionForLevel, activateWorker, and deactivateWorker to reflect the new terminology.
- Adjusted health check logic to utilize 'level' instead of 'tier'.
- Refactored tick and setup tools to accommodate the change from 'tier' to 'level', including model configuration and workspace scaffolding.
- Updated tests to ensure consistency with the new 'level' terminology.
- Revised documentation and comments to reflect the changes in terminology from 'tier' to 'level'.
- Introduced a new heartbeat service that runs at defined intervals to perform health checks on workers and fill available task slots based on priority.
- Added a health tool to scan worker health across projects with optional auto-fix capabilities.
- Updated the status tool to provide a lightweight overview of worker states and queue counts without health checks.
- Enhanced task creation tool descriptions to clarify task state handling.
- Implemented tests for the work heartbeat logic, ensuring proper project resolution, worker state management, and task prioritization.
Remove TEST.md which was created for testing purposes (issue #105)
and should not be in the repository.
File contained test content about Lauren ten Hoor profile information
and was not part of the core project functionality.
Addresses issue #117
Issue #115 requested changing the default from 'To Do' to 'Planning',
but investigation reveals this is already implemented.
Findings:
- Code has defaulted to 'Planning' since initial commit (8a79755e, Feb 9)
- README documentation correctly states 'defaults to Planning' (line 308)
- Tool description confirms 'defaults to Planning' behavior
Timeline:
- Feb 9, 2026: task_create implemented with Planning default
- Feb 10, 2026: Issue #115 filed (requesting already-implemented feature)
No code changes needed - feature already works as requested.
Added VERIFICATION.md documenting the current implementation and
providing evidence that the requested behavior is already active.
Addresses issue #115
