create-agentmark 0.10.8 → 1.0.1

package/dist/index.d.ts

@@ -1,2 +1,106 @@
+/**
+ * Shared MCP-config builder for the scaffolders.
+ *
+ * Writes the project-local IDE config (mcp.json / settings.json) for
+ * the four supported clients. Every scaffolded project gets THREE
+ * MCP servers wired up by default:
+ *
+ *   1. `agentmark-docs` (remote HTTP) — read-only docs / reference,
+ *      hosted at `https://docs.agentmark.co/mcp`.
+ *
+ *   2. `agentmark` (stdio, `@agentmark-ai/mcp-server`) — AgentMark
+ *      Cloud surface. Defaults to `https://api.agentmark.co`; pass a
+ *      custom URL via `customApiUrl` (the undocumented `--api-url`
+ *      flag on the CLI) to point at a non-prod gateway (staging,
+ *      self-hosted).
+ *
+ *   3. `agentmark-local` (stdio, `@agentmark-ai/mcp-server`) — the
+ *      same MCP binary, pointed at the local `agentmark dev` server
+ *      (`http://localhost:9418`). The local dev server serves the
+ *      same OpenAPI contract under `/v1/openapi.json`, so the same
+ *      tool surface (`list_traces`, `get_trace`, …) is available
+ *      against local SQLite traces.
+ *
+ * Why both `agentmark` and `agentmark-local`: workflows like "pull
+ * failing traces from AgentMark Cloud, fix locally, re-verify against
+ * `agentmark dev` traces" need BOTH endpoints reachable in the same
+ * conversation. MCP clients namespace tools by server name, so the
+ * agent calls `agentmark/list_traces` for cloud and
+ * `agentmark-local/list_traces` for local — same tool, explicit
+ * destination.
+ *
+ * Auth chain is endpoint-agnostic:
+ *
+ *   - `AGENTMARK_API_KEY` env (CI / dedicated agents) wins
+ *   - falls back to `~/.agentmark/auth.json` from
+ *     `agentmark login [--base-url <matching-endpoint>]`
+ *   - local dev calls are unauthenticated by design (the local dev
+ *     server doesn't validate auth headers)
+ *
+ * Shell `export AGENTMARK_API_URL=…` still wins at runtime when the
+ * IDE inherits the shell — what we write here is the default for
+ * cold-launched IDEs.
+ */
+type McpClient = "vscode" | "zed" | "cursor" | "claude-code" | "skip";
 
-export {  }
+/**
+ * `npm create agentmark` — minimal init.
+ *
+ * Scope is deliberately small. The CLI does NOT scaffold example code,
+ * pick an LLM adapter, or handle login. Its job is:
+ *
+ *   1. Write `agentmark.json` (the SDK loader's config root)
+ *   2. Create an empty `agentmark/` directory (where prompts go)
+ *   3. Wire MCP configs for any IDE clients the user selects
+ *   4. Install the AgentMark agent skill (`npx skills add agentmark-ai/skills`)
+ *   5. Hand off to the AI tool: "Open Claude Code / Cursor and say:
+ *      Set up AgentMark in this project."
+ *
+ * Everything else — framework detection, package install, code wiring,
+ * first prompt — is the job of the `setup-and-integration` skill workflow,
+ * which runs inside the user's IDE agent. That keeps integration adaptive
+ * to whatever stack the user already has, instead of forcing a template.
+ */
+interface CliArgs {
+    path?: string;
+    clients?: McpClient[];
+    /**
+     * Undocumented escape hatch for internal staging
+     * (`https://api-stg.agentmark.co`) and rare self-hosters. Defaults to
+     * `https://api.agentmark.co`. The `agentmark-local` MCP entry always
+     * points at `http://localhost:9418` regardless of this flag.
+     */
+    apiUrl?: string;
+    overwrite?: boolean;
+}
+declare const ALL_CLIENTS: readonly McpClient[];
+declare const AGENTMARK_JSON: Record<string, unknown>;
+declare const parseArgs: (argv?: string[]) => CliArgs;
+declare const clientLabel: (id: string) => string;
+/**
+ * Resolves the target folder via positional/flag arg or interactive prompt.
+ * Default to "." when cwd looks like an existing project (the common case
+ * for "wire AgentMark into my repo"); fall back to a fresh folder name when
+ * cwd is empty (the greenfield case).
+ */
+declare const resolveTargetPath: (cliPath: string | undefined) => Promise<{
+    targetPath: string;
+    isCurrentDir: boolean;
+} | null>;
+/**
+ * Resolves which IDE clients to wire MCP into. All 4 are pre-selected on
+ * the prompt so the typical "I use everything" case is one keystroke
+ * (Enter). Empty selection is equivalent to the old "Skip" option — the
+ * caller just writes nothing.
+ */
+declare const resolveClients: (cliClients: McpClient[] | undefined) => Promise<McpClient[]>;
+/**
+ * agentmark.json is the only file we conflict on (the others — MCP config
+ * dirs, agentmark/, .gitkeep — are either additive or no-ops if present).
+ * Default to "skip" so we never silently clobber an existing project's
+ * config; `--overwrite` is the explicit opt-in for re-init scripts.
+ */
+declare const shouldWriteAgentmarkJson: (filePath: string, overwrite: boolean | undefined) => Promise<boolean>;
+declare const main: () => Promise<void>;
+
+export { AGENTMARK_JSON, ALL_CLIENTS, type CliArgs, clientLabel, main, parseArgs, resolveClients, resolveTargetPath, shouldWriteAgentmarkJson };