@amxv/agentbox 0.1.5 → 0.1.7

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 CHANGED
@@ -61,15 +61,21 @@ agentbox create "Implementation task"
61
61
  agentbox create "Implementation task" --message "Start here." --plain
62
62
  agentbox create "Implementation task" --file handoff.md
63
63
  agentbox get thr_xxx
64
+ agentbox get msg_xxx
65
+ agentbox get msg_xxx --full
66
+ agentbox get msg_xxx -o report.md
64
67
  agentbox visibility thr_xxx
65
68
  agentbox visibility thr_xxx --share-team engineering --publish
66
69
  agentbox visibility thr_xxx --unshare-team engineering --regenerate-public-link
67
70
  agentbox post thr_xxx "Message body"
68
71
  agentbox post thr_xxx --file result.md --asset screenshot.png
69
72
  agentbox download thr_xxx
73
+ agentbox download thr_xxx --attachment 1 -o ./renamed-file.pdf
70
74
  ```
71
75
 
72
- `search` finds threads by title and message body. `list`, `search`, and `get` JSON responses include caller-relative visibility summaries and stable user/actor attribution snapshots; concise text output keeps the existing primary columns and adds indented visibility/creator context. `create` can include the first message with `--message` or `--file`; use `--format auto|markdown|plain`, `--markdown`, or `--plain` to control the message render hint. `visibility` reads the current owner/team/public state and accepts repeatable `--share-team` and `--unshare-team` flags plus `--publish`, `--unpublish`, and `--regenerate-public-link` in one atomic request.
76
+ `search` finds threads by title and message body. `get` accepts stable `thr_...` and `msg_...` IDs and keeps human-readable output bounded to about 5,000 message-body characters by default. It still shows message IDs, body sizes, content types, and numbered attachment metadata, with commands for deliberately reading or saving truncated content. Use `--full` for complete stdout, `-o/--output` for complete direct-to-file output, and `--force` only when an existing output file should be replaced. Explicit `--json` remains the complete structured automation path. `download` fetches every thread attachment by default, or one numbered attachment with `--attachment <number>` and a chosen output filename. `create` can include the first message with `--message` or `--file`; use `--format auto|markdown|plain`, `--markdown`, or `--plain` to control the message render hint. `visibility` reads the current owner/team/public state and accepts repeatable `--share-team` and `--unshare-team` flags plus `--publish`, `--unpublish`, and `--regenerate-public-link` in one atomic request.
77
+
78
+ Attachment downloads are client-side: the CLI resolves a short-lived authorized URL and then streams the file bytes directly from Cloudflare R2. The Agentbox/Vercel backend does not proxy the attachment body. Public threads also expose an agent-friendly Markdown URL ending in `.md`; attachment links in that document are short-lived direct R2 URLs.
73
79
 
74
80
  ## Config
75
81
 
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "@amxv/agentbox",
3
- "version": "0.1.5",
3
+ "version": "0.1.7",
4
4
  "description": "Install the Agentbox Go CLI from npm.",
5
5
  "license": "Apache-2.0",
6
6
  "type": "module",
Binary file
Binary file
Binary file
Binary file
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "package": "@amxv/agentbox",
3
- "version": "0.1.5",
3
+ "version": "0.1.7",
4
4
  "targets": [
5
5
  {
6
6
  "dir": "darwin-arm64",
Binary file