Skip to content

Evenfire is an intelligence layer platform for running LLM agents that take real actions, on your infrastructure

TypeScript

docs: address review findings on the reference docs

Jose Gabriel Ramirez Encinas95e3d686c834
diff --git a/docs/how-to/manage-users-and-teams.md b/docs/how-to/manage-users-and-teams.md
index 88ecb3b90..37685d028 100644
--- a/docs/how-to/manage-users-and-teams.md
+++ b/docs/how-to/manage-users-and-teams.md
@@ -31,19 +31,18 @@ pages redirect to the **Agents** tab.
Every team membership has one of three roles. The API and database store the
value; the Control UI shows a label.
-| Stored value | Control UI label | Invite members | Invite someone as `admin` | Change roles, remove members |
-| ------------ | ---------------- | -------------- | ------------------------- | ---------------------------- |
-| `admin` | Leader | Yes | Yes | Yes |
-| `inviter` | Inviter | Yes | No | No |
-| `member` | Participant | No | No | No |
+| Stored value | Control UI label | Invite members | Change roles, remove members |
+| ------------ | ---------------- | -------------- | ---------------------------- |
+| `admin` | Leader | Yes | Yes |
+| `inviter` | Inviter | Yes | No |
+| `member` | Participant | No | No |
The team detail Members table shows the same thing as two read-only columns,
**Can Invite Members** and **Can Delete Members**. The role editor sets the
role through those two checkboxes: delete implies invite.
-These roles govern what a member can do **for their own teams** through the
-member-facing API (`/external/members/*` and `/external/teams/*`), which the
-[profile UI](../surfaces/profile-ui.md) uses. In that API:
+These roles govern what a member can do **for their own teams** from the
+[profile UI](../surfaces/profile-ui.md). There:
- An `admin` or `inviter` can send, resend, and revoke member invitations for
teams where they hold that role.
diff --git a/docs/reference/configuration.md b/docs/reference/configuration.md
index 3f8a6c0a0..28f7f6e17 100644
--- a/docs/reference/configuration.md
+++ b/docs/reference/configuration.md
@@ -9,12 +9,16 @@ Full per-service variable lists live in each service's README (see
[Where every variable is documented](#where-every-variable-is-documented)).
> **`mcp-host-config` is not in `deploy/base`.** host-context-controller loads
-> the `mcp-host-config` ConfigMap into every agent pod, but only the minikube
-> overlay ships one (`deploy/overlays/minikube/configmaps/mcp-host-config.yaml`).
-> Without it, mcp-host uses its code defaults, so the mcp-host rows below are
-> off until your overlay provides that ConfigMap.
+> the `mcp-host-config` ConfigMap into every agent pod with a non-optional
+> `envFrom`, so agent pods fail to start (`CreateContainerConfigError`) until
+> you create it. Only the minikube overlay ships one
+> (`deploy/overlays/minikube/configmaps/mcp-host-config.yaml`); copy it and
+> review each value (see [Production deployment](../deploy/production.md)).
+> Variables you leave out take mcp-host's code defaults, so the mcp-host rows
+> below are off unless your ConfigMap sets them.
-Boolean switches accept only the string `true` unless noted.
+Set boolean switches to the lowercase string `true`. Some services also accept
+`1` or other casings, but `true` works everywhere.
## Off in `deploy/base`, on in the minikube overlay
diff --git a/mcp-host/README.md b/mcp-host/README.md
index 85f669311..853cb5eae 100644
--- a/mcp-host/README.md
+++ b/mcp-host/README.md
@@ -346,8 +346,10 @@ from the env var shown; in a cluster it comes from the Secret named by
| `grok-subscription` | xAI Grok subscription | none; set a model | none (OAuth sign-in) |
Vertex AI, Bedrock and Azure also need the non-secret settings listed under
-[LLM and models](#llm-and-models). The two subscription providers are off unless
-their `MCP_HOST_*_SUBSCRIPTION_ENABLED` flag is set; see
+[LLM and models](#llm-and-models). The two subscription providers are off by default.
+For Codex, set `MCP_HOST_CODEX_SUBSCRIPTION_ENABLED=true` in `mcp-host-config`.
+For Grok, set nothing here: HCC adds `MCP_HOST_GROK_SUBSCRIPTION_ENABLED` to each
+Host that is eligible for Grok. See
[Use a ChatGPT or Grok subscription](../docs/how-to/connect-llm-subscription.md).
Which providers work in which runtime, and how the model allowlist applies, is
in [LLM providers](../docs/llm-providers/README.md).
diff --git a/mcp-host/package-lock.json b/mcp-host/package-lock.json
index 1928bc87d..0e6daaf99 100644
--- a/mcp-host/package-lock.json
+++ b/mcp-host/package-lock.json
@@ -1,12 +1,12 @@
{
"name": "clerum-mcp-host",
- "version": "0.1.557",
+ "version": "0.1.558",
"lockfileVersion": 3,
"requires": true,
"packages": {
"": {
"name": "clerum-mcp-host",
- "version": "0.1.557",
+ "version": "0.1.558",
"license": "SEE LICENSE IN LICENSE",
"dependencies": {
"@anthropic-ai/sdk": "^0.32.0",
diff --git a/mcp-host/package.json b/mcp-host/package.json
index 2e9f5111a..17bcdd016 100644
--- a/mcp-host/package.json
+++ b/mcp-host/package.json
@@ -1,6 +1,6 @@
{
"name": "clerum-mcp-host",
- "version": "0.1.557",
+ "version": "0.1.558",
"description": "MCP Host - reads Host CRD and provides LLM access via OpenAI/Claude",
"main": "dist/main.js",
"engines": {