Add an explicit hidden automation-run or visible normal-task target, make
repository-free firings use task-owned scratch execution, and preserve exact
continuation/run accounting in both modes. Work is sequential because the
persisted contract and dispatch lifecycle must land before the editor and E2E
flows can rely on them.
Scope
In scope
Persist target mode and explicit repository mode with compatibility migration.
Admit and dispatch hidden repository/workflow-free runs.
Create, continue, finalize, and delete visible normal tasks without applying
hidden coordinator authority or hidden cleanup.
Expose target, workflow, repository, executor, and continuity choices with
accessible desktop/mobile copy and equal toolbar button heights.
Add backend, frontend, mobile, export, and end-to-end regression coverage.
Update public automation documentation and feature status.
Out of scope
Concurrent turns or additional sessions on a reusable target.
Per-automation MCP capability selection.
Automatic repository provisioning.
Converting an existing hidden task into a visible task in place.
Technical approach
Add typed task_mode and repository_mode contracts in
internal/automation, including store migration, request validation, export,
and compatibility defaults.
Split orchestrator task creation into hidden and visible target paths while
sharing title rendering, continuation admission, exact run binding, and
repository resolution. Add a visible automation task origin and use the
existing lifecycle scratch path for empty repository lists.
Route terminal run accounting by exact run identity. Keep hidden
SurfaceAutomation and hidden cleanup constrained to hidden origin tasks;
leave visible tasks in the normal task lifecycle on automation deletion.
Extend the editor payload and types with target/repository modes, allow
Worktree and Local-compatible profiles to use repository-free scratch,
require workflow only for visible mode, and keep descriptions accessible on
phones.
Add focused tests and E2E flows for both modes, then update public docs and
verification evidence.
Tests
internal/automation: schema/default/migration, target validation,
repository-mode resolution, export, and open-run behavior.
internal/orchestrator: hidden no-repo launch, visible task creation,
visible continuation, exact completion/stop, normal profile selection, and
deletion ownership.
internal/task/repository/sqlite and internal/task/service: visible
automation origin appears in task queries and accepts scratch tasks.
apps/web/components/runs: shared transcript and visible-run terminal paths.
E2E tests
Desktop: create a no-repository/no-workflow hidden automation with Worktree,
run it in scratch, and verify it succeeds without a repository error.
Desktop: create a workflow-backed normal-task automation, fire it with
new_task, and verify the task appears in the Kanban/sidebar and its run
completes.
Desktop/mobile: switch both target and continuity settings, read the visible
explanations, exercise a reusable visible task, and assert no horizontal
overflow. Verify Export and New Automation have equal height.
Backend: 2,937 automation, orchestrator, and backendapp tests passed. Earlier
task service/repository, MCP, and lifecycle suites remain green on this PR.
Frontend: 31 focused files and 296 tests passed; typecheck, i18n check, and
i18n ratchet passed.
Desktop E2E: all 19 automation-settings tests and both target-mode tests
passed. The target-mode flow proves repository-free Worktree execution and
visible task placement in the workflow's configured start step.
Mobile E2E: all three automation settings/scroll tests passed, including
44-pixel shared selectors and horizontal-overflow assertions.
Public docs: 61 validator tests and 41 published-page validations passed.
git diff --check passed.
Risks
Reusing an empty repository list without a migration mode would silently
change existing automations from workspace-default to scratch execution.
A visible task accidentally marked with the hidden origin would disappear
from boards or receive coordinator self-target restrictions.
Shared continuation code can finalize the wrong visible run unless every
completion and stop path carries the exact session and turn.
Worktree profiles must keep using scratch rather than Git worktree
preparation when no repository is attached.
Compatibility requests that name only repository IDs must resolve concrete
base branches without restoring the removed first-repository fallback.