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...
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...
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.
Comments
Post a Comment