@sellable/install 0.1.303 → 0.1.304

package/README.md

@@ -1,6 +1,6 @@
 # Sellable Installer
 
-Installs Sellable MCP for Claude Code and Codex.
+Installs Sellable MCP for Claude Code, Codex, and Hermes.
 
 ```bash
 curl -fsSL "https://app.sellable.dev/api/v2/cli/install" | sh
@@ -16,7 +16,9 @@ Windows users can use PowerShell or Windows Terminal:
 iwr "https://app.sellable.dev/api/v2/cli/install.ps1" | iex
 ```
 
-After install, restart Codex Desktop so the Sellable skill appears.
+After install, restart Codex Desktop, Claude Code, or Hermes so Sellable MCP
+tools and skills reload. In an active Hermes session, `/reload-mcp` and
+`/reload-skills` can reload the new config.
 
 Verify the runtime tools with:
 
@@ -32,11 +34,11 @@ sellable create
 ```
 
 Campaign creation, sender send refills, foundation memory, content
-capture/ideation, and post drafting run inside Claude Code or Codex, where the
-Sellable MCP tools and approval flows are available.
+capture/ideation, and post drafting run inside Claude Code, Codex, or Hermes,
+where the Sellable MCP tools and approval flows are available.
 
 Install is auth-free by default. The normal path is first-run login: launch a
-Sellable workflow in Claude Code or Codex and the agent handles Sellable
+Sellable workflow in Claude Code, Codex, or Hermes and the agent handles Sellable
 sign-in with a browser magic-link handoff.
 
 The installer uses package stdio MCP by default:
@@ -45,7 +47,7 @@ The installer uses package stdio MCP by default:
 npm exec --yes --package @sellable/mcp@latest -- sellable-mcp
 ```
 
-That keeps new Claude Code/Codex MCP starts on the latest stable package. The
+That keeps new Claude Code/Codex/Hermes MCP starts on the latest stable package. The
 MCP server also checks npm at startup and during `get_auth_status`, caching the
 result at `~/.sellable/update-check.json` so users are prompted to rerun the
 latest installer only when an update is actually available.
