autokap 1.8.7 → 1.8.8

package/dist/cli-config.js

@@ -1,15 +1,9 @@
-// CLI-local config helpers.
+// CLI-local config helpers. Self-contained, canonical implementation for the
+// bundled CLI binary.
 //
-// NOTE: this file currently duplicates the canonical implementation in
-// `@autokap/core/config`. The MCP server consumes the core package directly;
-// the bundled CLI binary still ships a self-contained copy because
-// `@autokap/core` is not yet published to npm. Once core@0.1.0 is on the
-// registry and the published CLI bumps to declare it as a runtime dep, this
-// file can become a thin re-export shim (just LOCAL_WS_URL + requireConfig).
-//
-// Hardening here must stay in lockstep with packages/core/src/config.ts:
-// atomic writes, scheme allowlist on URL inputs, env-var precedence, and
-// the "untrusted origin override" guard.
+// Security invariants to preserve when editing: atomic writes, scheme
+// allowlist on URL inputs, env-var precedence, and the "untrusted origin
+// override" guard.
 import path from 'node:path';
 import os from 'node:os';
 import crypto from 'node:crypto';
@@ -131,7 +125,8 @@ export async function writeConfig(config) {
             ? { exportDebugLogs: config.exportDebugLogs }
             : {}),
     };
