@clickminded/coauthor-cli 0.0.4 → 0.0.6

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
@@ -131,8 +131,13 @@ coauthor research-plan generate <project-id> --json
131
131
  coauthor research run <project-id> --wait --json
132
132
  coauthor draft generate <project-id> --wait --json
133
133
  coauthor draft get <project-id> --format markdown --json
134
+ coauthor draft get <project-id> --format html --json
135
+ coauthor draft get <project-id> --format text --json
136
+ coauthor draft get <project-id> --format json --json
134
137
  ```
135
138
 
139
+ Draft exports resolve generated image URLs for Markdown, HTML, and text output when images are available. Use `--format json` or omit `--format` for the raw editor document JSON.
140
+
136
141
  Images and threads:
137
142
 
138
143
  ```sh
package/dist/commands.js CHANGED
@@ -664,6 +664,7 @@ export function helpResult() {
664
664
  ' research-plan show|generate|save|approve',
665
665
  ' research run|status|structured',
666
666
  ' draft generate|status|get|save',
667
+ ' draft get supports --format json|markdown|html|text',
667
668
  ' workflow show|status|advance|run|rewind|approve',
668
669
  ' workflow run/advance supports --briefing-mode auto|strict|off and --require-brief-review',
669
670
  ' image list|status|show|generate|edit',
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "@clickminded/coauthor-cli",
3
- "version": "0.0.4",
3
+ "version": "0.0.6",
4
4
  "type": "module",
5
5
  "bin": {
6
6
  "coauthor": "dist/index.js",
@@ -9,6 +9,8 @@ This skill guides agent use of the CoAuthor CLI.
9
9
 
10
10
  - Prefer `coauthor` CLI commands for CoAuthor project and workflow work.
11
11
  - Do not drive browser routes, hand-written `curl`, or direct database edits when a CLI command covers the task.
12
+ - Use the configured production base URL by default. Do not point the CLI at `localhost` or start a local dev server unless the user explicitly asks to test local changes.
13
+ - For local development only, pass an explicit one-off override such as `--base-url http://localhost:3000` or `COAUTHOR_BASE_URL=http://localhost:3000`.
12
14
  - Use `--json` for machine-readable output and parse fields from that output.
13
15
  - Use `--wait` for commands that start asynchronous work when the user expects the operation to finish.
14
16
  - Let the default bounded briefing review run before outline/draft generation. Use `--briefing-mode strict` when the user explicitly wants a stronger brief gate, and answer or relay `data.clarification_questions` if the CLI returns `status: "needs_clarification"`.
@@ -29,3 +31,13 @@ This skill guides agent use of the CoAuthor CLI.
29
31
  3. Add `--wait` when starting or advancing asynchronous work.
30
32
  4. If anything is uncertain, query operation status and report the current state.
31
33
  5. For live publish/export, confirm explicit user intent, then run with `--yes`.
34
+
35
+ ## Draft Export
36
+
37
+ Use `coauthor draft get <project-id> --format markdown --json` when the user needs a finished draft in Markdown. Generated images are resolved into Markdown image URLs when available.
38
+
39
+ Use `coauthor draft get <project-id> --format html --json` when the user needs HTML with resolved image tags.
40
+
41
+ Use `coauthor draft get <project-id> --format text --json` when the user needs plain text with image URL references.
42
+
43
+ Use `coauthor draft get <project-id> --format json --json` or omit `--format` when the user needs the raw editor document JSON.
@@ -9,6 +9,8 @@ This skill guides agent use of the CoAuthor CLI.
9
9
 
10
10
  - Prefer `coauthor` CLI commands for CoAuthor project and workflow work.
11
11
  - Do not drive browser routes, hand-written `curl`, or direct database edits when a CLI command covers the task.
12
+ - Use the configured production base URL by default. Do not point the CLI at `localhost` or start a local dev server unless the user explicitly asks to test local changes.
13
+ - For local development only, pass an explicit one-off override such as `--base-url http://localhost:3000` or `COAUTHOR_BASE_URL=http://localhost:3000`.
12
14
  - Use `--json` for machine-readable output and parse fields from that output.
13
15
  - Use `--wait` for commands that start asynchronous work when the user expects the operation to finish.
14
16
  - Let the default bounded briefing review run before outline/draft generation. Use `--briefing-mode strict` when the user explicitly wants a stronger brief gate, and answer or relay `data.clarification_questions` if the CLI returns `status: "needs_clarification"`.
@@ -29,3 +31,13 @@ This skill guides agent use of the CoAuthor CLI.
29
31
  3. Add `--wait` when starting or advancing asynchronous work.
30
32
  4. If anything is uncertain, query operation status and report the current state.
31
33
  5. For live publish/export, confirm explicit user intent, then run with `--yes`.
34
+
35
+ ## Draft Export
36
+
37
+ Use `coauthor draft get <project-id> --format markdown --json` when the user needs a finished draft in Markdown. Generated images are resolved into Markdown image URLs when available.
38
+
39
+ Use `coauthor draft get <project-id> --format html --json` when the user needs HTML with resolved image tags.
40
+
41
+ Use `coauthor draft get <project-id> --format text --json` when the user needs plain text with image URL references.
42
+
43
+ Use `coauthor draft get <project-id> --format json --json` or omit `--format` when the user needs the raw editor document JSON.
@@ -6,6 +6,8 @@ alwaysApply: true
6
6
  # CoAuthor CLI
7
7
 
8
8
  - Prefer the `coauthor` CLI for CoAuthor project/workflow operations instead of browser routes, hand-written `curl`, or direct database access.
9
+ - Use the configured production base URL by default. Do not point the CLI at `localhost` or start a local dev server unless the user explicitly asks to test local changes.
10
+ - For local development only, pass an explicit one-off override such as `--base-url http://localhost:3000` or `COAUTHOR_BASE_URL=http://localhost:3000`.
9
11
  - Use `--json` for agent-readable command output.
10
12
  - Use `--wait` when starting asynchronous work and the user expects a completed result.
11
13
  - Let the default bounded briefing review run before outline/draft generation. Use `--briefing-mode strict` for a stronger brief gate, and answer or relay `data.clarification_questions` if the CLI returns `status: "needs_clarification"`.
@@ -15,3 +17,10 @@ alwaysApply: true
15
17
  - Treat publish/export commands as live side effects.
16
18
  - Require explicit user intent before live publish/export.
17
19
  - Use `--yes` only after the user has clearly approved the live publish/export action.
20
+
21
+ ## Draft Export
22
+
23
+ - Use `coauthor draft get <project-id> --format markdown --json` for finished draft Markdown. Generated images resolve into Markdown image URLs when available.
24
+ - Use `coauthor draft get <project-id> --format html --json` for HTML with resolved image tags.
25
+ - Use `coauthor draft get <project-id> --format text --json` for plain text with image URL references.
26
+ - Use `coauthor draft get <project-id> --format json --json` or omit `--format` for the raw editor document JSON.