From zedra
Open a new terminal on the connected phone via the running Zedra Host daemon. Use when the user wants to open a terminal on their phone, send a command to mobile, or launch a tool on the remote device.
How this skill is triggered — by the user, by Claude, or both
Slash command
/zedra:zedra-terminalThis skill is limited to the following tools:
The summary Claude sees in its skill listing — used to decide when to auto-load this skill
Open a new terminal on the connected Zedra mobile app via the running daemon.
Open a new terminal on the connected Zedra mobile app via the running daemon.
zedra status --workdir . 2>&1 || echo "NOT_RUNNING"
If NOT_RUNNING, tell the user to run /zedra-start first.
If $ARGUMENTS was provided, use it as the launch command:
zedra terminal --workdir . --launch-cmd "$ARGUMENTS"
If no arguments were provided, auto-detect the current agent tool and resume it:
Claude Code (when ${CLAUDE_SESSION_ID} is set):
zedra terminal --workdir . --launch-cmd "claude --resume ${CLAUDE_SESSION_ID}"
Codex:
zedra terminal --workdir . --launch-cmd "codex resume --last"
OpenCode:
zedra terminal --workdir . --launch-cmd "opencode --continue"
Gemini CLI:
zedra terminal --workdir . --launch-cmd "gemini --resume"
No agent detected — open a plain shell:
zedra terminal --workdir .
Report the result. The terminal appears on the user's connected phone.
npx claudepluginhub tanlethanh/zedra-plugin --plugin zedraBridges inbound iMessages to a Claude Code session via the njerschow/textme daemon. Lets whitelisted phone numbers send texts, voice notes, and images to drive Claude remotely.
Sets up Telegram/Discord channels for remote Claude Code access. Enables sending commands from phone via messaging apps with --auto flag and FORGE_OUTPUT=json protocol.
Wraps Claude Code as a daemon (launchd/systemd) to keep running after terminal closes. Required for HTTP bridge, webhooks, and scheduled tasks to run 24/7.