@mmmnt/flmnt 1.10.0 → 1.10.2

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
Files changed (2) hide show
  1. package/README.md +17 -4
  2. package/package.json +1 -1
package/README.md CHANGED
@@ -26,12 +26,23 @@ Authenticate, pick a workspace, and wire Claude Code to your flmnt MCP:
26
26
 
27
27
  ```sh
28
28
  flmnt login # OAuth2 — browser PKCE (or --device for headless)
29
- flmnt workspace use <name|id> # set the active workspace
30
- flmnt setup --server-url <flmnt-url> # write .mcp.json + the automation kit
29
+ flmnt setup --server-url <flmnt-url> --project <name> # wire this repo to a workspace
31
30
  ```
32
31
 
32
+ `--project` names the workspace **this repo** records into, by name — you do not need its id. It is required, and it pins the repo: every hook targets that workspace regardless of what the CLI is pointed at elsewhere.
33
+
33
34
  `flmnt setup` writes a project-local `.mcp.json` pointing at the local proxy plus a `.claude/` hook map and slash commands; `flmnt proxy` then injects your bearer token on outbound MCP requests — so Claude Code talks to a live, authenticated flmnt MCP without you handling tokens by hand. `setup` is idempotent.
34
35
 
36
+ ### Which workspace a command uses
37
+
38
+ `brief`, `derive`, `gate` and `record-*` resolve the project in this order, first match wins:
39
+
40
+ 1. an explicit `--project <name|id>` on the command
41
+ 2. `project_id` in the repo's `.quorum.json` — written by `flmnt setup --project`
42
+ 3. the active workspace (`flmnt workspace use`)
43
+
44
+ Step 3 is a fallback of last resort, not the norm: a repo that reaches it has no identity of its own, so a per-machine setting decides where its memory goes. `flmnt workspace use` remains a convenience for ad-hoc commands and does not decide where a configured repo records.
45
+
35
46
  ## Commands
36
47
 
37
48
  ```sh
@@ -41,7 +52,7 @@ flmnt <command> -h # detailed help for a command
41
52
  # Authentication
42
53
  flmnt login # authenticate via OAuth2 (browser PKCE, or --device for headless)
43
54
  flmnt logout # sign out and revoke local credentials
44
- flmnt whoami # show the active identity and workspace
55
+ flmnt whoami # show your identity and which workspace is in force here
45
56
 
46
57
  # Workspaces
47
58
  flmnt workspace list # list workspaces you own or are a member of
@@ -52,7 +63,9 @@ flmnt workspace add-member # add a member to a workspace you own
52
63
  flmnt workspace remove-member # remove a member from a workspace you own
53
64
 
54
65
  # MCP / Claude Code integration
55
- flmnt setup --server-url <url> # install the automation kit: .mcp.json + lifecycle hooks
66
+ flmnt setup --server-url <url> --project <name|id>
67
+ # install the automation kit: .mcp.json + lifecycle hooks
68
+ # --project is REQUIRED and pins THIS repo to that workspace
56
69
  # + .claude/commands/flmnt-* slash commands (idempotent)
57
70
  flmnt proxy # run the local MCP proxy (injects Authorization: Bearer)
58
71
  flmnt mcp auth-header # print MCP auth headers as JSON for .mcp.json
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "@mmmnt/flmnt",
3
- "version": "1.10.0",
3
+ "version": "1.10.2",
4
4
  "description": "flmnt CLI — installs the platform-native flmnt binary.",
5
5
  "type": "module",
6
6
  "license": "Apache-2.0",