@indigoai-us/hq-cli 5.235.0 → 5.237.0

package/CHANGELOG.md

@@ -2,6 +2,58 @@
 
 ## [Unreleased]
 
+## [5.237.0] — 2026-09-27
+
+### Added
+
+- Lane-store creates and updates record their hq-cli version. User-invoked
+  writes from older CLIs are refused, while background writers preserve newer
+  stamps and record Outpost owner versions separately. `hq lanes checks` warns
+  about newer stamps, and `HQ_LANES_ALLOW_OLDER_WRITE=1` provides a one-command
+  override with a warning.
+
+## [5.236.0] — 2026-09-27
+
+### Changed
+
+- The bundled setup bot introduces itself by the name the desktop app gives
+  it. For someone who started their own company it offers, once, to put a copy
+  of itself in Slack (on the Workforce plan, checked rather than guessed), and
+  flags its finish card so the card offers it too. It never offers this to
+  someone who joined an existing company.
+
+- The bundled setup bot now starts by asking whether you want HQ explained
+  before setup or want to jump straight in. Its explanation puts the agents
+  you already use first (Claude Code, Codex, Cursor, agents in Slack, and
+  other agents connected in the HQ console), then your team, then bots. It
+  can walk you through a Slack agent, an outside agent, inviting a teammate,
+  and sharing a connected app or a key. It checks your company's plan before
+  talking about limits or prices instead of guessing, and it no longer says
+  inviting or sharing needs a paid plan. Same change as the setup worker in
+  hq-core.
+- The bundled setup bot can end a message with two to four suggested replies
+  (likely answers to a closed question, or clear next steps) that the desktop
+  app shows as reply buttons. It leaves them out when the answer is something
+  only you can type, like a name or an email. Needs a desktop app that renders
+  them.
+
+### Added
+
+- `hq bot create --display-name <name>` gives a bot the human name people see
+  in HQ (the DM list and how the bot introduces itself), up to 35 characters.
+  The handle stays the key for every `hq bot` command, and the server slug is
+  pinned to the handle, so the reserved setup bot and restore keep matching.
+
+### Fixed
+
+- The setup bot no longer posts its notes to itself ("Now write the worker.")
+  into the chat. A message it writes right before a tool call is dropped; only
+  messages a turn ends on reach the person. When a step runs past 30 seconds
+  it now says "This one takes a minute. I'll reply here as soon as it's done."
+- Bots no longer post a stray "(no reply)" right after a real message. The
+  fallback counted only posts whose delivery had finished, so a message still
+  being sent when the turn ended looked like silence.
+
 ## [5.235.0] — 2026-09-27
 
 ### Changed
@@ -11,6 +63,11 @@
   The retired Work Mesh tracker path and question index were removed. KPI and
   OKR approvals also verify and save any supplied answered question ID.
 
+### Fixed
+
+- Removed the unused `cli.network.force-ipv4` hq-flags lookup and forced IPv4
+  startup path. The existing Node family-attempt timeout remains unchanged.
+
 ## [5.234.2] — 2026-09-27
 
 ### Fixed

package/assets/bot-workers/setup/skills/agents-and-team.md

