You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: README.md
+7-5Lines changed: 7 additions & 5 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -23,7 +23,7 @@ being treated as daily-driver infrastructure.
23
23
| Per-secret destination allowlists | Working |[Outbound traffic gating](https://calciforge.org/#outbound-traffic-gating)|
24
24
| Local paste UI for one-shot and bulk `.env` secret input | Working |[Secret management](https://calciforge.org/#secret-management)|
25
25
| MCP and CLI tools for agent-facing secret-name discovery, with no value readback | Working |[Agent-facing tools](https://calciforge.org/#agent-facing-tools-mcp)|
26
-
| Telegram, Matrix, WhatsApp, and Signal routing | Working |[Multi-channel chat](https://calciforge.org/#multi-channel-chat)|
26
+
| Telegram, Matrix, WhatsApp, Signal, and text/iMessage routing | Working |[Multi-channel chat](https://calciforge.org/#multi-channel-chat)|
27
27
| OpenAI-compatible model gateway, provider routing, model aliases, alloys, cascades, dispatchers, exec models, and local model switching | Working |[Model gateway](docs/model-gateway.md)|
28
28
| Codex CLI and OpenClaw Codex subscription/OAuth integration paths | Working |[Codex integration](docs/codex-openclaw-integration.md)|
29
29
|`calciforge doctor` config/state/endpoint diagnostics | Working |[Quick Start](#quick-start)|
@@ -75,10 +75,12 @@ Channel-based secret input is intentionally being de-emphasized because
75
75
chat transports can retain plaintext values. Prefer the local paste UI
76
76
or direct `fnox` input for new secrets.
77
77
78
-
Route Claude Code or another HTTP-speaking agent process through the gateway.
79
-
The installer and examples bias toward setting this on managed subprocess
80
-
agents directly; for external daemons, set it on the agent process or its
81
-
service manager, not on the Calciforge daemon:
78
+
Calciforge-managed subprocess agents should get proxy environment from their
79
+
agent config or installer-generated config. Do not put proxy variables on the
80
+
Calciforge daemon itself; that can route Calciforge's own provider and
81
+
control-plane traffic through its security proxy. For externally managed agent
82
+
daemons that Calciforge does not launch, set plain HTTP proxying on the agent
83
+
process or its service manager and validate it against `security-proxy` logs:
0 commit comments