正在加载视频...
视频加载失败
Thanks to Jev, you can now write workflows in plain English and run them instantly like code. I spent the day feeding it descriptions of tasks and it spit out workflows across hundreds of apps faster than I could read them. An agent could do this already, in 30... show more
26 条评论

Higher quality video - not sure what happened to the original

How does it actually work? Can we check out the repo?

Yes, I’ll work on getting the code ready to share! It starts with selecting relevant tools. It also evaluates dependencies, so any that require inputs not in the original prompt. Once that’s done, it evaluates step insertions, removals, and reordering.

you should see his videos, he wants get rid of things like that and that jev will be the brain. see this one

great use case @GilFeig been playing around with Jev and it's amazing at the real use case one can think of

I started off just to see if it could solve it, and it's way better than I expected.

it keeps surprising me indeed!

Impressive results.

yeah. i keep underestimating how long the second half takes

The ordering of the steps?

@shensi Holy shit this looks great !

Plain English works right up until someone writes an ambiguous sentence.

using plain English for workflows is a big win, but it won't handle all edge cases

True, doesn’t work for everything, because not everything’s a predetermined workflow. But for process automation and most work tasks, this destroys all the workflow and products and agent builders on the market

so cool

I was honestly shocked at how good it is

Free?

The bottleneck was never the agent, it was the API integration. If MERGE actually solves the routing layer, the workflow is just a dependency graph.

you can do the same with any model i don't see how it is any different than using luna

Everyone is reporting success, i report what did not work

This is important too!

Is it a Jev call at each step to determine what tool to call? Is there a place where we can read how it's working under the hood?

How many calls you need to this? Are you planning to put it to github pls?

Natural-language workflows are a great interface when the system keeps the plan visible and asks for confirmation at consequential steps. Speed plus inspectability is the sweet spot.

Any benchmark on how accurate it is in terms of generating the right workflow?

Plain English to executable workflow removes the setup overhead that blocks non-technical users. Have you hit edge cases where the generated workflow broke unexpectedly?
