Cross-post inspired by Garry's List: The New Octopus. Not affiliated with Garry's List.
Every platform layer that refuses open APIs taxes the next generation of software — including multi-agent systems.
What builders feel in production
- Dashboard lock-in — agents re-export CSVs instead of calling tools.
- Token vanity — "we burned 40 tool calls" is not an outcome.
-
Secret sprawl — long-lived keys in
.envinstead of short-lived runtime tokens.
Patterns that work
- Memory before gen — reuse prior answers before another full model burn.
- MCP / tool interfaces — ask systems you already pay for, don't stitch 12 screenshots.
- Outcome KPIs — jobs booked, tickets closed, dollars captured — never invent revenue.
What I ship (honest)
- Free After-Hours Leak Score for HVAC/plumbing shops: https://igorganapolsky.com/after-hours-leak-score.html?utm_source=garryslist&utm_medium=community&utm_campaign=ahls_free
- Optional $149 written After-Hours Leak Audit: checkout is not captured revenue until a live non-owner Stripe charge succeeds.
- Local multi-agent fleet control on Mac — governed where irreversible.
Ask
If you run agents in production: measure reuse rate and business outcomes, not token volume. Comments welcome.
— Igor Ganapolsky
AI Operations Agency
Top comments (0)