@interactive-inc/claude-funnel 0.29.0 → 0.31.0

package/README.md

@@ -42,7 +42,7 @@ Connector — a single attachment from a channel to an external source. Four typ
 
 Profile sits on top of that model as a launch convenience, not part of it — you never need one to run an agent (`fnl claude --channel <name>` is enough). It is a saved launch preset bundling `{ path, channelId, options, env, resume }` so `fnl claude --profile cto` reproduces a known setup: which directory to launch from, which channel to bind, and the launch recipe (args prepended to the claude argv, env layered under the process, session reuse). A profile carries a stable uuid `id` (the unit the PID file and the resumable session key off, so renaming it strands neither); `name` is just the handle you type. The first profile in the list is the default. Because a profile already binds a channel, `--profile` and `--channel` cannot be combined.
 
-The daemon is where all external connections live. It runs on port 9742, supervises connectors with auto-restart, broadcasts events to subscribed agent sessions over WebSocket, and serves the reply API that MCP calls. Starting or stopping an agent never starts or stops external connections.
+The daemon is where all external connections live. It runs on port 9742, bound to loopback (`127.0.0.1`) only so it is never reachable off-box; set `FUNNEL_HOST=0.0.0.0` to expose it deliberately (every privileged endpoint still requires the bearer token regardless). It supervises connectors with auto-restart, broadcasts events to subscribed agent sessions over WebSocket, and serves the reply API that MCP calls. Starting or stopping an agent never starts or stops external connections.
 
 The MCP layer is a thin bridge into the agent. It subscribes to the bound channel over WebSocket (the daemon does the work) and exposes one tool per callable connector so the agent can reply back out.
 
@@ -213,7 +213,7 @@ fnl gateway listeners                        live registry (alive / dead)
 fnl status                                   overall status (channels / profiles / gateway / clients)
 fnl schema                                   print the JSON Schema for funnel.json (pipe to a file for editor support)
 fnl update                                   `bun i -g @interactive-inc/claude-funnel`
-fnl                                          (no args) launch the OpenTUI dashboard
+fnl                                          (no args) show help
 
 fnl --version
 fnl --help                                   every subcommand has --help; verb-without-arg also returns help
@@ -442,16 +442,6 @@ console.log(await res.text())
 
 `cliApp` is the same app pre-wired to `new Funnel()` for callers who just want the default. The middleware sets the chosen Funnel onto `c.var.funnel`; the matching `Env` type is exported for composing custom routes that share the same context variable.
 
-### Launching the TUI
-
-`launchTui(funnel)` boots the OpenTUI dashboard against any `Funnel` instance — pass `Funnel.inMemory()` to drive it against a fake state, or your production funnel for a live view.
-
-```ts
-import { Funnel, launchTui } from "@interactive-inc/claude-funnel"
-
-await launchTui(new Funnel())
-```
-
 ### Validating connector configs
 
 Each connector type publishes its Zod schema, so consumers can parse external configs (JSON files, API payloads, etc.) before handing them to `addConnector`. The discriminated union `connectorConfigSchema` covers the whole set.