-    // Atomic write — see packages/core/src/config.ts for the canonical impl.
+    // Atomic write: write to a temp file then rename, so a crash mid-write
+    // never leaves a truncated config.
     const tmpPath = `${configPath}.${process.pid}.${crypto.randomBytes(4).toString('hex')}.tmp`;
     try {
         await fs.writeFile(tmpPath, JSON.stringify(normalizedConfig, null, 2), 'utf-8');

package/dist/cli-contract.d.ts

@@ -18,15 +18,6 @@ export declare const CLI_DEFAULT_INSTALL_COMMAND = "npx -y autokap@latest";
 export declare const CLI_DEFAULT_INSTALLED_SETUP_COMMAND = "autokap login <your-api-key>";
 export declare const CLI_DEFAULT_SETUP_COMMAND = "npx -y autokap@latest login <your-api-key>";
 export declare const CLI_FALLBACK_PROGRAM_COMMAND = "autokap run <preset-id> --program <file>";
-/** Bare MCP runner. Used by generic clients and as the npx command. */
-export declare const MCP_INSTALL_COMMAND = "npx -y @autokap/mcp";
-/** One-shot install command for Claude Code (CLI flag `claude mcp add`). */
-export declare const MCP_CLAUDE_CODE_COMMAND = "claude mcp add autokap -- npx -y @autokap/mcp";
-/**
- * JSON snippet to merge into the IDE-specific MCP config file (Cursor, Codex,
- * Windsurf, Cline...). Format follows the shared `mcpServers` schema.
- */
-export declare const MCP_CONFIG_SNIPPET_JSON: string;
 export declare function buildCliRunCommand(presetId: string, options?: {
     local?: boolean;
     env?: string;

package/dist/cli-contract.js

@@ -8,47 +8,20 @@ export const CLI_KEY_TERM = API_KEY_TERM;
 export const CLI_VERSION_HEADER = "x-autokap-cli-version";
 export const MIN_CLI_VERSION_FOR_SIGNED_PROGRAMS = "1.0.9";
 export const MIN_CLI_VERSION_FOR_DIRECT_ARTIFACT_UPLOADS = "1.5.0";
-// MCP-first install. The bundled CLI binary ships only for CI / Cloud Run;
-// recommend `npx -y autokap@latest` over a global install to keep version
-// drift contained and avoid the npm supply-chain anxiety the migration was
-// designed to remove. The `CLI_DEFAULT_INSTALL_COMMAND` alias is retained for
-// legacy doc surfaces that still want a single shell snippet.
+// The bundled CLI binary ships for CI / Cloud Run and for running preset
+// captures locally; recommend `npx -y autokap@latest` over a global install to
+// keep version drift contained. The `CLI_DEFAULT_INSTALL_COMMAND` alias is the
+// single shell snippet doc surfaces reference.
 export const CLI_DEFAULT_INSTALL_COMMAND = "npx -y autokap@latest";
 // `autokap init` was removed in v2. The setup command now uses the surviving
 // `autokap login` for the same purpose (store the API key in ~/.autokap/config.json).
-// MCP-first workflows should use `autokap_authenticate` from the IDE instead.
 export const CLI_DEFAULT_INSTALLED_SETUP_COMMAND = "autokap login <your-api-key>";
 export const CLI_DEFAULT_SETUP_COMMAND = "npx -y autokap@latest login <your-api-key>";
-// `autokap skill --agent` was removed in v2. The skill ships as the MCP resource
-// `autokap://skill/preset-spec` (or `autokap_get_skill` tool fallback). The
-// legacy `CLI_ADVANCED_SKILL_COMMAND` constant that pointed at the removed
-// command was dropped entirely — it had no consumers and any future doc page
-// surfacing it would mislead users into typing a non-existent command.
+// `autokap skill --agent` was removed in v2. The legacy `CLI_ADVANCED_SKILL_COMMAND`
+// constant that pointed at the removed command was dropped entirely — it had no
+// consumers and any future doc page surfacing it would mislead users into typing
+// a non-existent command.
 export const CLI_FALLBACK_PROGRAM_COMMAND = "autokap run <preset-id> --program <file>";
-// ── MCP-first install contract ──────────────────────────────────────
-//
-// AutoKap is primarily exposed as a Model Context Protocol server via the
-// `@autokap/mcp` package. Every supported IDE installs the server by adding a
-// single stdio entry that runs `npx -y @autokap/mcp` — the constants below
-// are the canonical shell forms used across onboarding surfaces (wizard,
-// modal, banner, docs). For per-IDE payloads (config paths, snippets, notes),
-// use `getMcpInstallEntries()` from `web/lib/site-discovery.ts`.
-/** Bare MCP runner. Used by generic clients and as the npx command. */
-export const MCP_INSTALL_COMMAND = "npx -y @autokap/mcp";
-/** One-shot install command for Claude Code (CLI flag `claude mcp add`). */
-export const MCP_CLAUDE_CODE_COMMAND = "claude mcp add autokap -- npx -y @autokap/mcp";
-/**
- * JSON snippet to merge into the IDE-specific MCP config file (Cursor, Codex,
- * Windsurf, Cline...). Format follows the shared `mcpServers` schema.
- */
-export const MCP_CONFIG_SNIPPET_JSON = JSON.stringify({
-    mcpServers: {
-        autokap: {
-            command: "npx",
-            args: ["-y", "@autokap/mcp"],
-        },
-    },
-}, null, 2);
 export function buildCliRunCommand(presetId, options = {}) {
     const flags = [
         options.local ? " --local" : "",
@@ -65,19 +38,19 @@ export const CLI_PUBLIC_COMMANDS = [
     {
         id: "login",
         command: "autokap login <key>",
-        summary: "Authenticate with your API key (used by Cloud Run + CI; from the IDE, call autokap_authenticate via MCP instead)",
+        summary: "Authenticate with your API key (used by Cloud Run + CI and for local preset runs)",
         docsDescriptionKey: "cliCmdLogin",
     },
     {
         id: "run",
         command: "autokap run <preset-id> --env local",
-        summary: "Run a preset capture using local Playwright (also spawned by autokap_start_capture from the MCP server)",
+        summary: "Run a preset capture using local Playwright",
         docsDescriptionKey: "cliCmdRun",
     },
     {
         id: "auto-recapture",
         command: "autokap auto-recapture --project <project-id> --env local",
-        summary: "Run every preset enabled for Recapture Cloud in a project (the canonical surface for Cloud Run + CI; MCP exposes autokap_start_auto_recapture for end users)",
+        summary: "Run every preset enabled for Recapture Cloud in a project (the canonical surface for Cloud Run + CI)",
         docsDescriptionKey: "cliCmdAutoRecapture",
     },
     {

package/dist/cli.js

@@ -120,9 +120,9 @@ program
     logger.success(`Authenticated. Key stored in ${getConfigPath()}`);
     process.exit(0);
 });
-// Auth commands (whoami / logout / ping) live in @autokap/mcp; this binary keeps
-// `login` only for CI / Cloud Run. Local dev can still inspect the config via
-// `autokap doctor` or `cat ~/.autokap/config.json`.
+// This binary keeps `login` only for CI / Cloud Run and local preset runs.
+// Local dev can still inspect the config via `autokap doctor` or
+// `cat ~/.autokap/config.json`.
 async function runOutdatedPresetsLocally(opts) {
     if (opts.output) {
         fatal('`--output` is not supported with `--outdated`; run an individual preset when local copies are needed.');
@@ -511,10 +511,10 @@ program
     });
     process.exit(0);
 });
-// Project, preset, capture, usage, video, auth, endpoints, skill, init, proxy,
-// and branding workflows live in @autokap/mcp. This binary exposes only the
-// commands needed by CI and Cloud Run (login / run / auto-recapture / doctor).
-// See MIGRATION-v1-to-v2.md for the CLI→MCP tool mapping (kept for older users).
+// Project, preset, capture, usage, video, endpoints, proxy, and branding
+// workflows are managed from the AutoKap web dashboard and GitHub PR
+// generation. This binary exposes only the commands needed by CI, Cloud Run,
+// and local preset runs (login / run / auto-recapture / doctor).
 // ── doctor command ──────────────────────────────────────────────────
 program
     .command('doctor')

package/dist/server-credit-usage.d.ts

@@ -1,5 +1,5 @@
 import type { SupabaseClient } from '@supabase/supabase-js';
-export type CreditUsageType = 'screenshot' | 'clip' | 'video' | 'cloud_recapture' | 'ai_chat' | 'studio_creation' | 'studio_iteration' | 'error_analysis' | 'obsolescence_analysis';
+export type CreditUsageType = 'screenshot' | 'clip' | 'video' | 'cloud_recapture' | 'ai_chat' | 'studio_creation' | 'studio_iteration' | 'error_analysis' | 'obsolescence_analysis' | 'pr_generation';
 export declare function recordCreditUsage(supabase: SupabaseClient, params: {
     userId: string;
     projectId: string | null;

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "autokap",
-  "version": "1.8.7",
+  "version": "1.8.8",
   "description": "AI-powered CLI tool for capturing clean screenshots of websites",
   "type": "module",
   "main": "./dist/index.js",

package/readme.md

@@ -3,21 +3,15 @@
 AI-powered website screenshot capture across every device, language, and
 theme.
 
-This npm package (`autokap`) is the **backend** consumed by:
-
-- the AutoKap Cloud Run service that handles
-  `npx autokap auto-recapture --cloud` jobs, and
-- the official MCP server `@autokap/mcp`, which spawns the package as a
-  sub-process for local capture execution (`autokap_start_capture`).
-
-**You probably do not need to install this package directly.** Wire your
-IDE assistant to `@autokap/mcp` instead — see the per-IDE install guides
-in the repository root README and the
-[migration guide](https://github.com/autokap/autokap/blob/main/MIGRATION-v1-to-v2.md).
-
-The advanced commands `autokap login`, `autokap run`, `autokap doctor`,
-and `autokap auto-recapture` remain available for users who need a
-scriptable backend (CI/CD, custom orchestrators).
+This npm package (`autokap`) is the **backend** that runs the AutoKap capture
+engine. It is consumed by the AutoKap Cloud Run service that handles
+`npx autokap auto-recapture --cloud` jobs, by CI pipelines, and for local
+preset runs.
+
+The commands `autokap login`, `autokap run`, `autokap doctor`, and
+`autokap auto-recapture` are available for users who need a scriptable backend
+(CI/CD, custom orchestrators). Project, preset, and capture management happens
+in the AutoKap web dashboard.
 
 ## Recapture Cloud in CI/CD