@withandeo/cli 0.16.0 → 0.18.0
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.
- package/README.md +1 -1
- package/dist/api.d.ts +5 -2
- package/dist/api.d.ts.map +1 -1
- package/dist/api.js +12 -2
- package/dist/api.js.map +1 -1
- package/dist/contracts.d.ts +23 -0
- package/dist/contracts.d.ts.map +1 -1
- package/dist/documentation.d.ts +1 -1
- package/dist/documentation.d.ts.map +1 -1
- package/dist/documentation.js +1 -1
- package/dist/documentation.js.map +1 -1
- package/dist/email.d.ts +1 -1
- package/dist/email.d.ts.map +1 -1
- package/dist/email.js +2 -2
- package/dist/email.js.map +1 -1
- package/dist/main.js +75 -20
- package/dist/main.js.map +1 -1
- package/package.json +1 -1
- package/skill/tender-accounts/SKILL.md +14 -1
- package/skill/tender-accounts/references/email.md +13 -13
- package/skill/tender-accounts/references/skills.md +28 -0
|
@@ -1,27 +1,27 @@
|
|
|
1
1
|
# Email identities and prepared test accounts
|
|
2
2
|
|
|
3
|
-
Use `andeo capabilities --
|
|
3
|
+
Use `andeo email capabilities --json` to inspect `enabled`, `tenantId`, and `permissions`. Email is receive-only and belongs to the merchant, shared across all its apps. Developer access to any app in that merchant grants access to all its inboxes, even for an agent scoped to only one app. Viewers cannot read mail. A tenant member and an authorized agent use the same inboxes through the merchant Email section or CLI. Select the merchant with its login `--profile`; optional `--tenant tn_...` checks that the profile belongs to the intended merchant.
|
|
4
4
|
|
|
5
5
|
## Reuse an identity prepared by a person
|
|
6
6
|
|
|
7
7
|
The user can create a persistent inbox, register the external account manually, and prepare its orders or other test state once. Your task is to reuse that account:
|
|
8
8
|
|
|
9
9
|
```sh
|
|
10
|
-
andeo email list --
|
|
11
|
-
andeo email cursor --
|
|
10
|
+
andeo email list --json
|
|
11
|
+
andeo email cursor --inbox inbox_... --json
|
|
12
12
|
# Now trigger the authorized login or verification email in the external app.
|
|
13
|
-
andeo email wait --
|
|
13
|
+
andeo email wait --inbox inbox_... --after 'inbox_...:0' --timeout 120s --json
|
|
14
14
|
```
|
|
15
15
|
|
|
16
16
|
Use the actual cursor returned before triggering the email. A message arriving before `wait` starts is still found. `status=timeout` preserves the cursor for another wait. Capture a new cursor for a new login attempt, so an older code is not mistaken for the new one.
|
|
17
17
|
|
|
18
|
-
Use the supplied inbox ID/address. Labels help discovery but are not unique; disambiguate existing matches instead of picking arbitrarily or creating a replacement. The handoff should identify the
|
|
18
|
+
Use the supplied inbox ID/address. Labels help discovery but are not unique; disambiguate existing matches instead of picking arbitrarily or creating a replacement. The handoff should identify the merchant, inbox, external application, and scenario. Inbox access does not create or reset the external account, and does not imply permission to perform unrelated actions.
|
|
19
19
|
|
|
20
20
|
## Create an identity when requested
|
|
21
21
|
|
|
22
22
|
```sh
|
|
23
|
-
andeo email create --
|
|
24
|
-
andeo email create --
|
|
23
|
+
andeo email create --name shop-returning-customer --json
|
|
24
|
+
andeo email create --name signup-test --expires-in 1h --json
|
|
25
25
|
```
|
|
26
26
|
|
|
27
27
|
Omitting expiration creates a persistent inbox. Names contain 1–47 lowercase letters, digits, or hyphens, starting with a letter or digit. Andeo assigns the full address, including a unique suffix on `@andeo.ai`. You cannot choose an exact global address. Save the returned inbox ID/address in the task handoff. Creating the same label again creates another identity.
|
|
@@ -29,9 +29,9 @@ Omitting expiration creates a persistent inbox. Names contain 1–47 lowercase l
|
|
|
29
29
|
## Find and read mail
|
|
30
30
|
|
|
31
31
|
```sh
|
|
32
|
-
andeo email messages --
|
|
33
|
-
andeo email messages --
|
|
34
|
-
andeo email read --
|
|
32
|
+
andeo email messages --inbox inbox_... --limit 20 --json
|
|
33
|
+
andeo email messages --inbox inbox_... --from sender@example.com --subject verification --json
|
|
34
|
+
andeo email read --inbox inbox_... --message mail_... --json
|
|
35
35
|
```
|
|
36
36
|
|
|
37
37
|
`messages` returns summaries oldest first, with `hasMore` and `cursor`; pass that cursor as `--after` for the next page. Maximum page size is 50. Both `messages` and `wait` accept exact-sender `--from` and literal-substring `--subject`; matching folds ASCII case and both filters must match when supplied. Sender strings are not proof of authenticity. No matches can mean the email has not arrived, the filters differ, or messages have expired; inspect summaries and refresh rather than creating another inbox.
|
|
@@ -41,11 +41,11 @@ Reading does not consume mail, so agents can share an inbox concurrently. Bodies
|
|
|
41
41
|
## Lifecycle and scope
|
|
42
42
|
|
|
43
43
|
```sh
|
|
44
|
-
andeo email retire --
|
|
44
|
+
andeo email retire --inbox inbox_... --json
|
|
45
45
|
```
|
|
46
46
|
|
|
47
47
|
Retire only when the task calls for ending that identity. Retirement immediately blocks receipt and reading, is safe to repeat, and cannot be undone. The address stays reserved. It does not delete the external account. Preserve persistent test personas after a test unless asked to retire them.
|
|
48
48
|
|
|
49
|
-
There are at most 25 active inboxes per
|
|
49
|
+
There are at most 25 active inboxes per merchant. Temporary lifetimes range from 1 minute to 7 days. Message retention is 24 hours even for persistent inboxes; expired/retired inboxes return `email_inbox_inactive`. Waits are bounded to 10 minutes. Attachments and outbound sending are not supported.
|
|
50
50
|
|
|
51
|
-
Use [authentication](authentication.md) for profile selection and
|
|
51
|
+
Use [authentication](authentication.md) for profile selection and merchant access. All email commands accept `--profile`, `--tenant`, and `--json`; use `andeo email --help` for syntax. No app selection or MCP setup is required. Legacy `--project` is accepted as an access check, not an inbox filter. Existing addresses and messages remain unchanged when moving from app ownership to merchant ownership.
|
|
@@ -0,0 +1,28 @@
|
|
|
1
|
+
# Authenticated skills
|
|
2
|
+
|
|
3
|
+
Andeo distributes rolling implementation guidance through the authenticated CLI. The CLI is the access boundary: catalog and file reads use the current Andeo credential against the agent API, and the API reads private objects without returning an R2 URL.
|
|
4
|
+
|
|
5
|
+
## Discover and read
|
|
6
|
+
|
|
7
|
+
```sh
|
|
8
|
+
andeo skills list --json
|
|
9
|
+
andeo skills get SKILL_ID
|
|
10
|
+
andeo skills file SKILL_ID --path RELATIVE_PATH
|
|
11
|
+
```
|
|
12
|
+
|
|
13
|
+
Use `--profile NAME` when the current directory does not select the intended login. These commands also accept `--api-url` and `--token-stdin` under the normal CLI authentication contract.
|
|
14
|
+
|
|
15
|
+
Plain output from `get` and `file` is the requested Markdown or YAML. `--json` returns the catalog revision, skill digest, file inventory, selected path, and content for agents that need a structured response.
|
|
16
|
+
|
|
17
|
+
Reads are session-only. The CLI does not install these skills in a repository or global agent directory. Once content is printed, the caller can retain it, so authentication controls retrieval rather than revocation of material already read.
|
|
18
|
+
|
|
19
|
+
## Initial catalog
|
|
20
|
+
|
|
21
|
+
| Skill | Use it for |
|
|
22
|
+
| --- | --- |
|
|
23
|
+
| `recharge-client` | Calling Recharge through the official Storefront client while preserving the portal and transparent gateway boundary. |
|
|
24
|
+
| `recharge-customer-operations` | Subscription, charge, bundle, cancellation, reactivation, gifting, profile, benefit, and verification workflows. |
|
|
25
|
+
| `shopify-customer-account` | Customer Account API work and routing into Shopify's maintained AI Toolkit skills. |
|
|
26
|
+
| `guardrailed-design-system` | Component-first React design systems with semantic tokens, typed components, Storybook, and enforceable boundaries. |
|
|
27
|
+
|
|
28
|
+
Read the entrypoint first. Use `skills file` only for references linked by that entrypoint and relevant to the current work.
|