agentho is now part of FlowMail.
The prototype is no longer being developed on its own. What it was trying to be — a place to build a workflow once, save it, and run it again later — ships today inside FlowMail.
What agentho was
It started as one hardcoded workflow: take my CV, take a job description, and tailor the first to the second. That worked well enough that the obvious next question was why the workflow had to be hardcoded at all — so it grew into a builder, where any sequence of steps could be assembled, saved and reloaded.
Then it hit a wall. Connecting to MCP servers means launching processes, and a sandboxed app destined for the App Store is not allowed to do that freely. There was a workaround. It was not a good one, and building a product on top of a workaround you already dislike is how you end up maintaining it for years.
Why it moved rather than continued
FlowMail turned out to be the better home for the same idea, for a reason that is almost funny in hindsight: it talks to remote MCP servers over HTTP. Nothing local is launched, so the sandbox limitation that stopped agentho simply is not in the way.
Everything else agentho was reaching for is there too. Workflows chain steps together — find something, label it, summarise it, classify it, draft a reply, call a tool on a server you run. The AI runs on your own Mac, with no API key to supply and nothing sent to an AI service. And a workflow can be triggered from Shortcuts, Siri or Spotlight, which is closer to “run this again later” than agentho ever got.
The one thing that did not survive the move is the CV workflow it began as. FlowMail is an email client; tailoring a CV is not what it is for.
The posts written while it was being built are still here, if you want the version with the dead ends left in: agentho – prototyping and agentho – 1.0.0, some UI improvements.
Photo by Rémy Penet on Unsplash