| Age | Commit message (Collapse) | Author |
|
Add --dirty flag to skip stashing behavior. Stashing includes untracked
files and uses a trap to ensure changes are popped back on exit.
|
|
claudomator create <name> -i <instructions> [flags]
--parent-id attach as subtask of given task ID
--working-dir working directory
--model claude model
--budget max USD
--timeout task timeout
--priority high/normal/low
--start queue immediately after creating
deploy script now also copies binary to /usr/local/bin/claudomator.
Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
|
|
Recovered files with no Claude→Agent contamination:
- docs/adr/002-task-state-machine.md
- internal/api/logs.go/logs_test.go: task-level log streaming endpoint
- internal/api/validate.go/validate_test.go: POST /api/tasks/validate
- internal/api/server_test.go, storage/db_test.go: expanded test coverage
- scripts/reset-failed-tasks, reset-running-tasks
- web/app.js, index.html, style.css: frontend improvements
- web/test/: active-tasks-tab, delete-button, filter-tabs, sort-tasks tests
Manually applied from server.go diff (skipping Claude→Agent rename):
- taskLogStore field + validateCmdPath field
- DELETE /api/tasks/{id} route + handleDeleteTask
- GET /api/tasks/{id}/logs/stream route
- POST /api/tasks/{id}/resume route + handleResumeTimedOutTask
- handleCancelTask: allow cancelling PENDING/QUEUED tasks directly
Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
|
|
READY state means a parent task whose subtasks should now run — select
its first PENDING child, not a global fallback. COMPLETED state means
continue the series via the next PENDING sibling. Only fall back to the
priority+age queue when neither yields a task.
Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
|
|
When the most recently completed task had no remaining PENDING siblings
(series fully done), the script returned empty and start-next-task
reported "No task to start." Fix by falling through to the
priority+age fallback whenever the sibling search yields nothing.
Also add header comment documenting the selection logic, and suppress
browser favicon 404s with <link rel="icon" href="data:,">.
Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
|
|
When an agent needs user input it writes a question to
$CLAUDOMATOR_QUESTION_FILE and exits. The runner detects the file and
returns BlockedError; the pool transitions the task to BLOCKED and
stores the question JSON on the task record.
The user answers via POST /api/tasks/{id}/answer. The server looks up
the claude session_id from the most recent execution and submits a
resume execution (claude --resume <session-id> "<answer>"), freeing the
executor slot entirely while waiting.
Changes:
- task: add StateBlocked, transitions RUNNING→BLOCKED, BLOCKED→QUEUED
- storage: add session_id to executions, question_json to tasks;
add GetLatestExecution and UpdateTaskQuestion methods
- executor: BlockedError type; ClaudeRunner pre-assigns --session-id,
sets CLAUDOMATOR_QUESTION_FILE env var, detects question file on exit;
buildArgs handles --resume mode; Pool.SubmitResume for resume path
- api: handleAnswerQuestion rewritten to create resume execution
- preamble: add question protocol instructions for agents
- web: BLOCKED state badge (indigo), question text + option buttons or
free-text input with Submit on the task card footer
Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
|
|
Add LogPather interface; ClaudeRunner implements it via ExecLogDir().
Pool pre-populates stdout_path/stderr_path/artifact_dir on the execution
record before CreateExecution, so paths are in the DB from the moment
a task starts running.
ClaudeRunner.Run() skips path assignment when already set by the pool.
Also update scripts/debug-execution to derive paths from the known
convention (<data-dir>/executions/<exec-id>/) as a fallback for
historical records that predate this change.
Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
|
|
|
|
debug-execution: inspect a failed execution by ID prefix from prod DB.
deploy: build and restart the claudomator systemd service.
Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
|
|
next-task now outputs only the task ID (or nothing), removing prose
prefixes that made downstream parsing fragile. start-next-task
simplifies to a direct empty-check with no awk required.
Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
|