Jeremy Pollock

In the age of AI, I’m not sure integration is much of a moat.

Any acquisition has a process, both pre and post, with transfer of Git repo ownership often being a "post acquisition" task. This has now been completed and soon we will be updating our repo to include code that runs the current version of app and website. Why the delay, beyond "acquisition"? We have been following our normal and robust protocols for migrating operational/production services with no interruption to our users. @wpengine is committed to keeping @wpackagist open, free and for the community. And we will seek to do right by the great work done before us, from @outlandish and others.

Roots Launches WP Composer as Open Source Alternative to WPackagist therepository.email/roots-launches…

Any acquisition has a process, both pre and post, with transfer of Git repo ownership often being a "post acquisition" task. This has now been completed and soon we will be updating our repo to include code that runs the current version of app and website. Why the delay, beyond "acquisition"? We have been following our normal and robust protocol for migrating operational/production services with no interruption of service. @wpengine is committed to keeping @wpackagist open, free and for the community. And we will seek to do right by the great work done before us, from @outlandish and others.

Proof I started working on our own app to replace WPackagist is attached > that WPackagist is open This is no longer clear. Their repository no longer reflects their app and website. Composer allows messages to be pushed directly to every developer on install/update: x.com/retlehs/status… That behavior isn’t clearly reflected in their repo: x.com/jonathan_dejon… Open source repo ≠ transparent system. WP Composer makes everything public, including infrastructure and build process.

Clarifying some things I’ve seen about WP Composer/Roots this week: – We started working on a WPackagist replacement last August, long before any recent attention – RTs/posts by dot org are unrelated to our motivations, but we do appreciate the extra visibility – Roots has been an independent open source org in the WordPress ecosystem since 2011, with one goal: improve the WP developer experience – We’ve never been an agency or owned by a hosting company, just a team and community focused on open source – I do sell one product, Radicle, to help fund that work, along with past products like screencasts and the Sage book – WP dot com has been a sponsor since 2021, and others, including Pantheon, have supported Roots over the years, with no influence on our roadmap – WP Engine hasn’t been involved with Roots, no sponsorship or collaboration to date, including support and documentation for Sage 11 – When critical ecosystem infrastructure ends up controlled by a private equity-owned company, especially when that platform still has gaps in Composer support, we think the community deserves an open alternative

@LocalWP reached 10.0.0 today! localwp.com/releases/10.0.0 This milestone release is centered around making #WordPress development workflows more resilient and portable. We’ve taken one of our most popular add-ons—Cloud Backups—and rebuilt it as a core, native experience. Say goodbye to the extra steps. Cloud Backups are no longer an optional add-on that requires a separate installation nor a Local Hub account. Starting in v10.0, Cloud Backups are built directly into the core Local application, offering a faster, more reliable way to protect your work and move between machines.

@aaronware @wpengine @LocalWP We are planning on adding: "WPackagist is now maintained by WP Engine." in the CLI. That is all.

What is the plan for @WPEngine acquisition of wpackagist? Historically WPEngine's purchases have been freemium to premium and generate $$$. @LocalWP came w/ Flywheel is well supported. Private Equity typically want profits from assets. First step is an ad in the CLI now

I lead the product team that owns Local. Yes, there are plenty of things that we could do. But, also, we've come to learn that Local does the things it does pretty well and satisfies the needs of the majority. I'd love to push more on adding more features. But to do so with adding more real value. Releasing features for the sake of indicating investment and importance seems counter-productive. Open to ideas on where we could take Local! Happy to chat or DM as well!

@lelandf @alexmansfield @bgardner @wpengine I think @WPLocal is a great, its stable and WP Engine maintain it, it also hasn't had a meaningful feature in years. Last bugfix was Oct 2025 since it doesn't make $. Paid tiers while hyperbolic isn't entirely unrealistic. Private packagists are easy to implement.

It’s been 0⃣ days since our team at @wpengine made an acquisition. wpengine.com/blog/wp-engine…

I lead the WP Engine product group that drove the acquisition and that will handle the maintenance of WPackagist. I was in direct conversations with the PE leaders as well. Monetization of WPackagist never came up. Could there ever be an analog to packagist.com? Sure. But there's no plans to do so and we'd have to have some pretty good data to indicate that it is worth doing so. To be clear: the decision to spend $$ never included a dependency on monetization of WPackagist. We going to maintain and support, proudly. And "It’s more valuable in goodwill to simply keep it free."

