teamai-cli 0.26.0-beta.0 → 0.26.0-beta.2

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "teamai-cli",
-  "version": "0.26.0-beta.0",
+  "version": "0.26.0-beta.2",
   "description": "TeamAI — Make Every Team AI Native (skill sync + shared knowledge base, powered by Git)",
   "type": "module",
   "bin": {

package/skill-data/core/SKILL.md

@@ -15,7 +15,11 @@ do not skip, reorder, or invent commands.
 
 Look at what the user typed after `/teamai`.
 
-**If they gave NO scenario** (bare `/teamai`, or only greetings/no task):
+**If they gave NO scenario right after a TeamAI friction reminder** (the
+`[teamai]` line that suggests `/teamai share what this session taught me`),
+that reminder is the scenario: load `teamai skill get share` and follow it.
+
+**If they gave NO scenario otherwise** (bare `/teamai`, or only greetings/no task):
 print the menu below **exactly**, then **STOP and wait**. Take no other action —
 do not run any command, do not load another skill yet.
 
@@ -62,7 +66,8 @@ Sharing a session's learnings needs no menu choice: TeamAI prompts on its own at
 the end of a session that produced something worth sharing, and that prompt means
 `teamai skill get share`. (Only when recall is on; it is off by default. The team turns it on with
 `sharing.recall.enabled: true` in `teamai.yaml`, a member with `teamai recall enable`;
-while it is off, `teamai skill get share` says so.)
+while it is off, or while the teamai config cannot be loaded, `teamai skill get share`
+says so and why.)
 
 ## Global rules
 

package/skill-data/core/references/commands.md

@@ -207,6 +207,34 @@ Generated: do not edit by hand. Regenerate with
   - `teamai webhook test` — Send test event to webhook endpoints
     - `--url <url>` — Test specific endpoint URL
 
+## models
+
+- `teamai models` — Share gateway model profiles and switch agents to them
+  - `teamai models list` — List team and personal model profiles and the agents using them
+  - `teamai models show <profile>` — Show a model profile without revealing its API key
+  - `teamai models add <id>` — Add a personal model profile stored only on this machine
+    - `--name <name>` — Display name
+    - `--protocol <protocols>` — Comma-separated: anthropic, openai-chat-completions, openai-responses
+    - `--base-url <url>` — Gateway root URL (without /v1)
+    - `--model <ids>` — Comma-separated model IDs; the first is the default
+    - `--from-env <name>` — Read the API key from this environment variable
+    - `--api-key-stdin` — Read the API key from stdin without placing it in shell history
+  - `teamai models configure <profile>` — Set the API key of a profile, or edit a personal profile
+    - `--from-env <name>` — Read the API key from this environment variable
+    - `--api-key-stdin` — Read the API key from stdin without placing it in shell history
+    - `--name <name>` — Personal profiles: new display name
+    - `--base-url <url>` — Personal profiles: new gateway root URL
+    - `--protocol <protocols>` — Personal profiles: serve models over these protocols too
+    - `--model <ids>` — Personal profiles: add model IDs
+  - `teamai models switch <profile>` — Point agents at a model profile (every compatible agent by default)
+    - `--agent <name>` — Only switch this agent. Repeatable or comma-separated.
+    - `--model <id>` — Default model to select (defaults to the first in the profile)
+    - `--dry-run` — Show what would change without writing
+  - `teamai models restore` — Restore agent model settings captured before the first TeamAI switch
+    - `--agent <name>` — Only restore this agent. Repeatable or comma-separated.
+    - `--dry-run` — Show what would change without writing
+  - `teamai models remove <profile>` — Remove a personal model profile without changing agent settings
+
 ## stats
 
 - `teamai stats` — Show local skill usage statistics

package/skill-data/core/references/contribute-member.md

@@ -8,7 +8,7 @@ team"*, in whatever language they work in — then you run the publish for them.
 ## Which kind of contribution?
 
 - **A learning** (a lesson, a gotcha, how you solved something) → this is
-  **automatic** once recall is on (off by default): TeamAI prompts at the end of a session worth sharing and the
+  **automatic** once recall is on (off by default) and the teamai config loads: TeamAI prompts at the end of a session worth sharing and the
   dedicated `share` workflow (`teamai skill get share`) takes over (it summarizes the
   session and runs `teamai contribute`). The user does not come through this flow
   for it. (Step A below is only a manual fallback for while recall is off.)

package/skill-data/core/references/troubleshooting.md

@@ -34,6 +34,20 @@ This is the #1 onboarding issue. In order:
    with `--scope user`.
 5. **Tool has no hook surface** (e.g. Gemini CLI, JoyCode): there is no auto-sync;
    run `teamai pull` manually each time.
+6. **Claude Code reads a different directory** (`CLAUDE_CONFIG_DIR` is set).
+   `teamai doctor` reports `Claude Code root matches CLAUDE_CONFIG_DIR` when the
+   directory the variable names is not the one this config syncs to. Re-run
+   `teamai init` from a shell that has the variable exported; it records the root
+   and moves the install. If the check says the value cannot be synced to (outside
+   your home, or nested deeper than `~/.config/<name>`), fix the variable first.
+6. **A command reports a broken manifest** (`Invalid roles manifest…`,
+   `Invalid projects manifest…`, `Invalid manifests…`, or `…manifest … could not
+   be read`). `pull` skips that scope on purpose, since syncing without the
+   manifest would deliver every namespace it gates; `push` stops before pushing
+   anything, even with `--role`; `status` lists the other resource types. The fix
+   belongs in the team repo's `manifest/roles.yaml` or `manifest/projects.yaml`,
+   which the error names by entry — tell the user to ask a team admin. Do not
+   delete the manifest or edit the local clone to get past it.
 
 ## Permission / access denied
 

