Support ~/work as a second Pipeline domain

t-631·WorkTask·
·
·
·Omni/Pipeline.hs
Created1 month ago·Updated1 week ago·pipeline runs →

Description

Edit

Add multi-domain support to Pipeline so it can run against ~/work independently from the omnirepo.

Changes needed

1. TASK_DB_PATH support in Pipeline — Pipeline should accept a --task-db flag (or config field) that sets TASK_DB_PATH when spawning agents. The task CLI already supports TASK_DB_PATH env var, so this is just plumbing it through. Initialize a new DB at ~/work/tasks.db with: TASK_DB_PATH=~/work/tasks.db task init

2. Auto-discover AGENTS.md from pcRepoRoot — The dev prompt builder (Dev.buildDevPrompt) currently injects omni-specific context. It should auto-discover <pcRepoRoot>/AGENTS.md instead of hardcoding omni's path. Optionally expose a --agents-md flag for explicit override.

3. CODEROOT / pcRepoRoot — Already configurable. Just needs to be set to ~/work when running for that domain. No code changes required, just config/docs.

4. Run config for ~/work domain — Document or create a config entry (e.g. in fund domain registry or a shell alias) so the user can launch a Pipeline instance pointed at ~/work with the correct CODEROOT, TASK_DB_PATH, and AGENTS.md.

Out of scope

  • Full domain registry / fund integration (that comes later)
  • Any scheduler changes
  • Isolation guarantees between domains (informal phase)

Goal

After this task, the user should be able to run two Pipeline instances: one for omnirepo and one for ~/work, each with their own task DB and AGENTS.md context.

Timeline (21)

🔄[system]Open → InProgress1 month ago
💬[system]1 month ago

Pipeline: dev completed (run=dev-t-631-1771479735, cost=0.0c)

🔄[system]InProgress → Open1 month ago
💬[system]1 month ago

Pipeline: verification failed: Build failed for omni.hs (exit 1): 7[10000;10000H

[0m[38;5;1m[2Kfail: bild: nothing to build [0m[0m [0m

🔄[system]Open → InProgress1 month ago
🔄[system]InProgress → Open1 month ago
💬[system]1 month ago

Pipeline: agent died without producing a commit, resetting

🔄[system]Open → InProgress1 month ago
💬[human]1 month ago

Pipeline scheduler: started run=pipeline-omni-pipeline-hs-t-631-1771562201 domain=Omni/Pipeline.hs

🔄[human]InProgress → Review1 month ago
💬[human]1 month ago

Pipeline scheduler: run=pipeline-omni-pipeline-hs-t-631-1771562201 domain=Omni/Pipeline.hs status=done cost=54c (fund-spend=failed)

💬[human]1 week ago

Ava triage: pipeline auto-run reached status=done but the agent made NO git commits and reported blockers (missing files, path mismatches, or need clarification). This task is not actually in review — there's nothing to review. Resetting status to Open so it can be re-scoped.

🔄[human]Review → Open1 week ago
💬[human]1 week ago

BRANCH EXISTS BUT UNMERGED: coder agent produced commit 12ea4d00 on branch t-631 (2026-02-19) but it was never merged into live. Pipeline scheduler bug — see separate task. To recover: git checkout t-631 or cherry-pick; expect conflicts after drift.