How I AIHow I run autonomous coding agents from my phone with OpenAI Symphony + Linear
At a glance
WHAT IT’S REALLY ABOUT
Running cloud coding agents via Symphony, Linear, and mobile management workflows
- Alessio explains the shift from being an “agent prompter” to an “agent manager,” using Linear as the state machine and source of truth for long-running autonomous coding work.
- He demos a Symphony+Linear workflow that turns issues into Codex workpads, produces PRs, routes tasks through human review/rework, and can be managed from anywhere (including a phone).
- They discuss why orchestration is less the hard part than tool support and context-shaping—e.g., adding capabilities like visual testing/screenshot diffs and tracking token usage per task to diagnose friction.
- Alessio highlights maintenance pitfalls of “skills” and markdown instruction files, arguing for periodic purges and tight, minimal instructions to prevent compounding agent confusion.
- A second demo shows Codex doing business-value automation for a trading card shop: extracting PSA certificate numbers, hunting underpriced high-end cards on eBay in controlled batches, and envisioning real-time trade-show pricing assistance.
IDEAS WORTH REMEMBERING
5 ideasTreat yourself as an agent manager, not a prompt typist.
Alessio’s core change is moving from direct back-and-forth prompting to managing a queue of issues and interventions, letting the agent execute plans and only stepping in at review/rework points.
Use Linear (or an equivalent) as the source-of-truth state machine.
By encoding status transitions (To Do → In Progress → Human Review → Rework → Done) in Linear, you get a durable workflow that’s easy to operate on desktop or mobile and keeps work organized across many runs.
Cloud-hosted runtimes make autonomous work actually usable day-to-day.
Moving agents off local machines to a VPS enables persistent execution and multi-channel control (phone, web, shell), removing the friction of babysitting hardware and sessions.
The real value is task history + context shaping, not “new capability.”
Symphony doesn’t magically add intelligence beyond the coding agent; it structures context (spec, plan, acceptance criteria, rework checklist, PR discussion) so you can understand failures and iterate systematically.
Track token spend per task to estimate cost and uncover bottlenecks.
A token ledger lets you see which tasks explode in cost (e.g., deployability refactors) and guides improvements in specs, checks, and tooling to reduce wasted cycles.
WORDS WORTH SAVING
5 quotesWhat really clicked for me was, like, starting to move away from being a agent prompter to kinda be a agent manager.
— Alessio Fanelli
If you expect something... You should start to have, at some point, some idea of, like, how many tokens you think this will take. You know, is this like a 10 million token task? Is this like 100 million token task? And if the reality is very far away from your expectations, there's probably something in the tooling layer that you can do to improve.
— Alessio Fanelli
Everything is like, how do you shape the context, you know? Like Symphony is just a way to shape the context. It's not, it's not giving you any new capability that you wouldn't have by using the coding agents directly. It's just helping you wield it.
— Alessio Fanelli
This is my favorite positive outcome of AI, which is small business creation. Just the ability to, like, intersect the human world in a way that has been historically very inefficient has been a quality of life improvement for me.
— Claire Vo
You can actually use AI to save clock time for real people by doing these things autonomously.
— Alessio Fanelli
High quality AI-generated summary created from speaker-labeled transcript.
