AskFutures orchestrates coding agents with Linear tickets
Understand this story
AskFutures shared its approach to orchestrating coding agents with Linear tickets: tickets are used to record decisions rather than activity, and a parent ticket is split into subtickets with dependencies, assigned to multiple coding agents for parallel execution, and finally merged into the same parent PR. According to AskFutures, the full merge gate runs only once at the parent PR boundary, avoiding each subtask having to bear the most expensive validation cost repeatedly. The team also uses a small text file as a decision index; agents follow a progressive disclosure order: first read the index, then look up tickets, and finally look at the code and PR.
AI overview based on source reports · Updated 9 min ago
Coverage timeline
Follow the coverage to explore different perspectives.
- Hacker News AIIt's Time to Reinvent Software Tickets for the AI Era
AskFutures describes using Linear tickets to record decisions rather than activity, structure parent and child tickets with explicit dependencies to orchestrate parallel coding agents, and group child work into a single parent pull request so the full merge gate runs once. A small text file serves as a decision index, letting agents progressively disclose detail by reading the map, then relevant tickets, then code and PRs only if needed.
Activity for this story
Not enough continuous observations to show a trend yet.