64 Labs
Static, Codex-managed publishing shifts content management from dashboards to files, rules, and deployment—and puts the traditional CMS on notice.
Two seemingly unrelated technology stories appeared one day apart this August.
On August 18, Check Point Research described a cybercrime operation that had turned nearly 2,000 compromised WordPress sites into infrastructure for malware delivery, surveillance, data theft, and ransomware. The researchers emphasized that poorly maintained installations were being abused; this was not evidence that every WordPress site was vulnerable. It was, however, another reminder that running a dynamic publishing platform comes with an ongoing maintenance surface. (Check Point Research)
On August 19, OpenAI published a very different announcement: Codex could now be built more directly into products and specialized workflows through its open agent harness, SDK, command-line tools, and app server. Codex was no longer being presented only as something that writes code inside a development environment. It was becoming infrastructure for operating entire processes. (OpenAI Developers)
Put those developments together and an interesting question emerges:
When an AI agent can create the content, update the site, follow its conventions, validate the result, and prepare it for deployment, how much of a traditional blogging platform is still necessary?
That may be a more consequential question than whether AI can write a decent article.
The dashboard was built for humans #
Traditional content-management systems solved a real problem.
Most people did not want to edit HTML, navigate a repository, manage templates, or run deployment commands. WordPress and similar tools placed a visual interface over all of that complexity. Substack went further by combining an editor with newsletters, subscriptions, audience discovery, analytics, and community tools.
The dashboard became the place where publishing happened.
But AI coding agents change the interface between a person and a website. Instead of learning where a platform placed its SEO field, image settings, category selector, or theme controls, the publisher can describe the desired result:
Add this article, use the existing post structure, preserve the site’s style, check the links, update the index, and verify that the site still builds.
In a static, Codex-managed setup, the article does not need to exist as a database record inside a remote admin panel. It can be a file stored with the website itself. The site’s existing code and conventions determine how that file becomes a page.
The CMS responsibilities do not disappear. They are redistributed.
Content lives in files. Structure lives in metadata and repository conventions. Presentation lives in templates. Revision history comes from version control. Validation comes from build checks. Deployment becomes the publish button. Codex acts as the interface joining those pieces together.
The result is not “no content management.” It is content management without a conventional CMS application.
This is already happening #
This approach is not yet evidence of a mass departure from WordPress or Substack. But it is no longer theoretical.
One public project, AIM-blog, documents a workflow in which Codex adds bilingual articles and related site content, runs a Hugo production build and diff checks, supports local review, and prepares the changes for a pull request. After approval, GitHub Actions builds and publishes the site. Its repository even includes project-specific Codex skills so the agent can follow the publication’s existing structure. (GitHub)
Another public Codex skill focuses specifically on publishing quality. It checks Markdown or MDX posts for frontmatter, source links, internal links, image alt text, schema readiness, metadata, heading structure, and other pre-publication requirements. (GitHub)
Developers discussing static-site migrations on Hacker News have described comparable systems. One reported using coding agents with Hugo to manage tagging, translations, tone checks, SEO, related content, and deployment. Another described retiring WordPress after Codex built a static replacement where checked-in Markdown becomes a site served by Nginx. These are individual experiences rather than adoption statistics, but they show that the model is already workable outside a controlled demo. (Hacker News)
The important shift is not that AI generated some Markdown.
It is that the agent understood the publication as a system.
What is actually at risk? #
Traditional platforms are not about to disappear. WordPress remains enormous: W3Techs reported on August 26, 2026 that WordPress was used by 40.7 percent of all measured websites and held 58.9 percent of the known CMS market. Any claim that coding agents are about to eliminate it would be difficult to support. (W3Techs)
The narrower risk is that a portion of what publishers currently consider essential may become optional.
The visual editor becomes less differentiated
A polished editor is valuable when it is the easiest way to communicate with the publishing system.
When a coding agent can translate natural-language instructions directly into valid site changes, the publisher may no longer care whether a platform has the best block editor, sidebar, template picker, or settings screen. The conversation with the agent becomes the interface.
That does not eliminate visual editing for everyone. It weakens its position as the only practical option.
Small customizations no longer require a plugin marketplace
Many blogging platforms expand through themes, plugins, extensions, and integrations. That ecosystem remains important for complex capabilities.
But a developer-operated static site can ask an agent to add a new post layout, modify a call-to-action, generate an RSS feed, adjust structured data, create a landing page, or change how related articles are selected. For contained changes, modifying the site may become easier than searching for, configuring, updating, and depending on another plugin.
The threat is therefore not to every plugin. It is to the long tail of relatively small features that previously justified installing one.
Publishing becomes part of the product codebase
For a company maintaining multiple products, keeping the articles beside the relevant website can provide useful context. The agent can see the site’s language, design system, existing pages, product terminology, internal links, and technical constraints in one place. OpenAI has described this broader principle as making the repository the system of record for agent work. Its own agent-first engineering experiment found that information needed by Codex had to be available as repository-local, versioned material, accompanied by mechanically enforced architectural rules. (OpenAI)
Applied to publishing, that means the brand guidelines, article conventions, metadata rules, internal-linking strategy, and validation requirements can live with the publication instead of being scattered across documents, platform settings, and human memory.
Platform switching costs may shrink
When articles are ordinary files and the published output is static HTML, the content is not inseparable from a particular editor.
Moving still requires work. Templates, URLs, redirects, subscriptions, comments, analytics, and media can complicate any migration. But the core articles are inspectable, searchable, versioned, and transformable by an agent.
AI does not eliminate migration costs. It can reduce the amount of manual work protecting those costs as a platform moat.
WordPress has clearly noticed the interface shift #
WordPress.com is not ignoring this development.
In February 2026, it introduced an AI assistant that works inside the editor and Media Library, with the ability to rewrite content, generate images, change layouts, add pages, and alter site-wide design through conversation. (WordPress.com)
By May, WordPress.com had expanded the assistant to all current paid plans and launched Studio Code in beta—a terminal-based coding agent designed specifically to build and modify WordPress sites. The company described a workflow in which the agent could create blocks, themes, plugins, and full sites, validate the generated result against the actual editor, inspect screenshots, and synchronize changes to staging or production. (WordPress.com)
That is not necessarily a sign of panic. It may be a sign that WordPress can absorb the change.
A traditional platform does not have to compete against agents by defending its dashboard. It can make the platform itself agent-operable. WordPress could remain the underlying content system while the human increasingly interacts with it through natural language and terminal workflows.
The risk is not simply that WordPress disappears.
The risk is that the familiar WordPress interface stops being the part users value most.
Substack faces a different kind of threat #
A static Codex-managed blog can replace a writing screen and publishing backend. It does not automatically replace distribution.
Substack combines long-form publishing with email delivery, recommendations, Notes, search, referrals, subscriptions, payments, podcasts, video, livestreaming, chat, and analytics. Its own positioning emphasizes the connection between publishing, audience discovery, community, and monetization. (Substack)
In April 2026, Substack added reusable post templates and expanded Notes scheduling and live-video tools—features aimed at making the platform an ongoing creator workflow rather than merely a place to host articles. (On Substack)
That suggests the greatest pressure from static, agent-managed publishing will fall on the content-management layer, not necessarily on the audience network surrounding it.
A publisher can own a static website and still need email delivery, subscriptions, discussion, discovery, or social distribution. Hacker News, Reddit, LinkedIn, newsletters, RSS, and search can all become the channels carrying content that originated elsewhere.
For platforms like Substack, the durable value may be less about where the article is typed and more about what happens after it is published.
Agent-managed does not mean unattended #
Removing the CMS dashboard does not remove the need for editorial discipline.
An agent can insert an incorrect fact, break a link, duplicate metadata, misunderstand a site convention, alter an unrelated file, or produce a page that builds successfully but looks wrong. A static workflow can also accumulate its own complexity through custom scripts, templates, dependencies, and deployment rules.
The reliable examples do not simply ask an agent to “write and publish.” They give it documented conventions, limited scope, validation commands, previews, diffs, and human approval.
That is the central tradeoff.
A traditional platform provides standardized guardrails. An agent-managed system allows customized guardrails, but someone must define and maintain them.
For one developer, a technical founder, or a small product team, that trade can be attractive. The publication becomes easier to shape around the business rather than forcing the business into a generic publishing workflow.
For a large editorial organization with many contributors, granular permissions, legal reviews, scheduled campaigns, subscriptions, and real-time collaboration, a mature platform may still be substantially easier to operate.
The CMS may become invisible #
The future of blogging is unlikely to be a simple choice between WordPress, Substack, and a folder of Markdown.
A more plausible outcome is that content platforms become increasingly invisible.
Some publishers will keep using familiar dashboards with AI built into them. Others will publish static files through coding agents. Some will retain WordPress as a headless backend while agents operate it through APIs. Others will own their websites but depend on external platforms for newsletters, payments, or discovery.
The traditional CMS bundled the interface, content model, workflow, storage, rendering, and publishing engine into one product because humans needed a manageable way to control all of them.
Coding agents make it possible to separate those pieces again without forcing the publisher to manage every technical detail manually.
That is the risk for conventional blog platforms: not immediate extinction, but a gradual reduction in what users must buy from them.
AI-generated writing is the obvious story because everyone can see the words.
AI-managed publishing may be the larger shift because it changes who—or what—operates the entire publication.
This article itself was published through the repository-managed system behind 64 Labs: a static content view, catalog metadata, generated artwork, automated checks, and a guarded deployment instead of a CMS dashboard.