@vatio-ai/cli 0.44.0 → 0.45.0

package/lib/commands/support-commands.mjs

@@ -4,9 +4,11 @@
 import { mkdirSync, readFileSync, writeFileSync } from "node:fs";
 import { dirname, resolve } from "node:path";
 
+import { buildBundle } from "../bundle.mjs";
 import { HttpClient } from "../http.mjs";
 import { VERSION } from "../version.mjs";
 import { fail, takeFlag, takeValue } from "../support.mjs";
+import { findWorkspaceRoot } from "../workspace.mjs";
 import { DOCS_URL } from "./misc.mjs";
 
 // The whole developer contract as markdown, live from the platform. Fetched
@@ -50,6 +52,9 @@ function issuesClient(config) {
 // `vatio issue` is a change worth making, written against a template the
 // platform also validates against. It is not an issue tracker: there are no
 // states, labels, assignees or backlog, and that is on purpose.
+//
+// Sent from a workspace, it carries the workspace -- see workspaceSource
+// below, and `--no-source` to send the sentence alone.
 export async function issue(config, args) {
   const sub = args[0];
   if (sub === "list") return await issueList(config);
@@ -58,6 +63,7 @@ export async function issue(config, args) {
 
   if (takeFlag(args, "--template")) return await issueTemplate(config);
 
+  const withoutSource = takeFlag(args, "--no-source");
   const file = takeValue(args, "--file");
   const workspace = takeValue(args, "--workspace") ?? safeWorkspace(config);
 
@@ -67,6 +73,14 @@ export async function issue(config, args) {
 
   const body = { cli_version: VERSION };
   if (workspace) body.workspace = workspace;
+
+  const source = withoutSource ? null : workspaceSource();
+  if (source?.files) {
+    body.files = source.files;
+    console.log(`Attaching ${source.root} — ${source.files.length} files, the same ones \`vatio push\` sends.`);
+  } else if (source?.error) {
+    console.log(`Not attaching your workspace: ${source.error}`);
+  }
   if (file) {
     body.markdown = readFileSync(file, "utf8");
   } else {
@@ -75,7 +89,8 @@ export async function issue(config, args) {
       fail(
         "Usage: vatio issue \"what should change\"\n" +
           "       vatio issue --file ISSUE.md\n" +
-          "       vatio issue --template   # the shape it is read against"
+          "       vatio issue --template    # the shape it is read against\n" +
+          "       vatio issue --no-source   # without your workspace attached"
       );
     }
     body.message = message;
@@ -160,6 +175,24 @@ async function issueComment(config, id, rest) {
   console.log(`Replied on issue ${id}.`);
 }
 
+// The directory the issue was typed in, sent whole -- the same bundle `check`
+// and `push` send, because which files matter is the platform's contract and
+// this client does not get a second answer to it.
+//
+// Nothing here can stop an issue from being sent: a directory that is not a
+// workspace, or one too large to bundle, travels without its source. The call
+// site says so out loud, since a developer is entitled to know what left their
+// machine, and `--no-source` declines in advance.
+function workspaceSource() {
+  try {
+    const root = findWorkspaceRoot(process.cwd());
+    if (!root) return null;
+    return { root, files: buildBundle(root) };
+  } catch (error) {
+    return { error: error.message };
+  }
+}
+
 // A workspace is useful context on an issue but never required: `vatio issue`
 // has to work from anywhere, including a directory that is not a workspace.
 function safeWorkspace(config) {

package/lib/help.mjs

@@ -61,6 +61,7 @@ flag, the directory decides.
 
   Everything else:
     issue "what should change"|list|show ID|comment ID "reply"|--template
+                               Sends your workspace along; --no-source to not
     mcp                        Speak MCP over stdio, for a coding agent
     config show|get KEY|set KEY VALUE|unset KEY
                                Keys: base_url, token

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@vatio-ai/cli",
-  "version": "0.44.0",
+  "version": "0.45.0",
   "description": "Vatio CLI — deploy and manage Vatio agent workspaces",
   "keywords": ["vatio", "agent", "ai", "cli", "deploy"],
   "homepage": "https://vatio.ai",