PM at @Cloudflare. @Stanford alum.
San Francisco, CA
Joined October 2010
- Tweets166
- Following266
- Followers1.1K
- Likes1.1K
Phillip Jones retweeted
the flywheel in motion making Cloudflare OS better each day is amazing right now. see note from principal engineer below.
1) move more workloads to Cloudflare OS
2) send feedback on what needs to improve
3) product improves to the point that it "honestly changed our lives after just a few hours of work"
4) repeat
Phillip Jones retweeted
This isn't your typical acquisition blog post. I'm really excited not just that @rough__sea, @piscisaureus, and friends are joining, but also what they plan to work on: Making workerd a first-class, self-hostable open source runtime. Read for more:
blog.cloudflare.com/deno-joi…
Phillip Jones retweeted
excited to announce that @Cloudflare Artifacts is now in open beta!
with Artifacts, you can give every application and agent its own repo that you can manage programmatically
plus you can use it to store and deploy your Workers code (and ofc it integrates with Workers Previews)
Phillip Jones retweeted
intelligent routing to optimize your model choices and token spend, now on @Cloudflare ai gateway. the control plane for your ai usage. blog.cloudflare.com/auto-rou…
Phillip Jones retweeted
production errors should not sit in a dashboard waiting for someone to copy a stack trace into a prompt 😿
today we’re introducing Workers Issues -- built-in error monitoring that can send production failures straight to your agent ✨
blog.cloudflare.com/real-tim…
Phillip Jones retweeted
biggest containers update since launch just dropped. and it's all about agents sandboxes
new scheduling policy, new runtime, 648ms median startup, runtime image selection, filesystem snapshots (!!), sandbox sdk 1.0
there's a lot in this one 1/ 🧵
Phillip Jones retweeted
Introducing Worker Previews: give your agent an entire production-like environment for every change it makes
Phillip Jones retweeted
Lots of what we ship for @Cloudflare Birthday Week starts with someone asking for it here. Less than a month out. Ask.
Phillip Jones retweeted
This week I "only" produced a 13,000-line PR...
Pretty excited about this feature though! I will now be able to vibe code my ideal code review workflow as a Cloudflare OS gadget.
Specifically, for reviewing PRs sent to me from others. PR descriptions are inconsistent and inevitably don't cover the points I care about, so I want an agent to look first and generate a report tailored for me, so once I open the PR I can get my bearings quickly. Then I want to be able to ask the agent further questions as I read, and maybe even prompt it to make changes, which should just be pushed directly back to the branch. (Sorry, "suggestions" are weak, I just want to push code to your branch, deal with it.)
I know there are many AI-assisted code review tools out there that do similar things, but none of them do things exactly the way I want, nor can I immediately add new features to them as I think of them. That's why I want to be able to vibe code my own -- but safely. This is exactly what Cloudflare OS and personal software is all about...
github.com/cloudflare/cloudf…
Phillip Jones retweeted
who wants to try out new granular permissions for @Cloudflare Workers?
would allow you to give a user/agent access to a specific Worker, without granting access to every Worker in your account
DM me if you're interested
Phillip Jones retweeted
A fun experiment with Code Mode and Flue to make generative art. Instead of inventing a tool for every possible shape, the model can write JavaScript and run it in an isolated worker.
repo: github.com/paperwing-dev/exp…
Phillip Jones retweeted
glm 5.3 flash from @Zai_org (fka ox alpha) is up on @CloudflareDev workers ai 🐮
‣ low cost, high intelligence
‣ 1M context window
‣ first multimodal model from the GLM family
‣ also accessible via CF AI Gateway and @OpenRouter
developers.cloudflare.com/ch…
You can vibe code anything.
But no one who needs access to sensitive data can safely share and collaborate on what they've built.
You can put auth in front, but how do you make sure everyone has the right access to the resources powering your app?
Cloudflare OS solves this:
Here's how it works:
• Agents and the apps they build start off completely sandboxed with access to nothing.
• Resources are added as narrowly scoped capabilities the agent and apps can use.
• Every observation of a resource is recorded.
• When you share with someone, the platform verifies whether they can access the specific resources observed, based on their own permissions.
• This keeps the policies on your systems of record intact and no one needs to worry about if they are sharing something they shouldn't be.
Most agents can build apps. Cloudflare OS can actually use the apps it builds.
This means if your team builds a tool to do a job, an agent can use the tool as you would—on a schedule or upon a triggering event—even if you're not there to work with it.
How: In Cloudflare OS, any UI you build can only communicate with its server over Cap'n Web RPC.
This means, by definition, every app comes with a clean API. When agents do work, they can have access to your app's full API.
os.cloudflare.app/
Phillip Jones retweeted
CloudflareOS is everything that you wish Google Workspace could do well, but can't
just went from data question to spreadsheet to pricing memo with a real-time editor in one browser tab
then sent someone on my team a link to all of it (including original prompt) — we can both keep prompting and make direct edits
all of this is possible to get done with codex/claude via computer use and integrations — but i am telling you it is night and day faster this way, and I don't worry about security/permissions at all because cfos makes the footguns impossible, in a way nothing else can
what starts out as a toy...
os.cloudflare.app/