ente-cli 0.4.100 → 0.4.101

package/README.md

@@ -92,12 +92,46 @@ fallback. CLI pairing without `--agent`
 creates a named connection agent. MCP authorization creates a connection agent
 named for the client.
 
-Named profiles are optional. Use one only when a person or process deliberately
-switches between several credentials. `--profile` overrides `ENTE_PROFILE`.
-Profiles do not activate from the current directory and are not a security
-boundary. Use a separate OS account or container when operators on the same
-machine must not read each other's keys. Never commit a key or put it in a
-project `.env` file.
+Named profiles are optional when one global default is sufficient.
+Profile selection uses `--profile`, then `ENTE_PROFILE`, then the nearest bound
+ancestor of the current directory, then the global `config.toml` default.
+Folder bindings are machine-local in the Ente config directory's `bindings.json`;
+no repository file selects an identity. Paths resolve symlinks before matching.
+A selected missing profile fails instead of falling back to another identity.
+Complete `ENTE_API_URL` / `ENTE_API_KEY` overrides still replace file credentials;
+partial overrides fail closed. `auth status` reports credential source separately
+from `profileSource` and `boundDirectory`.
+
+```bash
+ente auth bind /absolute/operator/folder operator-name
+ente auth bindings --json
+ente auth status --profile operator-name --json
+ente auth unbind /absolute/operator/folder
+```
+
+Bind an existing authenticated profile. Nested bindings override their parents.
+Platform administration credentials stay separate and ignore folder bindings.
+Bindings are defaults, not a security boundary. Use a separate OS account or
+container when operators must not read each other's keys. Never commit a key
+or put it in a project `.env` file.
+
+Inspect the selected credential before work:
+
+```bash
+ente auth whoami --json
+ente agent permissions --json
+ente agent permissions --check "Work" --action write --json
+```
+
+`whoami` reports the selected profile and its resolution `source`, the agent ID,
+name, icon, mailbox, active state, home space, and live scopes. The permission
+list includes account-visible spaces denied to the key, with `access` of `none`,
+`read`, or `write`, and server-derived `canRead`/`canWrite` flags. Scopes and OAuth
+consent can restrict those flags independently. Account panel visibility is
+separate from operational access. `--check` accepts an exact space name or ID
+and `--action read|write`; denial exits nonzero and names the web app's
+**Agent actions** and Connections scope settings. These commands never grant
+rights, invoke a provider, or print keys.
 
 ## Usage
 
@@ -142,7 +176,7 @@ Every command supports `--json`. Run `ente --help` or `ente <group> --help`.
 
 | Group | Commands |
 |---|---|
-| `auth` | `pair`, `login`, `status`, `logout`, `profiles` |
+| `auth` | `pair`, `login`, `status`, `whoami`, `logout`, `profiles`, `bind`, `unbind`, `bindings` |
 | `entity` | `list`, `create`, `get`, `update` (`--name`, `--tag`, `--description`), `rename`, `archive`, `restore` (`--share-parents` plus the returned grant fingerprint), `pin` (`--role`, optional confirmed parent grants), `unpin`, `add-to-space`, `remove-from-space` (`--remove-from-activities` optional) |
 | `activity` | `list`, `create`, `search`, `get`, `transcript` (`--grep`, `--context`), `update`, `delete`, `restore`, `message add`, `attachment upload` |
 | `agenda` | `create-point`, `link-task` |
@@ -155,7 +189,7 @@ Every command supports `--json`. Run `ente --help` or `ente <group> --help`.
 | `canvas` | `boards`, `html list`, `html get`, `html create`, `html update`, `html delete` |
 | `files` | `list`, `upload` (local file at most 10 MiB, or an activity attachment), `link`, `create-folder` — the entity's Nextcloud folder via your own connection; personal agent key only (MCP: `entity_files_list`, `entity_file_upload`, `entity_folder_link`, `entity_folder_create`) |
 | `notification` | `send` (emails only your own Ente account address; optional HTML, file attachments, and CID inline images) |
-| `agent` | `list`, `threads`, `show`, `new`, `send`, `config show`, `config set-prompt`, `schedules configure` |
+| `agent` | `permissions`, `list`, `threads`, `show`, `new`, `send`, `config show`, `config set-prompt`, `schedules configure` |
 | `agent mail` | `address`, `threads`, `show`, `send`, `reply`, `mark` |
 | top-level | `search`, `ask`, `query`, `tasks`, `guide` |
 

package/dist/SKILL.md

@@ -68,12 +68,43 @@ including cached JWT calls. There is no unrestricted user-key fallback. Create
 and manage keys from the agent’s Connections settings in `/agents`; several
 credentials can belong to the same agent.
 
-Named profiles are optional and only needed to switch deliberately between
-credentials. `--profile` overrides `ENTE_PROFILE`. Profiles do not activate
-from the current directory and do not isolate secrets from other processes
-running as the same operating-system user. Use a separate OS account or
-container when that isolation matters. Never store a key in the repository or
-a project `.env` file.
+Named profiles are optional when one global default is sufficient.
+Resolve the profile in this order: `--profile`, `ENTE_PROFILE`, the nearest
+bound canonical ancestor of the current directory, then the global default.
+Machine-local `bindings.json` in the Ente config directory stores folder bindings;
+repositories carry no binding file. Symlinked folders resolve to their real path.
+A selected missing profile fails closed. Complete API URL/key environment overrides
+still replace stored credentials; check these separately from profile selection.
+`auth status --json` reports `profileSource` and `boundDirectory` separately from
+credential `source`. Bind only an existing authenticated profile:
+
+```bash
+ente auth bind /absolute/operator/folder operator-name
+ente auth bindings --json
+ente auth unbind /absolute/operator/folder
+```
+
+Bindings do not isolate secrets from other processes under the same OS user.
+Use separate OS accounts or containers for that isolation. Platform keys ignore
+folder bindings. Never store a key in a repository or project `.env` file.
+
+Inspect the selected credential before work:
+
+```bash
+ente auth whoami --json
+ente agent permissions --json
+ente agent permissions --check "Work" --action write --json
+```
+
+`whoami` reports the selected profile and its resolution `source`, the agent ID,
+name, icon, mailbox, active state, home space, and live scopes. The permission
+list includes account-visible spaces denied to the key, with `access` of `none`,
+`read`, or `write`, and server-derived `canRead`/`canWrite` flags. Scopes and OAuth
+consent can restrict those flags independently. Account panel visibility is
+separate from operational access. `--check` accepts an exact space name or ID
+and `--action read|write`; denial exits nonzero and names the web app's
+**Agent actions** and Connections scope settings. These commands never grant
+rights, invoke a provider, or print keys.
 
 Verify server access with `ente entity list --limit 1 --json`.
 
@@ -150,6 +181,9 @@ ente auth login --url <convex-site-url> --key-stdin
 ente auth status
 ente auth logout
 ente auth profiles
+ente auth bind <path> <profile>
+ente auth unbind <path>
+ente auth bindings [--json]
 
 # Search & ask
 # Ask is an experimental opt-in beta, not a general AI chat or included-model execution API.