pre.dev remembers what you tell it once, and keeps it where it belongs told it 12 things in one chat, then asked in new chats: - same project: used all 12 - other project: used the 6 meant for every project, left out the 6 project-only ones - fresh account: 1 of 12 (a guess)

Of the five coding agent memories we compared, only pre.dev's does all six things we looked for. Tell it once. We told it 12 things in one chat. In a new chat it used all 12. In another project it used the 6 meant for every project and kept the 6 project-only ones out. It learns as you work. On 30 chat turns we labeled, it saved 12 of 14 lasting preferences and 0 of 16 things it should not keep, including secrets and instructions planted in a web page or a file. One memory for you, each project and your team, on the web and in your terminal. Other agents can read it and add to it over MCP. Switching is easy: on day one it brings in your repo's rule files (CLAUDE.md, AGENTS.md, Cursor rules and more), Claude Code's notes, and what ChatGPT, Claude or Gemini know about you. Comparison from each company's public docs, read October 23, 2026.

Muse can't shop Amazon anymore. Claude Code can: 1.8x faster and 1.6x cheaper with the pre.dev MCP than with Claude in Chrome. Amazon blocked Muse, a cloud agent that shops from a virtual machine in Meta's cloud. A local agent drives your own Chrome, signed in as you. The day after Prime Day, we had Claude Code find the best deal still live on Amazon, then check Best Buy, Walmart and Target. 4 shopping tasks, 3 runs each, Claude Sonnet 5.5 on both sides: - faster on all 4 tasks, first in 12 of 12 head-to-head runs - 12 of 12 runs complete, all 34 cited prices checked out on the live page - no store showed it a bot check - it stopped before the cart: the buy button stays yours What it found: Target had the Kindle Colorsoft $100 under Amazon. Amazon had a Shark robot vacuum $500 under Best Buy. Works with any coding agent on your laptop: npx -y @predotdev/mcp setup No coding agent? The pre.dev CLI does it too: type /chrome.

Same agent. Same model. Same Chrome. 2x faster and 1.8x cheaper. We raced Claude Code with Claude in Chrome against Claude Code with the pre.dev MCP: 8 everyday browser tasks, 3 runs each, Claude Sonnet 5.5 on both sides. - Faster on all 8 tasks, from 1.3x to 2.8x - First in 22 of 24 head-to-head runs - 12 minutes of browser work became 6 - 1.8x lower API cost per task, as Claude Code reports it - every answer right on both sides Most of the gap is outside the model: across all 24 runs, 349 seconds of tool and startup time vs 95. The pre.dev MCP hands the agent the page as short text with a ref on every button and field, so it takes fewer, smaller steps. Open source and built with pre.dev. One command sets it up in Claude Code, Codex, Cursor, Hermes, Pi and 20+ other agents: npx -y @predotdev/mcp setup

Every predev project now ships with AI, payments and auth built in. Open the Integrations panel on any project and you'll find them under Built-in. Already on, already wired, no setup. Here's what each one gives you 👇 AI Just ask the agent for an AI feature. A chatbot, smart search, recommendations, summaries, whatever your product needs. It runs on your predev key (PREDEV_API_KEY), so there's no model provider account to set up and no keys to juggle. In Bellavino, our demo restaurant menu, this is how we built an AI sommelier that pairs wines with whatever guests are ordering. Payments Every project starts in test mode: test cards only, nothing gets charged. Build your checkout, try every flow, break things safely. When you're ready for real money, flip to Live in Integrations > Built-in. One switch, same code. Auth Each project gets its own dedicated Clerk app. Sign-up, sign-in and sessions work from the first build. Once you claim it, it's yours. Open Clerk straight from the dashboard to manage sign-in methods, branding and users, with your keys right there to copy. Working locally? In the predev CLI, the keys for all three land in your project's .env automatically. Clone, run, done. Why this matters The first screen is never the hard part. The hard part is everything that makes an app real: users who can log in, a way to get paid, features that feel smart. That's usually where weekends get spent on API keys, webhooks and env vars. predev plans the architecture first, so these aren't bolted on later. The agent builds around them from the start and verifies they work. You go from idea to a product people can sign into and pay for, not just a demo. And the Built-in tab is just the start: Connections, Agent Skills, MCP Servers and your own API keys all live in the same panel. Build something people can engage with: @predotdev

Make your website agent-friendly, automatically. Apps built with predev now expose their actions through WebMCP. Whenever the agent builds or changes a form or action in your web app, it registers it as a WebMCP tool that runs the exact same handler as the button. AI agents in the browser can use your app directly, and normal clicks keep working just like before. The predev agent benefits too. Its own browser checks now call those tools, then still confirm the result on screen and again after a reload. They also finish sooner, because the first page visit already lists every control on the page. Your app works for humans and for agents, without building anything twice.

For AI labs doing post-training: runnable RL environments built from 9,000+ private production codebases. Hard, long-horizon tasks most models can't solve yet, with continuous rewards to hill-climb on. → Request samples + the metadata sheet

Native auth and payments, now in predev Earlier this week we gave you native AI tools to turn your ideas into products people actually want to use. Today you can capture that value. Authentication and payments are now built in, powered by @clerkdev and @stripe. Sign-ups, sessions, checkout, subscriptions. All of it works out of the box. As with our AI tools, predev orchestrates the vendor integration under the hood. No env files, no API keys, no permissions to reason about. You don't touch the plumbing, because there isn't any to touch. That leaves you free to do the part that actually matters: crafting AI workflows worth paying for, and building a relationship with customers who keep coming back. Tell us what you're building, and what integrations you want to see next.

New in @predotdev: native AI for your apps Adding AI to an app used to be tedious. Provider accounts, API keys, wiring up each integration, and making sure none of those keys ever leak. Starting today, you can skip all of that. Every model in predev now works directly inside the apps you build. No keys, no extra accounts, no secrets in your frontend. Just multimodal AI, ready from day one. A few ideas: - An AI calorie tracker that reads a photo of your plate - An interior redesign tool that reimagines a room from one picture - A recipe generator that works with whatever's in your fridge Or anything else you can dream up. Take it for a spin and build AI experiences your users will love.

Most coding agents give you one model for the whole run and hope it's the right call. predev lets you pick per phase. /model to set chat, research, coding, and acceptance independently. Cheap and fast where it doesn't matter, heavyweight where it does. Settings stick with the project.