Rhys

12.8K posts

Rhys banner
Rhys

Rhys

@RhysSullivan

building https://t.co/gIFOwRUrLU to connect any agent to every tool, API, and service your team uses | yc 26

San Francisco, CA Katılım Kasım 2007
1.4K Takip Edilen58.3K Takipçiler
Sabitlenmiş Tweet
Rhys
Rhys@RhysSullivan·
Executor is joining the YC S26 batch! We're building an open source MCP gateway to connect any agent to any service Your team is constantly spinning up new agents, trying out new tools, wrangling multiple accounts. You need one place to configure everything once, and use them anywhere. Executor gives you the ability to connect your agents to thousands of tools in a way that keeps you in control. Giving agents access to production services and data should be easy and predictable Since launching the beta we've: - Shipped a self-hostable Docker version - Shipped a desktop app - Shipped setup by chatting with your agent - Shipped multi-account support - Hit 2,000 GitHub stars - Built a product loved by thousands of users Truly appreciate all of the early support on it, has been incredible seeing all the ways people use it There's so much to build here. The past month has been laying the foundation. Now that that's in place, next up is custom tools, generative UI, and workflows. Setting it up is as easy as asking your agent "help use executor.sh". Incredibly excited about what's next, let me know all your feedback!
Rhys tweet media
English
272
68
1.6K
204.5K
Rhys
Rhys@RhysSullivan·
It’s absurd how good OpenAI’s communication game is
Tibo@thsottiaux

Hello beautiful people! We have reset usage limits across Codex and ChatGPT Work. And another one will come later in the day. Rejoice. Now that I have your attention, a quick update on ChatGPT Work, Codex and all the updates we shared yesterday. We’ve spent the last 24 hours reading feedback, looking at usage patterns, and talking with many of you. The short version is that there is a *lot* of excitement for GPT 5.6 Sol, ChatGPT Work on mobile & web, but also that we didn't get everything quite right. - We made it too easy to use the highest-compute settings without making the impact on usage limits sufficiently clear. - We reorganized the desktop app in one bold move, making familiar things like chats and projects harder to find. - Our launch framing was focused on ChatGPT Work and to some of our Codex fans it made it feel like Codex was going away over time. Absolutely not our intention, we love Codex and it is here to stay. - And we introduced regressions for some existing multi-agent workflows, alongside a collection of rough edges in plugins and other parts of the experience. We’re landing a first set of improvements today. We’re resetting usage twice so people can keep experimenting, changing defaults and the model picker so they don’t push people toward unnecessarily expensive settings, fixing several plugin submission issues, improving how we represent Codex in the product, and cleaning up some of the most immediate desktop problems. A larger set of improvements will land next week. We’re bringing chats and projects back into the sidebar in a more familiar and customizable way, making usage and reset timing much more visible, clarifying when to use ChatGPT Work and when to use Codex, and addressing the many other smaller pieces of great feedback we've had. The ambition behind this launch hasn’t changed. We think bringing ChatGPT and Codex together into a workspace where people and agents can collaborate is a very important step forward. But an ambitious direction doesn’t excuse avoidable confusion or regressions in the first version. Please keep the feedback coming. We’re moving quickly, and you should see the experience already get better with a few updates today; and substantially better again next week.

English
11
0
179
5.5K
Rhys
Rhys@RhysSullivan·
@samgoodwin89 i have opus tokens to burn if i can help contribute to generating more good specs lmk
English
0
0
2
335
Rhys
Rhys@RhysSullivan·
what do katy perry and justin trudeau talk about
English
16
0
17
2.5K
Rhys
Rhys@RhysSullivan·
LLMs have raised our ambitions so much we've gone from fighting about javascript frameworks to javascript runtimes
English
8
3
137
3.7K
Rhys
Rhys@RhysSullivan·
@zaherg fix is live now
English
0
0
1
51
Zaher 🦋@zaher.dev
hey @RhysSullivan , it seems the latest version of the selfhosted it broken (at least the docker image is) Cannot find module '@cloudflare/worker-bundler' from '/app/apps/host-selfhost/dist-server/serve.js' missing sourcemaps for /app/apps/host-selfhost/dist-server/serve.js
English
1
0
2
822
Rhys
Rhys@RhysSullivan·
@nathanv246 That’s a bad one I need to rewrite it manually
English
0
0
0
333
Rhys
Rhys@RhysSullivan·
i think i've come around to AGENTS.md being one of the most important files your project can have and yet none of the major harnesses treat it like that
English
22
2
171
12.9K
Rhys
Rhys@RhysSullivan·
I actually don't have any personal criticisms of React
English
13
0
111
7.1K
Rhys
Rhys@RhysSullivan·
random benchmark idea is 'lazy bench' which tests if a model can realize it needs to do an action in a more efficient way example: told codex to use computer use to scrape some data, it should realize it can write a script rather than manually fetching every page
English
11
2
89
5.7K
Rhys
Rhys@RhysSullivan·
@coleywoleyyy @steipete it's not really about the content, more that like "i have no idea whats in my agents.md as it changes" and it's especially hard to edit in claude code / codex
English
1
0
14
687
Rhys
Rhys@RhysSullivan·
@BenceRedmond agreed, just discovered a bunch of cruft in mine as its built up
English
1
0
13
741
Rhys
Rhys@RhysSullivan·
@davidobot_ congrats! we met waiting for the interviews right? love to see it
English
1
0
13
2.8K
David Khachaturov
David Khachaturov@davidobot_·
turns out yc does still take people with a phd
David Khachaturov tweet media
English
29
2
173
14.7K
Rhys
Rhys@RhysSullivan·
the new codex computer use is insane wtf i didn't think it could get better
English
26
2
324
20.2K
Rhys
Rhys@RhysSullivan·
@leylndd point claude at github.com/UsefulSoftware… and ask it to adopt the e2e testing approach for the mintlify repo and cli video of what it looks like: x.com/RhysSullivan/s… lets you start to go headless with it reproducing them, is pretty nice
Rhys@RhysSullivan

Clip from @NextTokenShow showing Dillon and Sunil my testing setup for Executor! The goal is 'programmatic computer use' - the agent has the same tools you use to test your app and can call it through a cli or tests Is one of the first ways I've gotten good tests from LLMs

English
2
0
5
177
leyland
leyland@leylndd·
@RhysSullivan I have it use the chrome instance on my laptop (Claude-in-chrome extension)
English
1
0
2
128
leyland
leyland@leylndd·
Sharing a prompt from today that one-shot a customer issue: > Get up to speed on this thread: {slack url} > First, replicate this issue by finding a relevant deployment with the MongoDB MCP, running yarn dev on tmux pane 2 and serving {subdomain}.localhost:3000 using chrome > Then fix the issue in code until you can validate that the issue is fixed on chrome at localhost:3000 > Once you are done, create a PR and include a Test Plan that contains prompt so that anyone's agent can automatically test this PR and send this in the #eng slack channel
English
2
1
18
1.5K
Rhys
Rhys@RhysSullivan·
@george_veng gets people using the plan but you can just not active it
English
0
0
2
85
Rhys
Rhys@RhysSullivan·
@fire yeah
English
0
0
6
480