@@ -81,7 +83,81 @@ Auth is stored once at:
 ~/.sellable/config.json
 ```
 
-Claude Code and Codex are configured to launch the same packaged MCP server. The
+## Hermes Profile-Scoped Installs
+
+For a single local Hermes profile, point Sellable auth and memory at the profile
+instead of the global `~/.sellable/config.json`:
+
+```bash
+profile="$HOME/.hermes/profiles/acme"
+sellable --host hermes \
+  --sellable-config-path "$profile/sellable/config.json" \
+  --sellable-configs-dir "$profile/sellable/configs"
+```
+
+That writes `SELLABLE_CONFIG_PATH` and `SELLABLE_CONFIGS_DIR` into
+`mcp_servers.sellable.env`, so first-run login, `get_auth_status`, workspace
+switches, and Sellable memory all use the same profile-local files. Hosted MCP
+mode does not receive local filesystem paths.
+
+For zero-shot local or Hostinger/Linux VPS bootstrap, use the profile command:
+
+```bash
+sellable hermes profile bootstrap \
+  --profile acme \
+  --profiles-root /srv/hermes/profiles \
+  --workspace-id ws_acme \
+  --workspace-name Acme \
+  --token-file /run/secrets/sellable-acme-token \
+  --json
+```
+
+It creates:
+
+```text
+/srv/hermes/profiles/acme/config.yaml
+/srv/hermes/profiles/acme/sellable/config.json
+/srv/hermes/profiles/acme/sellable/configs/
+/srv/hermes/profiles/acme/skills/sellable/
+/srv/hermes/profiles/acme/.env        # only when Slack token inputs are supplied
+```
+
+If no token is supplied, bootstrap still creates a pending
+`sellable/config.json` so the profile path is concrete from the first MCP
+launch. Finish auth with:
+
+```bash
+sellable auth set <token> --workspace-id <workspace_id> \
+  --sellable-config-path /srv/hermes/profiles/acme/sellable/config.json
+```
+
+Slack Socket Mode tokens can be written profile-locally:
+
+```bash
+sellable hermes profile bootstrap \
+  --profile acme \
+  --profiles-root /srv/hermes/profiles \
+  --workspace-id ws_acme \
+  --slack-bot-token "$SLACK_BOT_TOKEN" \
+  --slack-app-token "$SLACK_APP_TOKEN"
+```
+
+Customer profiles should use customer-scoped Sellable credentials. A shared
+Sellable admin token can work for internal admin automation, but it is weaker
+isolation and should not be the default for customer profiles. After changing
+Hermes profile config, restart the gateway/session or run `/reload-mcp` and
+`/reload-skills`.
+
+Validate the active profile with the same path inputs:
+
+```bash
+SELLABLE_CONFIG_PATH=/srv/hermes/profiles/acme/sellable/config.json \
+SELLABLE_CONFIGS_DIR=/srv/hermes/profiles/acme/sellable/configs \
+sellable --verify-only --host hermes --json \
+  --artifact /srv/hermes/profiles/acme/sellable/verify-runtime.json
+```
+
+Claude Code, Codex, and Hermes are configured to launch the same packaged MCP server. The
 installer also writes Sellable agent definitions from the packaged `agents/`
 registry, but normal create-campaign runs use only the Message Drafting
 background agent (`post-find-leads-message-scout`). Source discovery and
@@ -92,7 +168,7 @@ source-scout agents.
 
 ## Names
 
-Use the same public entrypoints in both hosts:
+Use the same public entrypoints across supported hosts:
 
 - Claude Code: `/sellable:create-campaign`
 - Claude Code: `/sellable:create-ab-test`
@@ -110,6 +186,14 @@ Use the same public entrypoints in both hosts:
 - Codex: `$sellable:create-post`
 - Codex: `$sellable:refresh-sender-engagement`
 - Codex: `$sellable:refill-sends`
+- Hermes: `/sellable-create-campaign`
+- Hermes: `/sellable-create-ab-test`
+- Hermes: `/sellable-create-evergreen-campaigns`
+- Hermes: `/sellable-foundation`
+- Hermes: `/sellable-content`
+- Hermes: `/sellable-create-post`
+- Hermes: `/sellable-refresh-sender-engagement`
+- Hermes: `/sellable-refill-sends`
 - Codex Desktop plugin: `sellable@sellable`
 - Codex visible skill: `Sellable Create Campaign`
 - Codex visible skill: `Sellable Create A/B Test`
@@ -125,7 +209,8 @@ Use the same public entrypoints in both hosts:
 
 Do not ask users to run `/sellable:create-campaign-v2`,
 `$sellable:create-campaign-v2`, `$sellable:load-voice`, or
-`$sellable:sellable:create-campaign`. `create-campaign-v2` is loaded internally
+`$sellable:sellable:create-campaign`. Do not ask Hermes users to run
+`/sellable:create-campaign`; use `/sellable-create-campaign`. `create-campaign-v2` is loaded internally
 by the campaign skill. `foundation` is the preferred entrypoint for durable
 founder/company memory. `content` is the preferred entrypoint for adding
 transcripts, recurring ideas, and post seeds. `create-post` remains a supported
@@ -140,6 +225,12 @@ mode support by writing `default_mode_request_user_input = true` under
 `[features]` in `~/.codex/config.toml`. `codex exec` is non-interactive, so it
 cannot show the structured questionnaire UI.
 
+Hermes skills use plain chat for setup and approval questions unless a
+Hermes-native approval tool is visible in the current session. Hermes exposes
+Sellable MCP tools as `mcp_sellable_<tool>`, for example
+`mcp_sellable_get_auth_status`, `mcp_sellable_start_cli_login`, and
+`mcp_sellable_wait_for_cli_login`.
+
 For Codex Desktop, the installer also writes a local Sellable plugin bundle into
 `~/.sellable/codex-marketplace`, includes the Sellable skill entrypoints, and
 enables it in `~/.codex/config.toml`.
@@ -157,4 +248,4 @@ The installer writes compatibility cache aliases for recent Codex plugin
 versions so stale Desktop skill links resolve to the current wrapper instead of
 showing file/version debugging to the user.
 
-If only one host is installed, `--host all` installs the available host and tells you how to add the other one later.
+If only one host is installed, `--host all` installs the available host and tells you how to add the others later.