@aaronware @alexmansfield @bgardner @wpengine Do you think this is a realistic scenario? I am thinking of LocalWP which is still free today. Nothing is truly altruistic when you think about it, but I don’t see the $/mo WPackagist tiers happening. It’s more valuable in goodwill to simply keep it free.

@SecWar, Make America Claude Again! #MakeAmericaClaudeAgain #Anthropic #ClaudeCode

@JiveDig @aBearded_Ginger @beyondcode @LocalWP And if you try out the Laravel add-on (jpollock.github.io/local-addon-la…), happy to take feedback!

@jeremypollock @aBearded_Ginger @beyondcode @LocalWP WHOA! Laravel in LocalWP looks great! My issue: When I have Herd and LocalWP running at the same time, loading a laravel site (.test) seems to work well, but loading local (.local) shows Herd's 404 screen.

Has anyone gotten @beyondcode Herd and @LocalWP to work at the same time? They work one at a time, but I'd love them to both work simultaneously. Seems like a port thing.

This might help, i.e. switching the router mode to localhost. This means that you'll have URLs like "http://localhost:32424/" instead of "https://nicesite.local". An upside though, especially when working with that experimental CLI in Claude, is that you don't get the OS popup for modifying host file when creating sites.

Any details that you can share around what you're seeing? I'd be happy to try to help, on the @LocalWP side of things. Since you mention Claude Code... I've been playing with a CLI for Local: github.com/jpollock/local… It has been super useful for Claude Code work, e.g. interact with Local sites, create new sites, in the flow/chat/agent work. Local still has to be running though. github.com/jpollock/local… might be useful for you, for Laravel dev using Local.

@aBearded_Ginger @beyondcode @LocalWP Yep 🤦‍♂️, pre Claude Code it wasn't as big of a deal, but now I want things running in the background on both.

@jonschr @LocalWP @claygriffiths Happy to chat, @jonschr. I lead the product team that manages @LocalWP . Also... "finding another similar one..." seems to be the story of my #AI life these days.

.@LocalWP @claygriffiths I just vibe-coded an addon for Local that allows for searching our sites (I have hundreds). Wondered if 1) you might like to add this functionality to core, or 2) if you could point me toward how to enable updates so that I could let other ppl use it.

@akka_io_ @AnthropicAI I really appreciated doc.akka.io/sdk/ai-coding-… and the fact that I don't have to ask for tests.

@akka_io_ and @AnthropicAI's Claude Code are absolutely brilliant when used together. 🧠 Yes, in last month or two, a leap forward with Opus. So many have experienced the shift. 🦾📈 But I am still stunned at what I can now do with Claude when building robust backend systems and services. Akka seems to be a near-perfect framework. I have found few instances of round-and-round with the AI. Code that's produced appears architecturally sound, tested and ready to scale, right out of the box. 🥂 I shouldn't be surprised. Well, I'm not! But very happy to experience it! 😃

@BobWeir, fare thee well.

Thanks, Claude, for your enthusiasm.

@PGE_BayArea @PGE_BayArea no update for quite some time. And your website is showing projected resolution for ~3:45pm for 12/20/25. Which is yesterday.

Update: #SanFrancisco Outage

@LocalWP 's add-on architecture enables innovation. Of course, not all problems should be solved in the #1 local dev environment for #WordPress. But it is sure fun to try! 3 new add-ons that you might want to try out: - Always have "one click admin on" for new sites: jpollock.github.io/local-addon-on… - Spin up @laravelphp apps easily: jpollock.github.io/local-addon-la… - For WP Engine sites, see usage data locally: jpollock.github.io/local-addon-wp… See preview below. 👇

@JamesWard Vibe driving.

Oh woah, my car is gonna get MCP support!?!

@DerekAshauer @laravelphp @LocalWP jpollock.github.io/local-addon-la… First and very early release! Happy to take input and feedback.

@DerekAshauer @laravelphp @LocalWP Initial POC.

Anyone want to run a @laravelphp site in @LocalWP ? Not saying that we depart from #WordPress! But playing with an add-on to make it easy to spin-up other types of sites.