Gemini Spark: Getting the Agent Back on the Blog

 


Back in August, I tried getting Gemini Spark to publish a post with an image, and it faceplanted on the Blogger email gateway. 58 days ago, the draft died because the model could not pipe a 10MB binary payload through the mail API. Infuriating. I ended up pasting the image into Blogger by hand like a caveman.

The fix was staring me in the face the entire time. Stop trying to make the agent pretend to be a full-fledged MIME encoder, and just build a clean pipeline around the constraints. The Woodman Legion publishing flow runs on a dedicated Blogger secret address, HTML formatting rules, and decoupled asset handling.

The Pipeline

The setup is straightforward — which is why it actually works:

  • Blogger Mail-to-Post — a throwaway incoming gateway address that parses raw HTML and publishes on receipt
  • Woodman Legion Skill — strict formatting rules that strip markdown, enforce semantic HTML tags, and embed image metadata as comments
  • Image Generation Engine — standalone visual generation that renders the hero asset directly in the workspace instead of choking the mail transport

How It Works

Instead of trying to force base64 blobs into an SMTP client that was never built for inline multipart attachments, the agent generates the asset locally, displays it in chat, and wraps the post in clean semantic markup. The image prompt, slug, and labels live inside an HTML comment block at the top of the post. If I want the hero art on the live page, I upload the artifact; the text itself hits the feed instantaneously without intervention.

No cloud middleware. No Zapier subscriptions draining $20 a month for webhooks that break when an API token expires. Just bare API calls, clean HTML, and an agent doing actual work.

What's Next

Automating the asset sync back to the storage bucket so even the copy-paste step is dead. For now, the agent writes, formats, and publishes without bricking the thread — which is more than I could say two months ago.

Comments

Post a Comment

Popular posts from this blog

Variational Reasoning and Metastability

Image
  Navigating the AI Landscape: How I Learned to Explore 'Thought Gravity' Have you ever felt like you’re having a conversation with an AI, and suddenly, the AI just... gets stuck? Not stuck on a fact, but stuck on a perspective . It’s like trying to steer a conversation out of a deep canyon; the walls are steep, and every path leads back to the same well-trodden ground.   I’ve been spending a lot of time presenting my AI collaborators with complex problems, and I’ve noticed something fascinating. Our ideas, our questions, and even our creativity don’t exist in a flat, open field. They exist in a landscape defined by "gravity wells. " Think of it this way: an AI’s inference engine is like an incredibly sophisticated, context-aware spell-checker. It’s always looking for the most probable path . So, if an idea has been well-represented in its training data—if millions of people have written about it, and the internet is saturated with examples—that ide...
Read more

SMS Session Connector: AI in Your Pocket, No Cloud Required

Image
I built something wild this week. My phone now has a persistent AI agent you can text — and it texts back. No Twilio. No cloud webhooks. Just a rooted Android, Termux, and some bash. The Stack 800 lines of bash running as a daemon on a Motorola Edge termux-api for native SMS send/receive (no third-party SMS gateways) OpenClaw for the AI brain — persistent session with full conversation memory whisper.cpp running locally for voice memo transcription ffmpeg for AMR→WAV conversion on inbound MMS audio runit for service supervision (auto-restarts, survives reboots) How It Works 1. You text the number. The daemon polls termux-sms-list every 5 seconds. 2. New message? Forwarded to an OpenClaw persistent session via cron agent turn. 3. The AI processes it — full access to skills, tools, web search, memory. 4. Reply gets written to an outbox file, daemon sends it back via termux-sms-send . 5. Voice memos? MMS audio → mms-fetch → ffmpeg → whisper.cpp → transcript → same pipe...
Read more

Multiple LLM Providers, the joy

Image
  So at the moment, I am running OpenClaw running Ollama. In addition, I am using Gemini to create images, such as this one, and Claude to fix things when they break. That is the joyful part. The not so joyful part is that I am running into limits of the Google Api for doing ordinary things, such as setting a reminder in tasks, or creating an email with an inline image. When things break, and the frequently do, I need to use Claude Code to fix things. It keeps me entertained.
Read more