@dypt/cli 0.1.17 → 0.1.19
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 +73 -0
- package/dist/index.js +330 -75
- package/dist/index.js.map +1 -1
- package/package.json +1 -1
package/README.md
CHANGED
|
@@ -83,12 +83,32 @@ Change status, priority, due date, archive state, or parent:
|
|
|
83
83
|
dypt task update 123 --status "in progress"
|
|
84
84
|
dypt task update 123 --priority high
|
|
85
85
|
dypt task update 123 --deadline 2026-05-01T09:00:00Z
|
|
86
|
+
dypt task update 123 --clear-deadline --preview
|
|
87
|
+
dypt task update 123 --clear-deadline
|
|
86
88
|
dypt task update 123 --parent Work
|
|
87
89
|
dypt task update 123 --parent root --preview
|
|
88
90
|
dypt task update 123 --position 0
|
|
89
91
|
dypt task update 123 --archive
|
|
90
92
|
```
|
|
91
93
|
|
|
94
|
+
`dypt task update-many` (including `--preview`) accepts at most 100 task IDs
|
|
95
|
+
per request, including repeated IDs. Apply commits the whole request and its
|
|
96
|
+
sync history atomically: if any task or journal write fails, no part of that
|
|
97
|
+
request is committed. Split larger updates into explicit batches; separate
|
|
98
|
+
requests are not one transaction. A lost response is still an uncertain
|
|
99
|
+
outcome—inspect the tasks before retrying.
|
|
100
|
+
|
|
101
|
+
Use `--clear-deadline` to remove an existing deadline. It can be previewed for
|
|
102
|
+
single or bulk updates:
|
|
103
|
+
|
|
104
|
+
```bash
|
|
105
|
+
dypt task update-many 123 456 --clear-deadline --preview
|
|
106
|
+
dypt task update-many 123 456 --clear-deadline
|
|
107
|
+
```
|
|
108
|
+
|
|
109
|
+
`--deadline` and `--clear-deadline` are mutually exclusive. Omitting both
|
|
110
|
+
leaves the current deadline unchanged.
|
|
111
|
+
|
|
92
112
|
### Reorder tasks
|
|
93
113
|
|
|
94
114
|
Set visible sibling order from an explicit task list. Preview first for safe
|
|
@@ -103,6 +123,14 @@ dypt task reorder 71595 71594 71598 --parent Work
|
|
|
103
123
|
Dependencies and blockers are not changed by reordering; use `dypt dep` commands
|
|
104
124
|
for execution dependencies.
|
|
105
125
|
|
|
126
|
+
Reorder and its preview accept at most 100 submitted IDs and require the
|
|
127
|
+
**complete sibling set**, including omitted and archived siblings, to contain
|
|
128
|
+
at most 100 tasks. Selected tasks come first; omitted siblings keep their
|
|
129
|
+
relative order afterwards. Larger sibling sets are rejected with
|
|
130
|
+
`CLI_BULK_TASK_LIMIT_EXCEEDED` before writes, not truncated or automatically
|
|
131
|
+
chunked (chunking would change the meaning of the reorder). Reorder writes and
|
|
132
|
+
sync history commit atomically, using the same rollback contract as bulk updates.
|
|
133
|
+
|
|
106
134
|
### Manage reminders
|
|
107
135
|
|
|
108
136
|
Configure up to three reminders relative to a task's deadline:
|
|
@@ -173,6 +201,51 @@ dypt task list --limit 10 --json
|
|
|
173
201
|
dypt task get 123 --json
|
|
174
202
|
```
|
|
175
203
|
|
|
204
|
+
### Maintenance responses
|
|
205
|
+
|
|
206
|
+
If dypt is in maintenance mode, API-backed commands stop after the first `503`
|
|
207
|
+
response and exit with code `75` (`EX_TEMPFAIL`). Mutations are never retried
|
|
208
|
+
automatically. Human output explains that no change was applied and includes
|
|
209
|
+
the server's `Retry-After` guidance when available.
|
|
210
|
+
|
|
211
|
+
The canonical server response combines HTTP `503`,
|
|
212
|
+
`X-Dypt-Maintenance: true`, `Retry-After`, and the stable
|
|
213
|
+
`DYPT_MAINTENANCE` response code. The CLI also normalizes an accidental HTML
|
|
214
|
+
`503` from a break-glass rewrite instead of reporting a JSON parse failure.
|
|
215
|
+
|
|
216
|
+
Commands invoked with `--json` write this stable retryable classification to
|
|
217
|
+
standard error and also exit `75`:
|
|
218
|
+
|
|
219
|
+
```json
|
|
220
|
+
{
|
|
221
|
+
"error": {
|
|
222
|
+
"code": "DYPT_MAINTENANCE",
|
|
223
|
+
"message": "dypt is temporarily under maintenance.",
|
|
224
|
+
"retryable": true,
|
|
225
|
+
"retryAfter": "120",
|
|
226
|
+
"retryAfterSeconds": 120,
|
|
227
|
+
"noChangeApplied": true
|
|
228
|
+
}
|
|
229
|
+
}
|
|
230
|
+
```
|
|
231
|
+
|
|
232
|
+
Agents may retry after the indicated delay. They should not revoke credentials,
|
|
233
|
+
start a new login flow, or assume that an interrupted mutation was applied.
|
|
234
|
+
|
|
235
|
+
### Read-query throttling
|
|
236
|
+
|
|
237
|
+
Authenticated reads use an account-level weighted budget that is shared across
|
|
238
|
+
all CLI tokens. Normal pagination and agent inspection workflows fit within the
|
|
239
|
+
budget, while sustained task list, tree, search, summary, and planning traffic
|
|
240
|
+
consumes it faster than bounded point reads.
|
|
241
|
+
|
|
242
|
+
When the server returns `CLI_READ_RATE_LIMITED`, wait at least the reported
|
|
243
|
+
`retryAfterSeconds`, add backoff or jitter, and continue from the last cursor.
|
|
244
|
+
Rotating credentials does not increase capacity. The CLI exits with temporary
|
|
245
|
+
failure code `75`; `--json` emits a stable retryable error object. Read
|
|
246
|
+
throttling is independent of mutation throttling and per-request filter/input
|
|
247
|
+
bounds.
|
|
248
|
+
|
|
176
249
|
## Agent guidance
|
|
177
250
|
|
|
178
251
|
Install or inspect dypt agent guidance for supported AI coding tools:
|