Core voice bridge
Tap earbuds, ask for workspace status, hear short updates, and approve or cancel actions through the local bridge.
DevPods keeps the local development loop close: status, diffs, CI, approvals, and agent direction move through your own desktop bridge.
Android catches the earbud gesture and voice. The desktop bridge decides what is allowed, what needs approval, and what reaches your tools.
Ask what changed, redirect an agent, approve a plan, cancel a task, or hear a completion report without turning DevPods into a cloud command relay.
What it is
DevPods is a local-first voice presence layer: Android captures the earbud interaction, the desktop bridge owns safety, and optional agent tooling moves work forward only through approved paths.
Tap earbuds, ask for workspace status, hear short updates, and approve or cancel actions through the local bridge.
Connect OpenClaw or Hermes so a local coding agent can plan, report, pause, redirect, and complete approved work.
Add local codebase context, impact analysis, route maps, changed areas, and tool awareness when deeper planning matters.
Architecture
DevPods routes earbud gestures and speech into your own machine. The bridge handles pairing, policy, approvals, audit, workspace access, and optional agent handoff.
Bluetooth earbuds
Gesture and mic path
Android relay
Wake, speech, approvals
Desktop bridge
Policy and local routing
Agent runtime
OpenClaw or Hermes
Local workspace
Repo, tests, git, CI
The website uses the app theme as a reference, but the product story stays web-native: relay, bridge, approvals, workspace tools, and optional agent runtime.
>- show status
Two files changed. Tests are idle.
>- approve plan after summary
Approval paused at desktop bridge.
Setup tiers
The installer can guide developers into Core, Agent, or Intelligence mode without forcing indexing, embeddings, or an autonomous runtime on day one.
Lightweight voice control for your local developer workspace.
Talk to your local coding agent without sitting at your desk.
Codebase-aware collaboration, still local-first.
Product surface
The site should sell presence, not novelty: wake, ask, approve, redirect, hear the useful bit, and keep moving.
Trust boundary
DevPods is designed around local control. Code, diffs, workspace state, raw audio, and transcripts are not sent to a cloud command relay by default. Dangerous actions still require explicit confirmation.
Pairing, approvals, workspace routing, and audit decisions stay on the machine.
The Intelligence Layer can be enabled, disabled, or removed without changing the Core voice bridge.
Risky agent actions pause for confirmation instead of becoming invisible voice automation.
Compatibility
Compatibility is verified per phone and earbud combination, with clear support states and fallback paths.
Wake, speech, and approval paths verified on a specific phone and earbud combination.
The signal is visible and usable, with more confirmation needed before claiming full support.
Hands-free path falls back cleanly to push-to-talk or assistant controls.
DevPods says so plainly instead of pretending every headset can do everything.
Install flow
The setup mirrors the mobile app: bridge pairing first, device truth second, then the listening state only when DevPods knows what path is available.
Choose Core, Agent, or Intelligence
Install the desktop bridge
Pair Android with a QR code
Run the earbud capability check
Tap, speak, approve, and stay in flow
Downloads
The beta surface is direct: install locally, pair Android, verify earbuds, and add agent or intelligence layers later.
Windows beta installer with local pairing, policy, approval, and workspace routing.
Download betaAPK beta for earbud gestures, speech capture, and spoken responses.
Get APKQuick start, pairing, compatibility, privacy, and troubleshooting guides.
Read setupRoadmap
Desktop bridge, Android relay, QR pairing, wake test, approvals.
OpenClaw and Hermes agent routing with spoken progress reports.
Local intelligence layer with codegraph context and impact-aware answers.