-
Notifications
You must be signed in to change notification settings - Fork 2
Closed
Labels
bugSomething isn't workingSomething isn't workingpriority:P1Critical priorityCritical prioritysquad:cliCLI squadCLI squadtype:codeCode qualityCode quality
Description
Problem
squads obs sync --dry-run reports "No JSONL records to sync" even though executions.jsonl has 57 records.
Root cause: The CLI resolves the JSONL path relative to the current working directory. When invoked from a git worktree (e.g., .worktrees/data-data-lead-xxx/) or any directory other than the hq root, it cannot find .agents/observability/executions.jsonl.
The file actually lives at: hq/.agents/observability/executions.jsonl
Verification:
- Run from worktree:
squads obs sync --dry-run→ "No JSONL records to sync" - File exists with 57 records at hq path
squads tiershows "Observability: 0 executions logged"
Impact
- Tier 2 goal (backfilling Postgres) is blocked — sync always shows 0 records
squads obs historyreturns empty from any non-hq directory- Postgres
agent_executionstable stays at 0 rows despite 57 JSONL records existing
Expected Behavior
squads obs sync should resolve the JSONL path relative to the hq root (the git root that contains .agents/), not the current working directory. It should work identically whether invoked from hq, a worktree, or any subdirectory.
source:data
Reactions are currently unavailable
Metadata
Metadata
Assignees
Labels
bugSomething isn't workingSomething isn't workingpriority:P1Critical priorityCritical prioritysquad:cliCLI squadCLI squadtype:codeCode qualityCode quality