package/skill-data/setup/references/join-member.md

@@ -88,6 +88,14 @@ teamai init --http https://your-team-host/api --token <api-key>
 This is a read-only consumer mode — `push` / `contribute` are not available, but
 skills and rules still sync.
 
+**Claude Code kept in a different directory (`CLAUDE_CONFIG_DIR`):** `init` records
+that directory (as `toolRoots.claude` in the local config) and syncs every Claude
+path there, so run `init` from a shell that has the variable exported. Re-running
+`init` after changing it moves the install (the old root's hooks, managed MCP
+servers and delivered model credentials are removed; its skills and rules are left
+and named in the output). To end the relocation, run `init` once with the variable
+set but blank: `CLAUDE_CONFIG_DIR= teamai init …`.
+
 ## Step 5 — Verify with doctor
 
 ```bash
@@ -143,7 +151,8 @@ Summarize the outcome **in the user's own language** (global rule 1). Cover:
    summarize and contribute it. They do **not** invoke `/teamai` for this. (This
    prompt only appears when recall is on — it is off by default; the admin turns it
    on in `teamai.yaml` (`sharing.recall.enabled`), a member with `teamai recall enable` — and the admin has not switched the
-   reminder off in `teamai.yaml`.)
+   reminder off in `teamai.yaml`. It also stays silent while their teamai config
+   cannot be loaded; `teamai skill get share` then names the file and the error.)
 3. **They can also contribute a skill — just ask in plain language.** A member does
    not need to be an admin to publish a skill. They tell TeamAI something like
    *"share this xxx skill with my team"*, in their own language, and you

package/skill-data/setup/references/manage-admin.md

@@ -81,6 +81,15 @@ teamai projects members <id> # who is registered on a project
 A member gets the union of their role resources and their active project's
 resources. Admins declare projects in `manifest/projects.yaml`, then `teamai push`.
 
+Every namespace that names a directory — `knowledge`, `skills` and `agents` in
+either manifest, and `learnings` in `projects.yaml` (a role's `learnings:` is
+ignored and unchecked) — must be a single path segment: no `/`, `\`, `:` or control character, no trailing
+`.` or space, and not a Windows device name (`CON`, `NUL`, `COM1`, …). Two
+namespaces of one resource type may not differ only by case, across both
+manifests. A manifest that breaks this, does not parse, or is empty stops
+members' pull for that scope until it is fixed; the error names the entry. Fix
+it rather than deleting it — with no `roles.yaml`, delivery is unfiltered.
+
 ## Team dashboard (web UI)
 
 ```bash
@@ -124,13 +133,16 @@ the team (`sharing.recall.enabled: true` in `teamai.yaml`, then `teamai push`; i
 off by default, and `teamai recall enable` turns it on for one machine only): at the end of a session
 worth sharing, TeamAI prompts the member and the dedicated
 `share` workflow (`teamai skill get share`) summarizes the session and runs
-`teamai contribute`. Nobody has to invoke it by hand.
+`teamai contribute`. Nobody has to invoke it by hand. (A member whose teamai config
+cannot be loaded gets no prompt; `teamai skill get share` names the file and the error.)
 (Publishing a **reusable skill** someone authored is a different task — any member
 can do it, see `"$(teamai skill path core)/references/contribute-member.md"`.)
 
 ### Turn the sharing prompt on or off (admin)
 
-The auto-share prompt is **on by default once recall is on**. To disable it team-wide, set this in
+The auto-share prompt is **on by default once recall is on**, and only shows in directories set up
+with teamai (never on a read-only HTTP source, or while a member's teamai config cannot be loaded).
+To disable it team-wide, set this in
 `teamai.yaml` and `teamai push`:
 
 ```yaml

package/skill-data/setup/references/setup-admin.md

@@ -187,9 +187,11 @@ If the repo does not exist yet, `init` offers to create it — accept the prompt
 - If `init` detects an unknown GitLab host, it stops and asks you to set
   `GITLAB_URL` + `GITLAB_TOKEN`, then retry.
 
-If the repo has roles enabled, `init` may ask for a primary role — pick one with
-the user, or pass `--role <id>` for a non-interactive run. Without a terminal
-(or with `CI` / `TEAMAI_NONINTERACTIVE` set) `init` never waits: a provider that
+If the repo has roles enabled, `init` asks for one or more comma-separated role
+numbers when running interactively. The first number is the primary role and the
+remaining numbers become additional roles; pass `--role <id>` for a
+non-interactive run when only a primary role is needed. Without a terminal (or
+with `CI` / `TEAMAI_NONINTERACTIVE` set) `init` never waits: a provider that
 would need a browser login fails at once and names the credential to prepare —
 a token for GitHub / CNB / GitLab / GitCode, and for TGit a prior `gf auth
 login` run in an interactive shell (see Step 3).
@@ -275,7 +277,8 @@ day-to-day work — they can keep letting the AI run things for them:
   its own at the end of a session worth sharing, and the `share` workflow
   (`teamai skill get share`) takes over. (Only once recall is on — off by default;
   turn it on team-wide with `sharing.recall.enabled: true` in `teamai.yaml`, then
-  `teamai push`.)
+  `teamai push`. Never on a read-only HTTP source, or while a member's teamai
+  config cannot be loaded.)
 
 Mention the underlying commands (`teamai push`, `teamai roles`, …) only as a note
 for users who *do* want them — the primary path is re-invoking `/teamai`.