Omni is the AI engineer that takes your agents from a laptop to the cloud. Today, your best AI workflows still live in Claude on your machine - stopping when the lid closes, running for no one but you. Describe what you want, or bring what you've built, and Omni wires the tools and skills, tests on mock data, and hands you a running cloud agent: scheduled, long-running, shareable with your team. It keeps agents healthy too - improves system prompts, compares models, debugs and fixes failed runs.
@ran_sheinberg The mock-data-to-cloud path is the part that stands out here. For an agent that can repair failed runs, what is the default approval boundary: can Omni change prompts, models, schedules, and tool permissions autonomously, or are higher-risk changes proposed with a diff and rollback point first? That audit trail seems especially important when the same agent can reach production systems.
the "stopping when the lid closes" line hit home - I was literally in a forum thread yesterday about caffeinate vs actual lid-close sleep on macOS for this exact reason, so this feels like the real fix past that hack. curious about the "compares models to pick the right one for the task" part specifically - once an agent is running fine on a given model, what triggers a re-comparison? is it every scheduled run, only on failure, or only when I ask, and if it decides to switch mid-flight does that need my approval or does it just swap silently
@galdayan check it out! Omni is able to do all the magic in the platform, and as a next step, I can simply set this to be a scheduled task, and tell it to select the best model for the job every time it runs!
@ran_sheinberg nice, that table is basically the answer to "does it decide silently" - looks like it surfaces the comparison rather than just picking one and moving on. one thing I still can't tell from the screenshot: does it re-run this three-model bakeoff every single time the scheduled task fires, or does it cache the winner and only re-bake if something changes? asking because re-comparing on every run is the more trustworthy default but also the more expensive one
@galdayan yeah that's what I meant that for now I just did a manual test - and as a next step I can schedule a task that would, for example, do the bake-off once a week, and then configure the winner as the default model for the agent
@ran_sheinberg makes sense, weekly is a reasonable cadence to amortize the cost. when the winner does flip mid-week, is that visible anywhere, like a log entry or notification saying "default model changed from X to Y," or does the agent just quietly start behaving slightly differently and you'd only notice by checking the config
Congrats on the launch! BTW, when a target site changes its layout, does the Bot auto-detect the break and self-heal, or does it silently start returning bad data until you notice?
@zeeshan_aslam2 so true, it really helps many customers first design the agent's behavior, and only then hook it up to critical systems. I really think it's one of those features that show the breadth and depth of the platform!
The “stop babysitting your agents” part got me 😅 I’ve had way too many workflows that work perfectly until I close my laptop or something quietly breaks overnight. Really like the idea of taking care of the deployment and the messy debugging afterward. Congrats on the launch!
Report
Really like how this takes away a lot of the annoying setup around running agents in the cloud. The auto-debugging part is especially interesting — feels like something that could save a ton of time. Curious to see how it works in practice!
Fish Audio
@ran_sheinberg The mock-data-to-cloud path is the part that stands out here. For an agent that can repair failed runs, what is the default approval boundary: can Omni change prompts, models, schedules, and tool permissions autonomously, or are higher-risk changes proposed with a diff and rollback point first? That audit trail seems especially important when the same agent can reach production systems.
Dial
the "stopping when the lid closes" line hit home - I was literally in a forum thread yesterday about caffeinate vs actual lid-close sleep on macOS for this exact reason, so this feels like the real fix past that hack. curious about the "compares models to pick the right one for the task" part specifically - once an agent is running fine on a given model, what triggers a re-comparison? is it every scheduled run, only on failure, or only when I ask, and if it decides to switch mid-flight does that need my approval or does it just swap silently
xpander.ai
@galdayan check it out! Omni is able to do all the magic in the platform, and as a next step, I can simply set this to be a scheduled task, and tell it to select the best model for the job every time it runs!
Dial
@ran_sheinberg nice, that table is basically the answer to "does it decide silently" - looks like it surfaces the comparison rather than just picking one and moving on. one thing I still can't tell from the screenshot: does it re-run this three-model bakeoff every single time the scheduled task fires, or does it cache the winner and only re-bake if something changes? asking because re-comparing on every run is the more trustworthy default but also the more expensive one
xpander.ai
@galdayan yeah that's what I meant that for now I just did a manual test - and as a next step I can schedule a task that would, for example, do the bake-off once a week, and then configure the winner as the default model for the agent
Dial
@ran_sheinberg makes sense, weekly is a reasonable cadence to amortize the cost. when the winner does flip mid-week, is that visible anywhere, like a log entry or notification saying "default model changed from X to Y," or does the agent just quietly start behaving slightly differently and you'd only notice by checking the config
Triforce Todos
Congrats on the launch!
BTW, when a target site changes its layout, does the Bot auto-detect the break and self-heal, or does it silently start returning bad data until you notice?
xpander.ai
@abod_rehman Omni is a real autonomous agent - it'll adjust to changes in target sites!
The mock data testing before putting an agent in the cloud is a really useful touch. It could save a lot of debugging time later.
xpander.ai
@zeeshan_aslam2 so true, it really helps many customers first design the agent's behavior, and only then hook it up to critical systems. I really think it's one of those features that show the breadth and depth of the platform!
Expertise AI
The “stop babysitting your agents” part got me 😅 I’ve had way too many workflows that work perfectly until I close my laptop or something quietly breaks overnight. Really like the idea of taking care of the deployment and the messy debugging afterward. Congrats on the launch!
Really like how this takes away a lot of the annoying setup around running agents in the cloud. The auto-debugging part is especially interesting — feels like something that could save a ton of time.
Curious to see how it works in practice!