Comment on Show HN: Fleet – Python supervisor for running coding agents in parallelComments−xms171893moThe parallel-agent angle is interesting. In practice the hard part for me is deciding when agents should share state versus stay isolated. Does Fleet keep per-agent logs and failure reasons separate enough to compare runs after the fact?−sermakarevichOP3moI think it does, yes. Logs are written in:(base) ~ tree ~/.fleet/tasks/Users/makarevychsergii/.fleet/tasks├── fleet-0a5│ ├── artifacts│ │ ├── KNOWLEDGE.md│ │ └── PLAN_AND_STATUS.md│ ├── events.jsonl│ ├── log.jsonl│ ├── log.stderr│ └── task.json
Comments
The parallel-agent angle is interesting. In practice the hard part for me is deciding when agents should share state versus stay isolated. Does Fleet keep per-agent logs and failure reasons separate enough to compare runs after the fact?
I think it does, yes. Logs are written in:
(base) ~ tree ~/.fleet/tasks
/Users/makarevychsergii/.fleet/tasks
├── fleet-0a5
│ ├── artifacts
│ │ ├── KNOWLEDGE.md
│ │ └── PLAN_AND_STATUS.md
│ ├── events.jsonl
│ ├── log.jsonl
│ ├── log.stderr
│ └── task.json