@conto_finance/create-conto-agent 0.9.0 → 0.10.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/CHANGELOG.md +45 -0
- package/README.md +18 -1
- package/dist/{chunk-FW6E3QMB.js → chunk-ALQ6UCGI.js} +799 -119
- package/dist/cli.js +93 -25
- package/dist/index.js +36 -3
- package/package.json +1 -1
package/CHANGELOG.md
CHANGED
|
@@ -1,5 +1,50 @@
|
|
|
1
1
|
# Changelog
|
|
2
2
|
|
|
3
|
+
## 0.10.0
|
|
4
|
+
|
|
5
|
+
- `create-conto-agent --connect` sets an agent up in a person's real Conto account without a
|
|
6
|
+
browser on the agent's computer. It prints a link and a code. The person opens the link, signs up
|
|
7
|
+
or signs in, checks the code and approves. With `--email you@example.com`, Conto emails the link.
|
|
8
|
+
`--wait` waits for the approval and saves the agent key (`conto_agent_`, never an organization
|
|
9
|
+
key) to the project's `.env.local`. Without `--wait` it returns right away and keeps the request
|
|
10
|
+
in `.conto/setup-request.json`, so a second run with `--wait` picks it up. From a sandbox project,
|
|
11
|
+
approval also copies the sandbox's policies to the new agent. `conto init --connect` and
|
|
12
|
+
`conto init --email` do the same. Exit codes: 0 approved or waiting, 1 failed or expired,
|
|
13
|
+
2 declined or refused, 4 still waiting when `--wait` ran out of time.
|
|
14
|
+
- `create-conto-agent --sandbox` no longer replaces a login saved in `~/.conto/config.json`. The
|
|
15
|
+
sandbox runs from the project's `.env.local` as before. The `--json` result has
|
|
16
|
+
`savedLoginKept: true` when the saved login was kept.
|
|
17
|
+
- The `--json` next steps use the full package name, `npx @conto_finance/create-conto-agent`, which
|
|
18
|
+
works from any folder. They also include the line that adds Conto to Claude Code:
|
|
19
|
+
`claude mcp add conto -- npx -y @conto_finance/create-conto-agent mcp`. The printed next steps
|
|
20
|
+
show the same line in place of `conto mcp`, which only starts the server.
|
|
21
|
+
|
|
22
|
+
## 0.9.1
|
|
23
|
+
|
|
24
|
+
- `conto login` and the `conto init` sign-in now collect the organization key from Conto instead
|
|
25
|
+
of waiting for the browser to send it to the CLI. Current Chrome can hold that send behind a
|
|
26
|
+
local network permission, so the page spun on "Connecting to CLI..." and the login timed out.
|
|
27
|
+
The CLI prints a code, and the browser shows the same one next to Connect CLI. Older Conto
|
|
28
|
+
servers still send the key from the browser, and the CLI accepts it as before.
|
|
29
|
+
- `conto alerts` works again. Without `--json` it failed as soon as an alert existed, and `--unread`
|
|
30
|
+
and `--active` always failed with "Invalid status filter". The table now shows each alert's ID,
|
|
31
|
+
date, severity, status, and title, and `--unread` and `--active` list open alerts.
|
|
32
|
+
- `conto config` no longer changes `server.baseUrl`, because the saved keys would go to the new
|
|
33
|
+
server. It tells you to run `conto login --base-url <url>`, which signs in to that server and
|
|
34
|
+
removes the agent key saved for the old one.
|
|
35
|
+
- Setup with `--api-key` or `CONTO_ORG_API_KEY` uses that organization key for the run and no longer
|
|
36
|
+
saves it in `~/.conto/config.json`, where other projects of the same organization on the machine
|
|
37
|
+
would use it. In a terminal, setup asks first, and the default is No. The output says when the key
|
|
38
|
+
was not saved, and the `--json` result has `credentials.orgApiKeySaved`. A key from the browser
|
|
39
|
+
sign-in or `conto login` is saved as before, and setup keeps one already saved for the same server.
|
|
40
|
+
- `--json` runs never prompt, even in a terminal. Setup uses the headless defaults for flags you
|
|
41
|
+
leave out and needs `--api-key`, `CONTO_ORG_API_KEY`, or `--sandbox`. `conto policies create`,
|
|
42
|
+
`update`, `delete`, and `add-rule` prompt for input, so under `--json` they now stop with an error.
|
|
43
|
+
- `conto agents unfreeze` no longer asks Conto to keep the agent's wallets frozen unless you pass
|
|
44
|
+
`--wallets`. With neither flag, Conto unfreezes the wallets the agent's freeze froze, leaving any
|
|
45
|
+
wallet a person froze or another frozen agent still holds. `--wallets` also does it for a freeze
|
|
46
|
+
recorded before Conto kept that list, and the new `--keep-wallets` leaves every wallet frozen.
|
|
47
|
+
|
|
3
48
|
## 0.9.0
|
|
4
49
|
|
|
5
50
|
- `conto pay --json` now exits 1 when a policy denies the payment, as it already did without
|
package/README.md
CHANGED
|
@@ -24,7 +24,9 @@ See [configure controls](https://conto.finance/docs/quickstart/agent-sandbox#con
|
|
|
24
24
|
|
|
25
25
|
Run the wizard without `--sandbox` to sign in and provision a managed wallet. Choose Tempo
|
|
26
26
|
Testnet for free faucet tokens and actual onchain test transfers. For headless organization
|
|
27
|
-
setup, set `CONTO_ORG_API_KEY` or pass `--api-key`.
|
|
27
|
+
setup, set `CONTO_ORG_API_KEY` or pass `--api-key`. Setup uses that key for the run and does not
|
|
28
|
+
save it in `~/.conto/config.json` unless you agree when it asks in a terminal. A `--json` run never
|
|
29
|
+
prompts.
|
|
28
30
|
|
|
29
31
|
A mainnet setup asks you to confirm the network (pass `--confirm-mainnet` when headless) and
|
|
30
32
|
creates the agent in the `PROD` environment, because only `PROD` agents can pay from mainnet
|
|
@@ -64,6 +66,21 @@ Setup keeps the other lines in an existing `.env.local` and replaces only its `C
|
|
|
64
66
|
before replacing an existing `conto.config.json` or `example.mjs`. A headless run keeps them unless
|
|
65
67
|
you pass `--overwrite`.
|
|
66
68
|
|
|
69
|
+
## Connect to a person's account
|
|
70
|
+
|
|
71
|
+
```bash
|
|
72
|
+
npx @conto_finance/create-conto-agent --connect --email owner@example.com --json
|
|
73
|
+
npx @conto_finance/create-conto-agent --connect --wait --json
|
|
74
|
+
```
|
|
75
|
+
|
|
76
|
+
`--connect` sets the agent up in a person's real Conto account without a browser on the agent's
|
|
77
|
+
computer. The first run prints a link and a code, and with `--email` Conto emails the link. The
|
|
78
|
+
person opens it, signs up or signs in, checks the code and approves. `--wait` waits for the approval
|
|
79
|
+
and saves the agent key to the project's `.env.local`. From a sandbox project, approval also copies
|
|
80
|
+
the sandbox's policies. Exit codes: 0 approved or the link is out, 1 failed or expired, 2 declined
|
|
81
|
+
or refused, 4 still waiting. See
|
|
82
|
+
[connect to a person's account](https://conto.finance/docs/cli/commands#connect-to-a-persons-account).
|
|
83
|
+
|
|
67
84
|
## Hand a sandbox to its owner
|
|
68
85
|
|
|
69
86
|
```bash
|