@cursor/july 0.1.2 → 0.1.3

package/AGENTS.md

@@ -139,6 +139,13 @@ export default defineEvalConfig({
   (schema-validated, in-process, no model). `--session <id>` runs it inside
   an existing session and records it on that session's event stream.
 - `init` with no directory prints this setup guide (does not scaffold).
+  `init <dir>` scaffolds (skipping existing files), runs `npm install`,
+  offers to install/update package skills into
+  `~/.cursor/skills/agentkit/` (TTY only; always overwrites with the
+  package copy), runs `login` and waits when unsigned, then prints `cd`
+  (when needed) and bare `dev`. `--json` still installs but never blocks
+  on login or skill install; it prints
+  `{ ok, directory, created, skipped, installed, installError, next }`.
 - `chat --json --message "..."` talks to a running server and prints a trajectory.
 
 ## Agent-to-agent (MCP endpoint + peer MCP connections)
@@ -168,7 +175,7 @@ instructions so A→B→A recursion cannot happen (e.g. a parent agent that
 delegates *only* weather questions to a `weather-agent` peer).
 
 ```bash
-agent-serve serve --dir ./agents --dev
+agent-serve dev ./agents
 agent-serve chat --url http://127.0.0.1:3000/concierge --message "Weather in Paris?"
 ```
 
@@ -192,7 +199,7 @@ agent-serve slack setup
 agent-serve slack init --dir ./my-agent --name "My Agent" --channel-posts
 # writes envPrefix from the directory name (MY_AGENT_SLACK_*)
 agent-serve slack doctor --prefix MY_AGENT
-agent-serve serve --dir ./my-agent --dev
+agent-serve dev ./my-agent
 ```
 
 Multi-agent Socket Mode needs **one Slack app (and token pair) per agent**:
@@ -218,8 +225,8 @@ The web playground is a Vite + React SPA under `playground/` (entry
 
 - If `dist/playground/` is missing and the local vite toolchain is present,
   serve auto-runs `vite build` before listening.
-- `serve --dev` also starts Vite HMR (default `:5273`) and prints
-  `playground (HMR): …`. Single-agent proxies `/v1` to the serve URL;
+- `serve --dev` / `dev` also starts Vite HMR (default `:5273`) and prints
+  that URL as `playground`. Single-agent proxies `/v1` to the serve URL;
   multi-agent serves the agents index at `/` and each SPA at
   `/<slug>/playground` (pin one slug with `AGENT_SERVE_BASE=/<slug>`).
 
@@ -261,7 +268,7 @@ agent-serve github events --dir ./agents --json
 
 # forward live deliveries to a served agent (no secret needed against --dev;
 # set GITHUB_WEBHOOK_SECRET to verify signatures)
-agent-serve serve --dir ./my-agent --dev &
+agent-serve dev ./my-agent &
 agent-serve github forward --dir ./my-agent
 ```
 
@@ -291,6 +298,10 @@ Fixtures still work for offline replay: `POST` a saved payload with an
 
 ## Do not
 
+- Proactively add or update documentation (`docs/`, READMEs, this file) as
+  part of a code change. Docs are written intentionally, on explicit request
+  only — never as a side effect of a feature or fix. If a change makes docs
+  stale, say so in the PR description instead of editing them unprompted.
 - Put durable `--state-root` inside a large monorepo if you care about
   ambient `AGENTS.md` / `.cursor` rules leaking into the agent workspace.
   Prefer `defineAgent({ local: { cwd } })` pointing outside the monorepo

package/README.md

@@ -53,9 +53,10 @@ my-agent/
 ```
 
 Scaffold a starter project with `agent-serve init ./my-agent` — a minimal
-agent (`package.json`, `agent/agent.ts`, `agent/instructions.md`, and a demo
-`agent/tools/echo.ts`) that serves immediately. From there, grow it folder by
-folder; the [docs](./docs/README.md) walk a weather agent from a single
+agent (`package.json`, `tsconfig.json`, `agent/agent.ts`,
+`agent/instructions.md`, and a demo `agent/tools/echo.ts`) that serves
+immediately and type-checks with `npm run check`. From there, grow it folder
+by folder; the [docs](./docs/README.md) walk a weather agent from a single
 `get_weather` tool through skills, channels, evals, and deployment.
 
 Serve one project with `agent-serve serve --dir ./my-agent --dev`, or point
@@ -79,10 +80,8 @@ one port, each under its own slug (its directory name):
 
 ```bash
 agent-serve serve --dir ./agents --dev
-# 2 agents listening on http://127.0.0.1:3000
-#   index: http://127.0.0.1:3000/
-#   /weather-agent → /weather-agent/playground, /weather-agent/v1/*
-#   /concierge    → /concierge/playground, /concierge/v1/*
+# 2 agents listening
+#   playground  http://127.0.0.1:5273
 ```
 
 `serve` always uses multi-agent layout by default: agents are mounted under
@@ -377,8 +376,8 @@ own playground at `/<slug>/playground` and `/` is an index of them all (see
 
 ### Developing the playground
 
-`serve --dev` also starts Vite HMR (default `:5273`) and prints
-`playground (HMR): …`. Single-agent proxies `/v1` to the serve URL; multi-agent
+`serve --dev` / `dev` also starts Vite HMR (default `:5273`) and prints that
+URL as `playground`. Single-agent proxies `/v1` to the serve URL; multi-agent
 serves the agents index at `/` and each SPA at `/<slug>/playground`:
 
 ```bash

package/dist/bin/agent-serve.d.ts

@@ -3,10 +3,12 @@
  * agent-serve CLI.
  *
  *   agent-serve serve      [--dir .] [--port 3000] [--host 127.0.0.1] [--dev]
+ *   agent-serve dev        [path] [--port 3000] [--host 127.0.0.1]
  *   agent-serve chat      [--url http://127.0.0.1:3000] [--message "..."] [--json]
+ *   agent-serve resume    <sessionId> [--url | --prod] [--message "..."]
  *   agent-serve run       [--dir .] [--message "..."] [--json|--text]
  *   agent-serve trajectory --events <file.ndjson>
- *   agent-serve init      [dir]
+ *   agent-serve init      [dir] [--json]
  *   agent-serve eval        [--dir .] [evalId...]
  *   agent-serve validate   [--dir .]
  *   agent-serve slack     <subcommand>

package/dist/bin/agent-serve.d.ts.map

@@ -1 +1 @@
-{"version":3,"file":"agent-serve.d.ts","sourceRoot":"","sources":["../../src/bin/agent-serve.ts"],"names":[],"mappings":";AACA;;;;;;;;;;;GAWG"}
+{"version":3,"file":"agent-serve.d.ts","sourceRoot":"","sources":["../../src/bin/agent-serve.ts"],"names":[],"mappings":";AACA;;;;;;;;;;;;;GAaG"}