artifacty 0.5.0 → 0.6.0

package/README.md

@@ -27,37 +27,43 @@ artifacty --help
 Run it without a global install:
 
 ```bash
-npx artifacty@latest serve
+npx artifacty@latest serve --foreground
 ```
 
-Start the local dashboard:
+Start the local dashboard in the background:
 
 ```bash
 artifacty serve
 ```
 
-Open the URL printed by the server. Artifacty prefers `http://127.0.0.1:8787`; if that default port is busy and no explicit port was configured, it starts on the next available local port and records the actual URL for CLI and MCP responses.
+Open the `url` printed in the JSON response. Artifacty prefers `http://127.0.0.1:8787`; if that default port is busy and no explicit port was configured, it starts on the next available local port and records the actual URL for CLI and MCP responses.
 
-Run it in the background and return to your prompt:
+Manage the background server:
 
 ```bash
-artifacty start
 artifacty status
 artifacty stop
 ```
 
-`artifacty serve --detach` is equivalent to `artifacty start`. Logs are written under `~/.artifacty/logs/`.
+`artifacty start` and `artifacty serve --detach` use the same lifecycle path as `artifacty serve`. Logs are written under `~/.artifacty/logs/`.
 These lifecycle commands use Node's detached process support and work on macOS, Linux, and Windows. `artifacty stop` uses Windows `taskkill` on Windows and process-group signals on macOS/Linux.
 
+For foreground debugging, keep the process attached:
+
+```bash
+artifacty serve --foreground
+npm start
+```
+
 Generate an API token at startup when you want to protect HTTP API and browser write routes:
 
 ```bash
 artifacty serve --generate-token
 artifacty serve --host 0.0.0.0 --share-mode lan --generate-token
-npm start -- --generate-token
+artifacty serve --foreground --generate-token
 ```
 
-The server prints the generated token plus `/new?token=...` and `/import?token=...` URLs. For scripts or background services that need a stable token, generate one first:
+Background `serve` returns the generated token and ready-to-open `/new?token=...` and `/import?token=...` URLs in JSON. Foreground `serve` prints the same values to stderr. For scripts or long-running services that need a stable token, generate one first:
 
 ```bash
 artifacty token
@@ -216,11 +222,11 @@ artifacty integrity
 
 ## API Example
 
-Start a protected server in another terminal, or generate a reusable shell token first:
+Start a protected server with a reusable shell token:
 
 ```bash
-artifacty serve --generate-token
 export ARTIFACTY_API_TOKEN="$(artifacty token --raw)"
+artifacty serve --api-token "$ARTIFACTY_API_TOKEN"
 ```
 
 ```bash

package/docs/integrations.md

@@ -13,22 +13,23 @@ The dashboard prefers `http://127.0.0.1:8787`. If that port is busy and no expli
 Use a generated startup token when running a protected foreground server:
 
 ```bash
-node src/cli.js serve --generate-token
-node src/cli.js serve --host 0.0.0.0 --share-mode lan --generate-token
+node src/cli.js serve --foreground --generate-token
+node src/cli.js serve --foreground --host 0.0.0.0 --share-mode lan --generate-token
 npm start -- --generate-token
 ```
 
-The generated token is printed with ready-to-open create and import URLs.
+Foreground runs print the generated token with ready-to-open create and import URLs. Background runs return the same values in JSON.
 
 For prompt-friendly local background runs, use the lifecycle commands:
 
 ```bash
+node src/cli.js serve --port 8787
 node src/cli.js start --port 8787
 node src/cli.js status
 node src/cli.js stop
 ```
 
-`serve --detach` uses the same detached-process path as `start`. It writes `server.pid`, `server.json`, and logs under `ARTIFACTY_HOME` (default `~/.artifacty`). Prefer `start --api-token "$(node src/cli.js token --raw)"` when a background server needs API protection, because generated startup tokens are only visible in the server log.
+`serve`, `serve --detach`, and `start` use the same detached-process path. They write `server.pid`, `server.json`, and logs under `ARTIFACTY_HOME` (default `~/.artifacty`). `serve --generate-token` and `start --generate-token` generate the API token in the parent CLI process and return it in JSON along with ready-to-open create/import URLs. Use `serve --foreground` when you want attached logs for debugging.
 
 The lifecycle commands are intended to be cross-platform:
 
@@ -105,7 +106,7 @@ Generate a token for protected HTTP routes:
 node src/cli.js token
 node src/cli.js serve --generate-token
 npm start -- --generate-token
