Clawd Presence

**Judgment:** A focused, minimal terminal-based presence display that does one job well: showing a live, glanceable status for an AI agent. It’s best suited to technically comfortable users who can dedicate a terminal or screen to the display. **What it does well** - Provides continuous, low-friction visibility into an agent’s state using simple CLI calls (`status.py`). - Color-coded states and short activity messages give quick context without opening logs or chat. - Simple setup (configure → run display → update from agent) with no backend services. - Auto-idle timeout reduces the risk of a frozen, misleading “busy” or “working” indicator. **Limitations / Risks** - Terminal-only: no web UI, mobile view, or multi-user dashboard; scaling to many agents is manual (multiple terminals/tmux panes). - No built-in authentication, multi-user permissions, or logging; status text could leak sensitive task names if the display is visible in shared spaces. - Reliability depends on the agent actually calling `status.py`; if it crashes or loses network, the display may not reflect reality until auto-idle kicks in. - Requires basic command-line and Python familiarity; not ideal for completely non-technical users. **Recommended scenarios** - Developer or ops environments where an AI agent runs continuously and you want an “at a glance” view of whether it’s idle, thinking, working, or needs attention. - Personal workstations with a spare monitor/terminal dedicated to agent presence (e.g., tmux session, side monitor). - Lightweight lab or hackspace setups where a full observability stack is overkill but ambient awareness of agent activity is useful. **Less ideal for** - Non-technical end users, large teams needing web dashboards, historical metrics, or complex workflows. - High-sensitivity environments where even short activity descriptions on a public display could expose confidential work.