Tidal Echo plugin

Install

Works in

• Claude Code

Manual install

{"mcpServers": {"companion": {"command": "bun", "args": ["run", "--cwd", "/абсолютный/путь/companion-channel", "--silent", "start"]}}}

What it does

Tidal Echo links a phone to a Claude Code session running on a computer. The repository has three parts: `backend/` (a FastAPI relay with SQLite that fans messages out over SSE), `web/` (a single-page HTML PWA installed on the home screen) and `channel/` (a Claude Code plugin on Bun and MCP). A message from the phone appears in the session as a `<channel>` block, the agent replies by calling the `reply` tool, and the answer reaches the phone as a chat message. A single shared secret, `RELAY_SECRET`, protects access: there are no user accounts and no third-party hosting, messages pass only through your server. MiniMax voice and Web Push are optional and switch off with empty settings. Any model with an OpenAI-compatible API can replace Claude Code: the `examples/bridge_any_llm.py` script swaps the AI side. The `examples/api_loop.py` script keeps a resident agent on the server with a fallback model chain, images and attachments, MCP tools over stdio or streamable-http and a system prompt file that reloads without a restart.

Who it is for. People who message their own Claude Code session from a phone and keep the chat only on their own server.

Example request

Deploy Tidal Echo following AGENTS.md: the relay on my VPS, the PWA on my domain, the plugin in Claude Code, and test the chain with a message from the phone

Limitations

• The system is built for one user with one `RELAY_SECRET`, there are no user accounts.
• The PWA needs a domain with HTTPS: without it installation, the service worker and Web Push do not work.
• Claude Code starts with the `--dangerously-load-development-channels server:companion` flag, and every start shows a confirmation dialog. For an automatic answer the repository ships scripts for tmux and Windows.
• The documentation is in Chinese, the last commit is from September 2026.

How to disable. Close the Claude Code session started with `--dangerously-load-development-channels` and remove the companion key from `.mcp.json`. Stop the relay service with `systemctl disable --now companion-relay`, then delete `~/.claude/channels/companion/.env` and the SQLite database on the server.

README in short

The README, in Chinese, explains the three-part scheme, the full deployment order (relay, PWA, plugin), the option of using the frontend with your own backend and the protocol: three required API endpoints and optional ones. A separate section covers the server API loop.