-ARTIFACTY_API_TOKEN="$(node src/cli.js token --raw)" node src/cli.js serve
+ARTIFACTY_API_TOKEN="$(node src/cli.js token --raw)" node src/cli.js serve --foreground
 ```
 
 ## Claude Code
@@ -308,7 +309,7 @@ node src/cli.js service install
 
 The generated service runs `src/server.js` with explicit `--host` and `--home` arguments. It includes `--port` only when you configure a port, which keeps the default port fallback available. Load or unload it manually with the `launchctl` commands returned by `service install`.
 
-For background services, prefer a stable `ARTIFACTY_API_TOKEN` in the service environment. `serve --generate-token` is intended for foreground runs where the operator can read the generated token from startup output.
+For background services, prefer a stable `ARTIFACTY_API_TOKEN` in the service environment. `serve --generate-token` is intended for temporary interactive sessions; the parent CLI returns the generated token in JSON.
 
 ## Backup and Audit
 

package/docs/network-sharing.md

@@ -30,7 +30,7 @@ The generated token protects HTTP API routes and browser write forms. Prefer the
 
 Artifacty does not terminate TLS. Do not expose it directly on the public internet. If a shared instance must cross an untrusted network, put it behind a TLS reverse proxy or a private VPN.
 
-When Artifacty binds outside loopback, startup output includes a warning that the server is reachable beyond the local machine and that TLS is not provided by Artifacty.
+When Artifacty binds outside loopback, startup output includes a warning that the server is reachable beyond the local machine and that TLS is not provided by Artifacty. Background `serve` returns this warning in JSON; foreground `serve` and `src/server.js` also write it to stderr.
 
 ## Browser Write Behavior
 

package/docs/release-checklist.md

@@ -24,6 +24,7 @@ This runs syntax checks, the full Node test suite, and a local smoke test that s
 - Keep the default HTTP bind address at `127.0.0.1`.
 - Require `ARTIFACTY_API_TOKEN` and `ARTIFACTY_SHARE_MODE=lan` or `team` before binding to `0.0.0.0`.
 - Confirm non-loopback startup output includes the LAN/team warning.
+- Confirm `artifacty serve` starts a managed background server and returns prompt-friendly JSON; use `artifacty serve --foreground` for attached log checks.
 - Prefer `x-artifacty-token` or `Authorization: Bearer <token>` over query tokens in scripts.
 - Review secret-scan bypasses. `--allow-secrets` and `ARTIFACTY_ALLOW_SECRETS=true` should be deliberate and temporary.
 - Review [../SECURITY.md](../SECURITY.md) and [threat-model.md](threat-model.md) when changing auth, rendering, MCP, or network-sharing behavior.

package/docs/threat-model.md

@@ -51,8 +51,8 @@ Controls:
 - Browser form token URLs exist only for local convenience.
 - Token comparisons use timing-safe digest comparison.
 
-Guidance: rotate tokens after sharing sessions and prefer foreground generated
-tokens for temporary LAN use.
+Guidance: rotate tokens after sharing sessions, prefer header-based tokens for
+scripts, and use generated startup tokens only for temporary interactive shares.
 
 ### Cross-Site Request Forgery
 

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "artifacty",
-  "version": "0.5.0",
+  "version": "0.6.0",
   "description": "Local artifact exchange for heterogeneous LLM agents via HTTP and MCP.",
   "type": "module",
   "keywords": [

package/src/cli.js

@@ -47,7 +47,10 @@ async function main() {
   }
 
   if (command === "serve") {
-    if (options.detach) {
+    if (options.detach && options.foreground) {
+      throw new Error("Use either --foreground or --detach, not both");
+    }
+    if (!options.foreground) {
       printJson(await startBackgroundServer({
         ...serverOptions(options),
         serverPath: path.join(PACKAGE_ROOT, "src", "server.js")
@@ -314,7 +317,7 @@ function parseArgs(args) {
     }
 
     const key = arg.slice(2);
-    if (key === "raw" || key === "dry-run" || key === "trust" || key === "include-archived" || key === "allow-secrets" || key === "generate-token" || key === "detach" || key === "force") {
+    if (key === "raw" || key === "dry-run" || key === "trust" || key === "include-archived" || key === "allow-secrets" || key === "generate-token" || key === "detach" || key === "foreground" || key === "force") {
       options[toCamelCase(key)] = true;
       continue;
     }
@@ -397,10 +400,11 @@ function printHelp() {
 
 Usage:
   artifacty token [--bytes 32] [--raw]
-  artifacty serve [--host 127.0.0.1] [--port 8787] [--home ~/.artifacty] [--api-token token] [--generate-token] [--bytes 32] [--detach]
-  artifacty start [--host 127.0.0.1] [--port 8787] [--home ~/.artifacty] [--api-token token] [--timeout 5000]
+  artifacty serve [--host 127.0.0.1] [--port 8787] [--home ~/.artifacty] [--api-token token] [--generate-token] [--bytes 32] [--foreground]
+  artifacty serve --foreground [--generate-token]
+  artifacty start [--host 127.0.0.1] [--port 8787] [--home ~/.artifacty] [--api-token token] [--generate-token] [--timeout 30000]
   artifacty status [--home ~/.artifacty]
-  artifacty stop [--home ~/.artifacty] [--timeout 5000] [--force]
+  artifacty stop [--home ~/.artifacty] [--timeout 30000] [--force]
   artifacty publish --title <title> (--file <path> | --content <text>) [--format html|markdown|text|json|code|svg|mermaid|react] [--source agent] [--tag tag]
   artifacty import --agent claude|codex|gemini|copilot|cursor|auto (--file <path> | --content <text>) [--title <title>] [--format html|markdown|text|json|code|svg|mermaid|react] [--tag tag]
   artifacty install claude|codex|gemini|copilot|cursor|all [--dry-run] [--config <path>] [--server-path <path>] [--url http://127.0.0.1:8787] [--timeout 30000]

package/src/lib/background.js

@@ -4,14 +4,23 @@ import { readFile } from "node:fs/promises";
 import path from "node:path";
 import { createStore } from "./storage.js";
 import { readServerState, serverStatePath } from "./server-state.js";
+import { exposureWarning, securityConfig } from "./security.js";
+import { generateToken } from "./token.js";
 
-const DEFAULT_READY_TIMEOUT_MS = 5000;
+const DEFAULT_READY_TIMEOUT_MS = 30000;
+const DEFAULT_HOST = "127.0.0.1";
 
 export async function startBackgroundServer(options = {}) {
   if (options.generateToken && options.apiToken) {
     throw new Error("Use either --api-token or --generate-token, not both");
   }
 
+  const generatedToken = options.generateToken ? generateToken(options) : null;
+  const serverOptions = {
+    ...options,
+    apiToken: generatedToken?.token || options.apiToken,
+    generateToken: false
+  };
   const store = createStore({ home: options.home });
   const paths = backgroundPaths(store);
   const current = await backgroundStatus({ home: store.home });
@@ -22,7 +31,7 @@ export async function startBackgroundServer(options = {}) {
   mkdirSync(paths.logDir, { recursive: true });
   mkdirSync(store.home, { recursive: true });
 
-  const child = spawnDetachedServer(options, store, paths);
+  const child = spawnDetachedServer(serverOptions, store, paths);
 
   writeFileSync(paths.pidFile, `${child.pid}\n`, "utf8");
 
@@ -39,6 +48,11 @@ export async function startBackgroundServer(options = {}) {
       pid: child.pid,
       url: ready.url,
       home: store.home,
+      auth: authResponse(generatedToken, ready.url),
+      securityWarning: exposureWarning({
+        host: serverOptions.host || process.env.ARTIFACTY_HOST || DEFAULT_HOST,
+        config: securityConfig(serverOptions)
+      }) || undefined,
       logs: {
         stdout: paths.stdoutLog,
         stderr: paths.stderrLog
@@ -58,6 +72,20 @@ export async function startBackgroundServer(options = {}) {
   }
 }
 
+function authResponse(generatedToken, url) {
+  if (!generatedToken) {
+    return null;
+  }
+  return {
+    token: generatedToken.token,
+    bytes: generatedToken.bytes,
+    header: generatedToken.header,
+    authorization: generatedToken.authorization,
+    createUrl: `${url}/new?token=${encodeURIComponent(generatedToken.token)}`,
+    importUrl: `${url}/import?token=${encodeURIComponent(generatedToken.token)}`
+  };
+}
+
 export async function stopBackgroundServer(options = {}) {
   const store = createStore({ home: options.home });
   const paths = backgroundPaths(store);
@@ -68,7 +96,7 @@ export async function stopBackgroundServer(options = {}) {
       action: "stop",
       stopped: false,
       running: status.running,
-      reason: status.pid ? "server was not started by artifacty start" : "server is not running",
+      reason: status.pid ? "server was not started by artifacty serve/start" : "server is not running",
       pid: status.pid || null,
       home: store.home
     };