@rehpic/vcli 0.1.0-beta.10.1

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 ADDED
@@ -0,0 +1,200 @@
1
+ # Vector CLI
2
+
3
+ CLI for interacting with a Vector workspace from the terminal.
4
+
5
+ This package wraps the same auth and Convex-backed workflows used by the app, so you can manage orgs, roles, teams, projects, issues, documents, notifications, and admin settings without opening the UI.
6
+
7
+ ## Install
8
+
9
+ ```bash
10
+ npm install -g @rehpic/vcli
11
+ yarn global add @rehpic/vcli
12
+ pnpm add -g @rehpic/vcli
13
+ bun add -g @rehpic/vcli
14
+ ```
15
+
16
+ Then verify the install:
17
+
18
+ ```bash
19
+ vcli --help
20
+ ```
21
+
22
+ ## Requirements
23
+
24
+ - Node.js `>=20.19.0`
25
+ - A running Vector app
26
+ - Access to the app's Convex deployment
27
+
28
+ The CLI talks to:
29
+
30
+ - the Next.js app for auth routes
31
+ - the Convex deployment for queries, mutations, and actions
32
+
33
+ The app URL is required. `vcli` resolves it from:
34
+
35
+ - `--app-url <url>`
36
+ - the saved profile session
37
+ - `NEXT_PUBLIC_APP_URL`
38
+
39
+ The Convex URL still defaults from:
40
+
41
+ - `NEXT_PUBLIC_CONVEX_URL` or `CONVEX_URL`
42
+
43
+ You can override either with flags:
44
+
45
+ ```bash
46
+ vcli --app-url http://localhost:3000 --convex-url https://<deployment>.convex.cloud --help
47
+ ```
48
+
49
+ ## First Run
50
+
51
+ Sign up or log in:
52
+
53
+ ```bash
54
+ vcli --app-url http://localhost:3000 auth signup --email you@example.com --username you --password 'secret'
55
+ vcli --app-url http://localhost:3000 auth login you@example.com --password 'secret'
56
+ vcli auth whoami
57
+ ```
58
+
59
+ Create and select an org:
60
+
61
+ ```bash
62
+ vcli org create --name "Acme" --slug acme
63
+ vcli org use acme
64
+ ```
65
+
66
+ From there, most commands can rely on the active org. You can always override it with `--org <slug>`.
67
+
68
+ ## Profiles
69
+
70
+ Sessions are stored per profile in:
71
+
72
+ ```text
73
+ ~/.vector/cli-<profile>.json
74
+ ```
75
+
76
+ Examples:
77
+
78
+ ```bash
79
+ vcli --profile work auth login you@example.com --password 'secret'
80
+ vcli --profile staging --app-url http://localhost:3001 auth whoami
81
+ ```
82
+
83
+ Use profiles when you work across multiple environments or accounts.
84
+
85
+ ## Common Commands
86
+
87
+ Inspect the current session:
88
+
89
+ ```bash
90
+ vcli auth whoami
91
+ vcli org current
92
+ vcli org members acme
93
+ ```
94
+
95
+ Discover workspace metadata before mutating:
96
+
97
+ ```bash
98
+ vcli refdata acme
99
+ vcli search --org acme "billing"
100
+ vcli permission check issue:create --org acme
101
+ ```
102
+
103
+ Create core entities:
104
+
105
+ ```bash
106
+ vcli team create --org acme --key eng --name "Engineering"
107
+ vcli project create --org acme --key api --name "API" --team eng
108
+ vcli issue create --org acme --title "Ship CLI" --project api --team eng
109
+ vcli document create --org acme --title "CLI Notes"
110
+ vcli folder create --org acme --name "Runbooks"
111
+ ```
112
+
113
+ Issue workflows:
114
+
115
+ ```bash
116
+ vcli issue list --org acme
117
+ vcli issue assignments API-1
118
+ vcli issue set-priority API-1 High
119
+ vcli issue replace-assignees API-1 "alice,bob"
120
+ vcli issue comment API-1 --body "Investigating now."
121
+ ```
122
+
123
+ Invites and notifications:
124
+
125
+ ```bash
126
+ vcli org invite acme --email teammate@example.com
127
+ vcli invite list
128
+ vcli invite accept <inviteId>
129
+ vcli notification inbox --filter unread
130
+ vcli notification unread-count
131
+ ```
132
+
133
+ Settings metadata:
134
+
135
+ ```bash
136
+ vcli priority list acme
137
+ vcli state list acme
138
+ vcli status list acme
139
+ vcli role list acme
140
+ ```
141
+
142
+ Platform admin:
143
+
144
+ ```bash
145
+ vcli admin branding
146
+ vcli admin signup-policy
147
+ ```
148
+
149
+ ## JSON Output
150
+
151
+ Use `--json` for automation and scripts:
152
+
153
+ ```bash
154
+ vcli --json issue list --org acme
155
+ vcli --json notification inbox --filter unread
156
+ ```
157
+
158
+ For scripts, prefer:
159
+
160
+ - `--json`
161
+ - `--profile`
162
+ - `--org`
163
+
164
+ ## Troubleshooting
165
+
166
+ `Not logged in`
167
+
168
+ - Run `vcli auth login` or `vcli auth signup`.
169
+
170
+ `app URL is required`
171
+
172
+ - Pass `--app-url <url>`, set `NEXT_PUBLIC_APP_URL`, or log in once with `--app-url` so the selected profile stores it.
173
+
174
+ `Organization slug is required`
175
+
176
+ - Pass `--org <slug>` or run `vcli org use <slug>`.
177
+
178
+ Auth errors against the wrong app
179
+
180
+ - Make sure `--app-url` points at the running Vector app origin.
181
+
182
+ Convex connection errors
183
+
184
+ - Set `--convex-url`, `NEXT_PUBLIC_CONVEX_URL`, or `CONVEX_URL`.
185
+
186
+ Validation errors when creating teams or projects
187
+
188
+ - Use short slug-like keys such as `eng`, `api`, or `mobile-platform`.
189
+
190
+ ## Help
191
+
192
+ Inspect command groups directly:
193
+
194
+ ```bash
195
+ vcli auth --help
196
+ vcli org --help
197
+ vcli issue --help
198
+ vcli notification --help
199
+ vcli admin --help
200
+ ```