Damn, there really is a way to operate a computer faster

The clip posted with this case (hosted by the collector’s media CDN); original post on X · 51s.

Built a Jev-powered computer-use layer for Codex, comparing it against the built-in version on a calendar-event task with fewer pauses.

The original post, translated

Damn, there really is a way to operate a computer faster than Codex's built-in computer use

I tried using Codex + Jev to build an enhanced version of computer use, which I call "Jev Use". It's faster and smoother than the built-in one, yet the token consumption is about the same

Below is a comparison video I made using "adding a Mac calendar event". With the same content, you can clearly see that the Jev version has almost no pauses throughout the whole process 😆

Show the original post in its source language ▾

卧槽,居然真有比Codex内置computer use更快的操作电脑的方式

我尝试用Codex+Jev打造了一个加强版computer use,我称之为「Jev Use」。比内置的更快更丝滑,token消耗却差不多

下面是我用「添加Mac日历事件」做了一个对比视频,同样的内容,明显可以看到Jev版本整体过程几乎无任何停顿😆

The post above is a machine translation from zh; the untranslated text is in the fold-out.

Quoted post

@Saccc_c307.4K views
source

强烈建议大家都亲自试试Jev,能让你的Codex操作速度提高10倍并省下大量token! 因为Jev非常适合用于判断型工作,能在毫秒内做出正确判断,而且token价格极低。因此非常适合以下几个场景: 1、computer use 将Jev用作操作判断层,指导模型快速操作你的电脑

Engagement when collected

Views145.4K
Likes819
Bookmarks1K
Reposts73
Replies57
Quotes5

Numbers are a snapshot taken from X when the case was added to the library (schema v1, collected 2026-09-19); they will not match today.

Where this case fits

Filed under browser & computer use. In the pattern Jev is built for, the model answers a bounded question per step — and ordinary code acts on the answer, because the answer is already a value rather than a paragraph. Other posts in the same family are on the browser & computer use page.

Related Jev cases

Keep browsing: all 1173 Jev cases · more from @Saccc_c · builders · what Jev is

Last updated: 2026-09-22 · sources & corrections · every card links to its author's original post