@tryterra/cli-darwin-x64 0.2.0 → 0.4.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 +58 -5
- package/bin/terra +0 -0
- package/package.json +1 -1
package/README.md
CHANGED
|
@@ -1,7 +1,8 @@
|
|
|
1
1
|
# Terra CLI
|
|
2
2
|
|
|
3
|
-
 [![npm]](https://www.npmjs.com/package/@tryterra/cli) 
|
|
4
4
|
|
|
5
|
+
[Homebrew]: https://img.shields.io/badge/Homebrew-tryterra%2Ftap-orange?style=flat-square
|
|
5
6
|
[npm]: https://img.shields.io/npm/v/@tryterra/cli.svg?style=flat-square
|
|
6
7
|
|
|
7
8
|
Set up and debug your Terra integration from the terminal. Create environments
|
|
@@ -9,9 +10,8 @@ and credentials, turn providers on and off, see which users have connected, and
|
|
|
9
10
|
replay the webhook events your integration received. `terra data-api` reaches
|
|
10
11
|
the data API too, for the wearable data itself and the user-linking flow.
|
|
11
12
|
|
|
12
|
-
|
|
13
|
-
|
|
14
|
-
agent every command in a single call.
|
|
13
|
+
Your coding agent can drive it too, so you can ask for the result instead of
|
|
14
|
+
looking up the command. See [Let your agent drive it](#let-your-agent-drive-it).
|
|
15
15
|
|
|
16
16
|
## Get started
|
|
17
17
|
|
|
@@ -46,7 +46,15 @@ agent every command in a single call.
|
|
|
46
46
|
terra users list
|
|
47
47
|
```
|
|
48
48
|
|
|
49
|
-
4.
|
|
49
|
+
4. Ask a question when you are not sure:
|
|
50
|
+
|
|
51
|
+
```sh
|
|
52
|
+
terra ask "how do I generate an auth widget"
|
|
53
|
+
```
|
|
54
|
+
|
|
55
|
+
Answered from the documentation, with links to the pages it came from.
|
|
56
|
+
|
|
57
|
+
5. Find any other command:
|
|
50
58
|
|
|
51
59
|
```sh
|
|
52
60
|
terra reference
|
|
@@ -55,6 +63,51 @@ agent every command in a single call.
|
|
|
55
63
|
Every command and flag as one page. Name a group to narrow it:
|
|
56
64
|
`terra reference billing`.
|
|
57
65
|
|
|
66
|
+
## Let your agent drive it
|
|
67
|
+
|
|
68
|
+
Terra configuration usually means clicking around the dashboard, which your
|
|
69
|
+
agent cannot do. Give it the CLI instead. Paste this into Claude Code, Cursor,
|
|
70
|
+
Codex or whatever you use:
|
|
71
|
+
|
|
72
|
+
```text
|
|
73
|
+
Set up the Terra API CLI for this project. Install it with
|
|
74
|
+
"brew install tryterra/tap/terra" on macOS, or "npm install -g @tryterra/cli"
|
|
75
|
+
otherwise. Then run "terra agent setup" to install Terra's agent skills, read
|
|
76
|
+
the terra-cli skill it writes, and follow its getting-started section to tell
|
|
77
|
+
me what my account is configured to do.
|
|
78
|
+
```
|
|
79
|
+
|
|
80
|
+
That installs the skills into whichever agent is asking, so your agent then
|
|
81
|
+
knows the commands, the exit codes, and the traps worth avoiding. In a later
|
|
82
|
+
session, once it has picked the skills up, this is enough:
|
|
83
|
+
|
|
84
|
+
```text
|
|
85
|
+
Get started with Terra API.
|
|
86
|
+
```
|
|
87
|
+
|
|
88
|
+
It will check that the CLI is authenticated, find your environments, report
|
|
89
|
+
which wearable providers are on and where webhooks are going, and name the gap
|
|
90
|
+
that matters. Then ask for whatever you need:
|
|
91
|
+
|
|
92
|
+
```text
|
|
93
|
+
Which wearable providers are enabled in my dev environment, and where are its
|
|
94
|
+
webhooks going?
|
|
95
|
+
```
|
|
96
|
+
|
|
97
|
+
```text
|
|
98
|
+
A sleep webhook never arrived for user 8f2a1c. Find out what Terra actually
|
|
99
|
+
delivered, and resend it.
|
|
100
|
+
```
|
|
101
|
+
|
|
102
|
+
```text
|
|
103
|
+
Set up a staging environment with Garmin and Fitbit turned on, and point its
|
|
104
|
+
webhooks at my tunnel.
|
|
105
|
+
```
|
|
106
|
+
|
|
107
|
+
Asking questions is safe: reading changes nothing, credentials stay hidden
|
|
108
|
+
unless someone passes `--reveal`, and anything destructive refuses to run
|
|
109
|
+
unattended rather than guessing that you meant it.
|
|
110
|
+
|
|
58
111
|
## Before you change anything
|
|
59
112
|
|
|
60
113
|
Every command takes `--dry-run`, which prints the request that would be sent and
|
package/bin/terra
CHANGED
|
Binary file
|