Observed Signal · Jun 24, 2026 · Technical Release · Source: DEV Community · Impact: 1/5 · Sentiment: Neutral
Old Phones as Bodies: LLM Agents Coordinate via Shared Log
An engineer describes a self-hosted, open-source multi‑agent system built from a laptop, several old Android phones, a small VPS and a home router. Sensors (mic, camera, BLE, GPS, accelerometer) run on phones via Termux and are accessed over SSH; the agents are LLMs running in tmux panes on a Linux host. Tailscale provides the mesh network and a shared text stream (tmux scrollback) is the agents' coordination log where they post [task]/[taking]/[done] markers. Design principles include strict separation of sensing and reasoning, a verification principle that requires real artifacts/tests (e.g., JPEG/.m4a) rather than trust, and a single-writer substrate for critical edits with rollback. The project is open-source (github.com/genaforvena/lte-workstation, CC0) and presented as an experiment rather than a product. Published 2026-06-24.
Technical, open-source experiment in agentic LLM systems that demonstrates novel coordination patterns but is a personal project with limited immediate impact on the broader AdTech/MarTech industry.
Track Telegram Signals & Market Shifts in Real-Time
Polaris7 autonomous intelligence agents track regulatory filings, primary sources, executive changes, and deal flow 24/7. Create your free Explorer workspace to monitor these entities.
Key Takeaways & Evidence Grounding
- The system is self-hosted and built from a laptop, several old Android phones, a small VPS, and a home router.
- Core software stack: bash, tmux, cron, Tailscale, and an LLM API key; phones expose sensors via termux-api over SSH.
- Agents run as LLMs inside tmux panes; tmux scrollback acts as the shared coordination log where agents post task markers.
- A verification principle enforces that tools produce real artifacts (e.g., JPEGs, .m4a) and sensors report UNKNOWN rather than falsely reporting clear readings.
- The project repository is published at https://github.com/genaforvena/lte-workstation (CC0).
Connected Companies & Entities
1 Entity mapped“I talk to it over Telegram; an agent hears me through a room phone's mic, thinks, and replies by voice over the same speaker....”
Ontology Mapping & Concepts
Related Market Signals & Shifts
Recent verified developments and strategic activity across this market segment.
Running Hermes Agent on Android Phone
A developer published a hands‑on guide showing how to run Hermes Agent — an open‑source agentic framework from Nous Research — on an Android phone using Termux. The post (May 16, 2026) details a one‑line install, configuring a provider (the author used DeepSeek), connecting a Telegram bot for messaging, and using Hermes tools (patch, read_file, cronjob, memory, etc.) to autonomously edit code, deploy to GitHub Pages, and run scheduled bounty scans. The author highlights Hermes' persistent memory, cron features (including a "--no-agent" mode to run scripts without invoking an LLM), and practical viability on ARM64 devices with limited RAM, positioning a smartphone as an always‑on, production‑capable AI workstation.
Developer Ships Autonomous Multi‑Agent LLM System
A developer using the handle PINGx published a detailed Dev.to post (2026-05-09) describing an open-source autonomous multi-agent system built in ~12 hours. The system runs on a single Google Cloud e2-small VM (~€13/month) and uses CrewAI, Google Gemini (Flash‑Lite for most roles, Pro for the CEO), ChromaDB for memory, and a SQLite metrics database. Key components include a KPI‑driven “CEO” agent that generates nightly strategic reports, an auditor crew that writes YAML proposals to improve worker agents (agents edit YAML, not Python), and a git-backed change workflow so autonomous edits are single-line commits and reversible. The first CEO run diagnosed four prior failed runs and produced actionable recommendations. Code is published at github.com/PINGxCEO/PINGx (MIT license); the author reports negligible per-run costs using GCP credits and free Gemini tiers.
AI Agents Using Real iPhones Spotlight Mobile Identity
A Dev.to analysis reviews a low‑visibility r/openclaw Reddit thread where a builder gave an AI agent control of a real iPhone using an “Appium type layer.” The author argues this illustrates a broader trend: agents will need persistent mobile identities (real phone numbers, app sessions, iMessage accounts) to operate in mobile‑only workflows that lack APIs. The post recommends a layered architecture (use APIs and iOS Shortcuts when available, fallback to UI automation), strict guardrails (approvals for sensitive actions, logging, allowlists), and model routing to control cost (use cheaper models for routine perception, stronger models for ambiguous or sensitive tasks). It notes practical deployment options — DIY Appium, device clouds (BrowserStack), or agent‑native platforms — and highlights cost pressures from tokenized billing, suggesting flat‑rate compute for long‑running agent workloads.
Track Real-Time Market Signals & Shifts
Set up custom watchlists to receive automated, evidence-grounded executive digests whenever material signals or shifts occur across your tracked landscape.