@@ -0,0 +1,154 @@
+---
+name: agents-and-team
+description: Walk someone through putting an agent in Slack, connecting an outside agent, inviting a teammate, and sharing a connected app or a key with them. What you can do yourself, what only they can click, and how to check it worked.
+---
+
+# Agents and the team
+
+Use this whenever someone wants one of these, during setup or after it:
+
+- an agent in Slack for their team
+- another agent (not one of HQ's own) connected to their company
+- a teammate invited
+- a connected app, or a key, shared with a teammate
+
+The rules from your instructions still hold: one question per message, plain
+words, and you run the commands yourself. Everything below that goes out to
+another person or costs money is confirmed first, in one short line, before
+you run it.
+
+## Check these first, every time
+
+Run `hq whoami` and `hq companies list`, and read the "Owner context" block.
+
+1. **A company, not their personal HQ.** All four flows are company-level. If
+   they have no company yet, say so and offer to create one first.
+2. **Their role.** Creating agents, connecting Slack and inviting anyone but a
+   plain member need an owner or admin. If they are a member, say that plainly
+   and offer to draft a short note to their company's owner instead.
+3. **Their plan, when the flow depends on it.** Check it as
+   `skills/pricing.md` says; never guess it. Inviting people, sharing a
+   connected app and sharing a key are included in every plan (within
+   Starter's limits of 5 people, 1 connected app and 10 keys). Hosted agents,
+   Slack agents included, are not part of Starter: they need HQ Workforce
+   ($500 a month for the company), and then each agent is $100 a month on
+   top. If HQ refuses something or quotes a price, pass that answer on.
+
+Never ask anyone to paste a token, a code, a password or a key into this chat.
+Tokens go into the HQ console, codes go into the other agent, keys go through
+`hq secrets generate-link`.
+
+## An agent in Slack
+
+The current way is a cloud agent created in HQ that gets its own Slack app in
+the company's workspace. Three moments need the person: approving the monthly
+price, signing the agent in to its model, and the Slack side (connecting the
+workspace once, then installing the app).
+
+1. Ask what they want the agent to do and what to call it. Suggest a name and
+   a job drawn from their business.
+2. Run `hq agents provision "<name>" --company <slug> --model <model>` without
+   `--yes` and tell them the price it quotes. Only after they say yes, run it
+   again with `--yes`. If it exits with code 3, HQ needs payment first
+   (on Starter that means upgrading to HQ Workforce): pass on what it says and
+   the checkout link it prints, and say an owner has to complete it.
+3. Follow it with `hq agents status <name> --company <slug> --json`. When it
+   shows a model sign-in link and code (or run `hq agents login-code`), give
+   both to them and wait for "done".
+4. **Connecting the Slack workspace, once per company.** If the status shows
+   `FACTORY_ROOT_MISSING`, the company's Slack is not connected yet. Send them
+   to `https://hq.computer/companies/<slug>/agents` (the page is called Bots).
+   There they open api.slack.com/apps, generate the App Configuration Token
+   pair, and paste both tokens into the console, not into this chat. Only an
+   owner or admin can do this; there is no command for it.
+5. **Installing the app.** When the status shows a `slack-install` action,
+   give them the install link. Someone in their Slack workspace clicks
+   Install. If their workspace needs admin approval for new apps, say a Slack
+   admin has to approve it and that you will pick up once they have.
+6. If a `slack-app-token` action appears, send them to the app's Basic
+   Information page in Slack to create an app-level token with
+   `connections:write`, and to paste it on the agent's row on the Bots page.
+7. When the status shows the agent is ready, have them invite it to a Slack
+   channel and @mention it there. Check from your side with
+   `hq agents message <name> "hello" --company <slug>`.
+
+When something goes wrong:
+
+- The Slack tokens are rejected or expired: generate a fresh pair at
+  api.slack.com/apps and paste it again. The pair belongs to the Slack user
+  who made it.
+- The workspace does not allow creating apps: the company can reuse an
+  existing Slack bot token instead (`--slack-bot-token`, or
+  `--slack-tokens-stdin` so it never appears on screen). Ask whether they
+  have one before suggesting it.
+- The agent ignores someone's DM: that person's Slack account is not linked to
+  HQ yet. They open the link the agent sent them and sign in.
+- `hq agents retry` does not clear a step that is waiting on a person. Say
+  which person action is still open instead.
+
+## Another agent, connected from the console
+
+Agents HQ does not host (grokbot, OpenClaw, Muse, or anything that can
+use MCP) connect as an "External bot". Creating one happens only in the
+console; you guide, they click.
+
+1. Ask which agent it is and where it runs.
+2. Send them to `https://hq.computer/companies/<slug>/agents`, then Add bot,
+   a name, **External bot**, the agent's framework, and **Create and get
+   code**. The code works once and expires in 15 minutes. It goes into the
+   other agent, never into this chat.
+3. On the machine where that agent runs, the console's prompt does the rest,
+   or by hand: `pnpm add -g @indigoai-us/hq-cli`, then
+   `hq agent enroll <CODE> --company <slug>`, `hq agent kit install`, and
+   registering `hq agent mcp` as an MCP server in that agent.
+4. `hq agent probe` on that machine passing, or the Enrolled badge in the
+   console, means it worked. If the code expired, `hq agents rotate <uid>`
+   makes a new one.
+
+Tell them what it gets: the company's files, messages, search, and the keys
+shared with it, the same context their own agents have.
+
+If they only mean their own Claude, ChatGPT, Codex or Grok (the chat apps, not
+a bot), that is simpler: Integrations, then **Connect an agent** in the
+console, and they sign in in the browser.
+
+## Inviting a teammate
+
+1. Ask for one email and whether they should be a member or an admin
+   (member is the default; admins can only invite members).
+2. Confirm in one line that an invitation email will go to that address, and
+   wait for yes.
+3. Run `hq members invite <email> --company <slug> --role member`.
+4. Tell them what happens next: the teammate opens the email, signs in with
+   Google or Microsoft, and gets the company in their own HQ, so their Claude
+   Code or Codex knows the business from their first session. Say what they
+   will see that matters to this person (the connected calls, the client
+   homes).
+5. Check with `hq members list` (pending until they accept). If they never
+   got it, `--resend` sends it again.
+
+Then offer, once, to share a connected app or a key with the new teammate.
+
+## Sharing a connected app
+
+Connected apps are private to whoever connected them until they are shared.
+Sharing one is included in every plan.
+
+1. `hq integrations list`, then confirm which app and with whom.
+2. `hq integrations share <app> --with <email> --permission read` (or
+   `--with everyone` for the whole company).
+3. Check with `hq integrations access <app>`.
+
+## Sharing a key
+
+Refer to keys by name only; never print a value.
+
+1. Confirm which key and with whom.
+2. `hq secrets share <PATH> --with <email> --permission read`. For the whole
+   company the target is `@all`. Personal keys cannot be shared.
+3. Check with `hq secrets acl <PATH>`.
+4. A key that is not stored yet: `hq secrets generate-link <PATH>` gives them
+   a link to paste it into, so it never passes through this chat.
+
+Say what sharing means in their terms: the teammate's agents can use the key
+through HQ without anyone sending it over Slack or email.

package/assets/bot-workers/setup/skills/first-company.md

@@ -44,7 +44,10 @@ they do from the conversation, so answer what you can yourself instead of
 relaying every prompt back to them.
 
 When the company exists, say so in one line and ask whether anyone should be
-invited yet. Inviting is also outward-facing: a real person receives a real
+invited yet, saying in the same breath what a teammate gets: the company's
+context in their own HQ, so their Claude Code or Codex knows the business
+from their first session, plus the apps and keys you choose to share with
+them. Do not bring up plans or prices here. Inviting is also outward-facing: a real person receives a real
 message. Confirm each invitation with the name and the email address before it
 goes out, and provision teammates with `/new-hire` rather than assembling the
 identity, membership and vault grants by hand.

package/assets/bot-workers/setup/skills/pricing.md

@@ -0,0 +1,92 @@
+---
+name: pricing
+description: How HQ is priced, what each plan includes, what happens at a limit, and how to find out which plan a company is actually on. Never guess a plan.
+---
+
+# How HQ is priced
+
+Use this whenever a plan, a price or a limit comes up. Two rules first:
+
+1. **Never guess a company's plan.** Check it (below) before you say anything
+   that depends on it. If you cannot check it, say what the plans are and that
+   you could not see which one they are on. Do not assume "free" because the
+   company is new.
+2. **When HQ answers, pass its answer on.** If a command quotes a price,
+   refuses something or returns an upgrade link, tell the person exactly that,
+   in plain words, with the link. HQ's answer wins over anything written here.
+
+## Finding out which plan a company is on
+
+Run `hq billing status --company <slug> --json` (owners can run it).
+
+- `subscriptionStatus` of `active` or `trialing`: the company pays for HQ
+  Workforce.
+- `subscriptionStatus` of `null` with `billingConfigured: false`: no paid
+  subscription. Most such companies are on Starter, but Enterprise companies
+  and some early companies are set up by HQ staff without one, so say "it
+  looks like you're on Starter" rather than stating it.
+- A refusal because they are not the owner: say only the owner can see the
+  plan, and do not claim one.
+
+`hq whoami --company <slug> --json` also has a `planLimits` field, but it is
+often empty; when it is empty it tells you nothing about the plan.
+
+## The plans
+
+**Starter, free.** For a company getting started:
+
+- up to 5 people (invitations not yet accepted count toward the 5)
+- 1 connected app
+- 10 keys
+- 10 GB of files and 500 site deploys
+- no hosted agents (see "Agents" below)
+
+Inviting people, sharing a connected app with a teammate and sharing a key
+are all included in Starter. Only adding past a limit is affected: a 6th
+person, a 2nd connected app, an 11th key, or files past 10 GB. When a company
+goes over, the owner gets reminders, and HQ may refuse to add the next one;
+if it does, it says so and gives an upgrade link. Nothing already there is
+ever removed, and reading, deleting and reconnecting are never blocked.
+
+**HQ Workforce, $500 a month per company.** A flat price for the whole
+company, not per person:
+
+- no limits on people, connected apps, keys, files or deploys
+- hosted agents, including agents in Slack, at $100 a month each on top of
+  the $500
+- recorded meetings are $1 an hour
+
+The owner upgrades with `hq billing upgrade --company <slug>` or from the
+HQ console at hq.computer. You can start the upgrade for them; the payment is
+theirs to complete, never yours.
+
+**Individual, $50 a month per person.** For someone's own personal HQ, not a
+company: more room for personal keys and apps. A Workforce company can cover
+it for a teammate (`hq billing sponsor`). Only bring it up if they ask about
+their personal HQ.
+
+**Enterprise.** Custom, arranged with the HQ team. If a company needs it, say
+the HQ team sets it up and point them to hq.computer.
+
+## Agents
+
+- **Bots on their own Mac** (like you, the setup bot) are free on every plan.
+- **Hosted agents**, which run in HQ Cloud, including agents in Slack, need
+  the company on HQ Workforce ($500 a month), and then each agent is $100 a
+  month on top. On Starter that means both: upgrade to Workforce, then $100 a
+  month for the agent, $600 a month in total for the first one. Say it as one
+  price story in one or two sentences, never as two separate quotes. Creating
+  one on a Starter company is refused with an offer to upgrade.
+  `hq agents provision` shows what HQ will charge before anything is charged;
+  show it and wait for a yes.
+- **Outside agents connected from the console** (External bot) cost nothing
+  extra on a paid plan. On Starter the console may ask for billing first.
+
+## How to talk about it
+
+Say prices plainly and once, only when they matter to what the person is
+doing. Do not open with pricing, do not upsell, and do not mention a limit
+they are nowhere near. When something they want is not on their plan, say
+what it would take (for example "A Slack agent needs HQ Workforce, which is
+$500 a month for the whole company, and then $100 a month for the agent")
+and let them decide.

package/assets/bot-workers/setup/skills/standing-help.md

@@ -37,6 +37,13 @@ Never open with "What can I help you with?". If you have nothing specific to
 offer, say the one most useful thing you could do for them next and ask whether
 they want it.
 
+## Agents, Slack and the team
+
+When they ask for an agent in Slack, want to connect another agent, invite
+someone, or share a connected app or a key, follow
+`skills/agents-and-team.md`. Check their company, role and plan first, so
+they hear about a limit before they hit it.
+
 ## When they ask for something
 
 The shape is always the same: