Okena plugin
The okena-lifecycle plugin reports Claude Code state to Okena: tab color, an agents list and a finish notification.
- 103 ★ on the repository
- Last commit
- MIT
Extended access
Why this level
- Hooks run on every prompt and tool call and write to `/dev/tty`.
- Okena has a local HTTP and WebSocket remote-control server: review its settings and pairing.
Install
- Works in
Manual install
/plugin marketplace add ./integrations/claude-codeRun it from a clone of the repository. It is followed by `/plugin install okena-lifecycle@okena`.
Access and checks
How we reviewExtended accessThe tool runs code or makes network calls and only reads external data.
- Hooks run on every prompt and tool call and write to `/dev/tty`.
- Okena has a local HTTP and WebSocket remote-control server: review its settings and pairing.
This is third-party code. Review the repository files before installing.
What it does
Okena is a terminal multiplexer written in Rust with GPUI, featuring tabs, splits and workspace restore. The repository ships a Claude Code plugin, `okena-lifecycle`, whose hooks tell the terminal what the agent is doing: working, waiting for permission, failed or finished a turn. From those signals Okena recolors the tab icon, builds an Agents section in the sidebar across all projects and raises a notification when an agent finishes or is blocked. The plugin is added as a marketplace from the `integrations/claude-code` directory.
Who it is for. Developers running several Claude Code sessions in different panes who want to see which agent is waiting for input.
Good fit when
- Five Claude Code sessions run in different projects and you want one list of states.
- An agent is blocked on a permission prompt while you work in another tab.
- You want a notification when a long task finishes.
- A session is resumed after a restart and Okena picks up its identifier.
Not a fit when
- You work on Windows without WSL: native cmd and PowerShell panes cannot report agent status.
- You need the status of another agent: working glue exists only for Claude Code.
- Switching your current terminal to Okena does not suit you.
Example request
Run `claude` in an Okena pane and check that the tab icon changes color while working and on a permission prompt.Limitations
The plugin works only inside the Okena terminal. The hook script is written in `sh` and uses `/dev/tty`, `base64` and `sed`, so Unix and WSL are supported. Codex has a registered harness without session resume or capture hooks. Mobile clients do not get notifications yet. The README installs Okena itself with `curl ... | bash`: read the script before running it. A status stays until the next signal, so a finished turn remains marked until the agent reports a new one.
How to disable. Disable the plugin in Claude Code (`/plugin`) or remove `okena-lifecycle@okena` from `enabledPlugins` in `~/.claude/settings.json`. The Show Agents in Sidebar setting hides the Agents section in Okena.
FAQ
Which states does the plugin report?
Five: `working`, `blocked`, `done`, `error` and a reset at session start and end. The `UserPromptSubmit`, `PreToolUse` and `PostToolUse` hooks give `working`, while `Stop` gives `done`.
Does Okena read the agent output?
No. The agent writes a short escape sequence to its terminal itself; Okena neither parses the output nor reads the private files of the agent.
Do I need Okena for the plugin?
Yes, without the Okena terminal nobody receives the signals.
What if the tab does not change color?
Check that `claude` runs inside an Okena pane: the `$OKENA_TTY` variable is set only there and only on Unix.
Does the plugin work on Windows?
Only inside WSL. In native cmd and PowerShell panes the setup silently does nothing.
Discussion
No questions or reviews yet.
Related
PluginsA pixel-art office on screen shows Claude Code agents at work: who is busy, who awaits approval and what each session costs.
A Claude Code plugin with seven specialized subagents and approval gates: the agent proposes a plan and waits for confirmation before touching code
Three Claude Code plugins: the savvy-flow orchestrator with tiered subagents and two mods for a progress panel and a cache timer
A Claude Code and Codex plugin with skills for code research, tests, refactoring and independent review of finished changes
A Claude Code plugin that puts context usage, active tools, running subagents and todo progress into the statusline
A large Claude Code and Cursor plugin: development skills, specialist agents and hooks with quality gates and git protection
Comparison with similar tools
Cards that share the main search query, and how they differ.
| Tool | Official | Repository stars | Main difference |
|---|---|---|---|
| Okena (this card) | no | 103 | |
| cmux | no | 28,779 | a multiplexer for agents with its own session model; Okena adds Claude Code hook plugin inside a general terminal |
| Claude Squad | no | 8,790 | manages parallel sessions through tmux and worktrees; Okena shows agent state in terminal panes |
README in short
To connect the plugin, add the marketplace from `integrations/claude-code` and install `okena-lifecycle@okena`. Claude Code hooks map to the `working`, `blocked`, `done` and `error` states.