持续积累的实践记录。

Hardware

qibuddy: Agent hardware console for developers

The problem

Developers may run Claude Code, Codex, Gemini CLI, OpenCode, and other coding Agents at the same time. The difficult part is knowing which Agent is working, which is finished, and which is waiting for permission or an answer across many terminals and sessions.

qibuddy moves that status out of terminal windows and onto an always-visible, low-distraction desktop device that can also accept direct input.

Hardware and desktop

• ESP32-S3 console with an approximately 2.8–3.2 inch TFT display.
• Physical 1 / 2 / 3, BACK, GO, PRAISE / HEART, and FN / MODE buttons.
• A Rust desktop program connects Agents, manages state, and bridges USB serial or a simulator.
• A unified protocol carries Agent, session, state, event, permission, and user-action messages.
• Real hardware, a virtual device simulator, and desktop debugging are supported in parallel.

Core capabilities

• Status overview: Agent name, state, task summary, and elapsed time.
• Permission control: Approve or deny a requested command directly on the device.
• Choice input: Answer 1 / 2 / 3 when an Agent asks the developer to choose.
• Multi-session view: Switch between CLI sessions and prioritize those needing attention.
• Statistics: View tokens, sessions, active work, and waiting tasks.
• Shortcuts: Use GO, BACK, PRAISE, and FN for continue, back, confirm, and mode actions.
• Extensions: Leave room for plugins, JavaScript / Python workflows, and custom macros.

Current status

The project is in planning and implementation. The repository already contains a Rust workspace, desktop app, daemon, protocol, virtual-device simulator, Agent hook integrations, and ESP32-S3 firmware build preparation. Current work is converging the hardware form, screen hierarchy, button interactions, and real-device integration.

ESP32HardwareAgentDeveloper toolsBuilding