I’ve seen a lot of people dunking on @thdxr and @opencode, and I needed to say something. Frankly, I don’t think anyone understands how sophisticated these attacks are. These aren't script kiddies doing this after school. These are state actors, with real companies fueling the fire. One of the bigger companies behind distillation has 4 office locations worldwide, and there are a number of companies that are entirely fronts for distillation. You’ve probably seen their ads. Some have raised venture. I’ve personally seen messages claiming they bought over $5 million in inference for distillation. They’ve gone so far as to recruit people close to the model labs for better access, and the dollars flowing through the distillation ecosystem are in the 9 figures. These attacks offer a huge economic incentive. These aren't fly-by-night operations. At Vectoral we've see relays offering affiliate programs, net 30 invoicing for enterprises, and strict SLAs. Together, the top relays get tens of millions of visitors per month. Frankly, they are more sophisticated than most SAAS companies. The sad reality is that things likely only get worse from here. We are at war for global AI hegemony.

We urgently need more public traces of AI agents attacking and defending systems. Defenders can’t learn from what they can’t see. If you have traces and are being pressured to keep them private, my DMs are open. Let’s level the playing field and fight the asymmetry and lack of transparency in AI!

Serious question, in case anyone knows: How long does it take for Meta/Facebook to reply to a vulnerability report?

The most important technology problem of the next 5 years: Creating a broadly accepted standard for agents to identify themselves to service providers, so that providers can adjust the way they interface with clients (as compared to human-based traffic). In the interim (i.e., for the next 6 months), there will be a cat-and-mouse game that agents will play -- to circumvent detection and maintain their product's utility during this growth phase. However, this will only be a stopgap and it will not be the terminal state of the world.

Attackers only have to get it right once. Defenders have to get it right every time. At #HumanX, @nikesharora explains why that imbalance and vulnerabilities across enterprise infrastructure will drive a major IT overhaul in the years ahead.

How long does it take for Meta to reply to a vulnerability report?

You can finally close your laptop now and your agents will keep working. Codex cloud environments are here. Reusable environments mean less setup and faster starts, with your repo, dependencies, scripts, and settings already in place.

Today we are launching pachx. More than a year of work, and the answer to problems I've discussed in hundreds of conversations across my career. Attackers use agents now; engineers still carry the pager. pachx gives them evidence, not guesses.

Today we’re introducing Base Code. It’s an early preview of how we think software will be built in the future. It’s a product that encapsulates everything we’ve learnt from: - How our users are building software. - How we’re building internally, scaling to hundreds of millions of dollars in revenue while keeping our engineering team very small and focused. Here are some of the principles behind it, which align with how we at @Base44 think about the future of software engineering: Cloud: - Software will move past local desktop environments (where current tools are widely used) and move to the cloud. - Moving everything to the cloud is not easy. Setting up dev environments with databases, infra components, services, mock data, etc. is easier said than done. - Base Code first scans your code repo and sets up everything - every infra component (databases, Redis, etc.) - in the cloud. It runs nonstop until your preview environment is ready. - From an enterprise standpoint, it’s also the logical thing to do: a centralized, governed dev environment instead of handing out keys and secrets to all team members. - Once Base Code does that, EVERY team member can work in this environment. No more syncing local environments. Internally, this (cloud) is one of the main things that enabled us to move so fast. Collaboration: - Once everything is in the cloud, everybody can write software from anywhere (any browser, your phone, WhatsApp / iMessage coming soon). - You can easily see what everyone is working on, where they’re at, and how they’re prompting - and jump to their environment in one click. - We’ve built many great collaboration features from the ground up. Loops, automations, software factories: - A full, working cloud environment allows for many advanced capabilities we will unveil soon-think agents running in the browser and testing on every device and in any browser. - It also allows the use of automations to build software factories-e.g., agents reading support tickets, identifying bugs to fix or features to develop, implementing the changes, verifying them in the cloud, and potentially pushing them. And lastly, there’s a real advantage in being model agnostic. -------------- As always, we’re releasing it very early. It’s far from perfect-but we’re looking for early feedback so we can build it together with our great community and make this vision a reality. *We’re giving it away for free for 30 days*. Give Base Code a try. Connect any GitHub repo, get your live preview, and share it with your team. I’d love to hear what works and what doesn’t: app.base44.com/base-code