Launched this week
Managed agent as a service: launch a long-horizon AI agent in one click — Claude Code, Codex, Hermes, or OpenClaw — with full history, managed recovery, and access through WhatsApp, iMessage, Telegram, Slack, web, API developers, and CLI.
Congrats on the launch!
What does the developer API expose compared with the CLI? can teams programmatically create, pause, resume and manage agents?
AgentSky
@easton_carter Thanks! Our developer API is basically feature parity to CLI. We gave both options just for convenience, sometimes CLI is a bit more favorable for quick test/demo. For developers, they can use either our REST API or CLI to automate the AgentSky fleet management. Quick start https://agentsky.dev/docs
what runtime or channel are you most excited to add next? are you prioritizing integrations based on community requests or technical demand?
AgentSky
@colton_drake I think we're aligned with the trend toward open-weight frontier models, where we're seeing growing demand. Over time, we'd like to support as many stable harnesses and models as possible.
congrats! can developers choose different LLM models for the same harness? how quickly can you switch models without changing the agent configuration?
AgentSky
@carter_garcia Thanks!
Yes, for compatible ones.
Switching models is considered changing agent configuration. It takes about ~5 sec to deploy the new change.
If you had to recommend one harness for someone building their first long-running agent, which one would you suggest, and why?
AgentSky
@samra_habib1 I would suggest Hermes for maximum compatibility of open weight models and no vendor lock-in.
Can AgentSky automatically scale when multiple users start interacting with the same agent? how do you handle sudden spikes in agent sessions?
AgentSky
@dylan_russell
multiple users get their own sessions with same agent (same MDs, same skills, same capabilities)
Under the hood, we have an elastic sandbox infra which can handle new agent sandbox requests on demand.
Saying state restore is best effort and cannot prevent a race condition is rare on a launch day. You mentioned wanting idempotent agent replies in your own layer. Where do you think that line sits between the infra and the product on top, Darren?
AgentSky
@lucasjpols Appreciate the feedback! An analogy I would use is DB backup/restore, there would be no guarantee on a perfect restore with absolute no loss of rows. For most product user cases, I do feel this is sufficient, considering that agent crash should not be a high frequent event. We are still trying to put more common product concerns into our infra layer, while still let developers to keep their own part.
Congrats Darren! The channels part is what sells it for me. I correct my coding agent from the phone mid-run all the time, and that flow is usually held together with duct tape. Curious: when a WhatsApp message lands while the agent is mid-task, does it interrupt the run or queue until the current step finishes?
AgentSky
@artem_t Thank you! For now, we support 2 modes, please check out https://agentsky.dev/docs/api
you may request interrupt + another input message (interrupt first, then handle the new message)
you may just send another input message which will be queued
@darren_y_lu interrupt first is exactly what I need when correcting from the phone and queue covers the rest. thanks for the link, good luck with the rest of the week