Maybe tell your agent that your readme doesn't need to be that long so humans can read it and understand it. The Github readme is ludicrously long winded.
What's the point of this vs telling the agent to just use the cloudflare CLI?
"Local tool for publishing agent reports and small static sites" - Aren't agent reports small static sites? Why do you need to mention both?
Your Good Fits vs Bad Fits section is just a good fits vs bad fits for cloudflare pages, not your specific application.
Creating a chrome extension to add the publish button on the page is quite possibly the single biggest piece of evidence I've ever seen that code is now cheap.
Readme needs screenshots.
-----
Edit: I've been emotionally triggered by this project because the overall feel of it reminds me of all the junior developers at work who've started vibe coding everything and presenting it with confidence that even the most senior developers lack.
rolymath
This is nice, but I don't see much of a difference between just asking claude to write a wrangler config to push to cf pages, which can be extremely simple
Remote MCP could even allow you to share it with coworkers so they don't have to run anything
I usually use Claude Code but sometimes I find myself using chat and then when it creates an artifact sometimes I just want more flexibility or less restrictions. I might be missing something but I found it surprisingly hard to actually push an artifact to a custom URL. This was okay with Netlify as a connector, but I quickly ate through the free credits.
Unfortunately the Cloudflare connector surprisingly didn't expose the way to publish a site with just static files So I ended up having Claude just write the files to a folder with a script and a wrapper worker to make it all work and then everything was manual to republish.
Seems like if you have this all bundled up via MCP you can add as connector to chat and then get the same experience. But not sure if this is over engineered or if there's an easier way.
crisscrosscrash
When a URL is re-synced, do you keep older versions anywhere or does the new deployment completely replace them?
karthickrmchn
Is there by chance a way to password protect the generated site?
comments (6)
What's the point of this vs telling the agent to just use the cloudflare CLI?
"Local tool for publishing agent reports and small static sites" - Aren't agent reports small static sites? Why do you need to mention both?
Your Good Fits vs Bad Fits section is just a good fits vs bad fits for cloudflare pages, not your specific application.
Creating a chrome extension to add the publish button on the page is quite possibly the single biggest piece of evidence I've ever seen that code is now cheap.
Readme needs screenshots.
-----
Edit: I've been emotionally triggered by this project because the overall feel of it reminds me of all the junior developers at work who've started vibe coding everything and presenting it with confidence that even the most senior developers lack.
rolymath
mpeg
Remote MCP could even allow you to share it with coworkers so they don't have to run anything
I usually use Claude Code but sometimes I find myself using chat and then when it creates an artifact sometimes I just want more flexibility or less restrictions. I might be missing something but I found it surprisingly hard to actually push an artifact to a custom URL. This was okay with Netlify as a connector, but I quickly ate through the free credits.
Unfortunately the Cloudflare connector surprisingly didn't expose the way to publish a site with just static files So I ended up having Claude just write the files to a folder with a script and a wrapper worker to make it all work and then everything was manual to republish.
Seems like if you have this all bundled up via MCP you can add as connector to chat and then get the same experience. But not sure if this is over engineered or if there's an easier way.
crisscrosscrash
karthickrmchn
hbcondo714
ms_by_pd