How Ulanzi Studio Syncs Codex / Claude Status to Vibe Key
After Vibe Key is connected, Ulanzi Studio attempts to automatically install Hooks for Codex and Claude Code on the computer. When you start a new session and begin working in Codex or Claude, Ulanzi Studio monitors the agent status and syncs it to the Vibe Key key and knob lights. This helps you see whether a task is running, needs confirmation, or requires your attention.
Getting started
- Open Ulanzi Studio: Make sure the software is installed and running.
- Connect Vibe Key: Connect the device and wait for Ulanzi Studio to recognize it.
- Install Hooks automatically: If Codex or Claude Code is installed, Ulanzi Studio attempts to install the corresponding Hooks.
- Start a new session: Open Codex or Claude, create a new session, and start working.
- Check the lighting feedback: Vibe Key displays lighting feedback as the agent status changes.
Lighting indicators
- Key K1: Voice input status. It breathes while listening and is off in other states.
- Key K2: A confirmation is pending. It breathes when confirmation, approval, or continuation is needed.
- Key K3: The task can be cancelled or interrupted, or human intervention is needed. It breathes in these states.
- Knob light: The agent is still progressing. It stays on while the agent is thinking, executing, or organizing work in the background.
Lighting rules
- Vibe Key displays the status of only one focused session at a time.
- Multiple sessions do not compete for the lights simultaneously.
- All breathing indicators use one consistent rhythm.
- One approval and multiple approvals use the same lighting; multiple breathing indicators are not stacked.
- The number of pending items is shown through the interface, voice, or a list, not through the lighting rhythm.
Lock screen and sleep
Locking the screen usually does not affect the agent continuing to work, so status synchronization generally continues.
Sleep usually pauses local processes. The agent and Hooks generally stop running, and Vibe Key status synchronization is interrupted.
For long-running tasks, avoid automatic sleep. Locking the screen is usually fine, but sleep may pause the task.
FAQ
Why are the Vibe Key lights off?
Possible causes include an unsuccessful device connection, a lighting mode other than Working, Ulanzi Studio not running, Hooks not being installed correctly, no active session, or the computer being asleep.
Why does Vibe Key not respond while Codex / Claude is working?
Check that Ulanzi Studio is still running in the background, Hooks are registered successfully, the session is new or its status has changed, and the computer has not entered sleep.
How can I confirm that Hooks were installed successfully?
In Claude Code, use /hooks in the terminal.
For Codex, check the Hooks configuration in ~/.codex/ or the project's .codex/ directory. You can also check Codex → Settings → Hooks → User configuration.
Why do multiple approvals show only one breathing indicator?
This is by design. Vibe Key indicates that there are pending items, not how many; multiple approvals do not stack multiple breathing indicators.
Will a task stop when the screen is locked?
Usually not. Locking the screen normally does not stop the task.
Will a task stop after the computer goes to sleep?
Usually yes. Sleep generally pauses local processes and status synchronization.
What should I do if it stops working after reinstalling the system or upgrading the client?
Return to Ulanzi Studio and run the Hooks installation or repair again.
Troubleshooting
- Confirm that Vibe Key is connected.
- Confirm that Ulanzi Studio is running.
- Confirm that Codex or Claude has a new session open.
- Check that Hooks were installed successfully.
- Check whether the computer has entered sleep.
- If the issue persists, reinstall or repair the Hooks.
Related documentation: Codex Hooks, Claude Code Hooks Guide.