@cursor/july 0.1.108 → 0.1.111

package/docs/guides/opentelemetry.md

@@ -7,11 +7,11 @@ description: "Push session, turn, and tool traces from the serve process to an O
 
 Agent SDK can push traces, metrics, and logs from the serve process to
 an OTLP collector you run. Point the process at the collector with
-standard `OTEL_EXPORTER_OTLP_*` env, or author `agent/otel.ts`. Traces
-cover the inbound request, each turn, and every tool call.
+standard `OTEL_EXPORTER_OTLP_*` environment variables, or pass the
+same options to `serve({ otel })`. Traces cover the inbound request,
+each turn, and every tool call.
 
-Export is opt-in. Nothing leaves the process until you set an endpoint
-or a `defineOtel` config.
+Export is opt-in. Nothing leaves the process until you set an endpoint.
 
 ## What does Agent SDK export?
 
@@ -22,7 +22,7 @@ or a `defineOtel` config.
 | Logs | off | Session events as log records. Prompt text, tool payloads, and failure messages stay off unless you opt in |
 
 Turn off a signal with `traces: false`, `metrics: false`, or `logs: false`
-on `defineOtel`. Logs also turn on when you set `OTEL_LOGS_EXPORTER` to
+on `serve({ otel })`. Logs also turn on when you set `OTEL_LOGS_EXPORTER` to
 anything other than `none`, or when you set the content flags below.
 
 ## How do I turn OpenTelemetry export on?
@@ -61,46 +61,34 @@ Optional:
 | `OTEL_LOG_USER_PROMPTS=1` | Include user prompt text on logs and span events |
 | `OTEL_LOG_TOOL_CONTENT=1` | Include tool payloads and failure text (truncated) |
 
-`serve(dir, { otel: false })` turns export off even when env or
-`agent/otel.ts` is set.
+`serve(dir, { otel: false })` turns export off even when env is set.
 
-## How do I author `agent/otel.ts`?
-
-Use `defineOtel` when you want the collector URL, headers, or sampling
-in the project instead of the environment:
+You can pass the same options object to `serve(dir, { otel })`.
+Precedence is `serve({ otel })` over env.
 
 ```ts
-import { defineOtel } from "@cursor/july/otel";
-
-export default defineOtel({
-  serviceName: "cursor",
-  exporters: [
-    {
-      url: "https://otel.example.com",
-      protocol: "http/protobuf",
-      headers: { Authorization: "Bearer …" },
-    },
-  ],
+await serve(dir, {
+  otel: {
+    serviceName: "cursor",
+    exporters: [
+      {
+        url: "https://otel.example.com",
+        protocol: "http/protobuf",
+        headers: { Authorization: "Bearer …" },
+      },
+    ],
+  },
 });
 ```
 
 Multiple `exporters` fan out to every destination. Restrict one
 destination with `signals: ["traces"]`.
 
-You can also pass the same object to `serve(dir, { otel })`. Precedence
-is `serve({ otel })` over `agent/otel.ts` over env. An empty
-`defineOtel()` still records traces; export starts when
-`OTEL_EXPORTER_OTLP_*` or a factory-returned `exporters` list appears.
-
-Hosted deployments can bind secrets after startup. Pass a factory so
-flush can re-read them. The hosted handler constructs the OTLP client
-when it flushes and sends the queued batch.
-
-```ts
-export default defineOtel(() => resolveMyOtelConfig());
-```
+`defineOtel` / `agent/otel.ts` (`@cursor/july/internal/otel`) is
+factory-only. Discovery still loads that file for Cursor factory
+agents. It is not a public Agent SDK export.
 
-The companion skill is [`skills/otel/SKILL.md`](../skills/otel.md).
+The companion skill is [`skills/otel/SKILL.md`](../../skills/otel/SKILL.md).
 
 ## What spans does a session produce?
 
@@ -192,7 +180,7 @@ generic message (`turn failed` / `session failed`).
 
 Opt in with `OTEL_LOG_USER_PROMPTS=1` and `OTEL_LOG_TOOL_CONTENT=1`, or
 the matching `logs: { userPrompts, toolContent }` fields on
-`defineOtel`. Opted-in strings truncate at 2,048 characters.
+`serve({ otel })`. Opted-in strings truncate at 2,048 characters.
 
 Deployment URLs from `agent.bound` stay off spans unless
 `toolContent` is on.
@@ -223,14 +211,13 @@ another library already registered a TracerProvider, MeterProvider, or
 LoggerProvider, Agent SDK reuses it. Run `serve` as its own process
 when the Agent SDK exporters should own the destination.
 
-Two mounts with different `agent/otel.ts` files fail at serve start.
-Use the same `defineOtel` config on every mount, or configure once
-through `serve({ otel })` or env.
+Two mounts with different authored OTel configs fail at serve start.
+Configure once through `serve({ otel })` or env.
 
 ## What's next
 
-- [`skills/otel/SKILL.md`](../skills/otel.md): compact
-  `defineOtel` reference for coding agents
+- [`skills/otel/SKILL.md`](../../skills/otel/SKILL.md): compact
+  env / `serve({ otel })` reference for coding agents
 - [Hooks](../reference/hooks.md): observe the same session event stream
   in-process
 - [Deployment](../deployment.md): env, secrets, and self-hosting

package/docs/guides/slack.md

@@ -7,12 +7,13 @@ description: "Run a Socket Mode Slack bot from the dashboard wizard, or import a
 
 The Slack channel is a Socket Mode bot. The app connects out, so you
 don't need a public Request URL. Mentions and DMs start a thread.
-Replies stream there, with thinking steps and suggested prompts.
+Replies land in that thread. You choose the status chip, a live
+stream, or agent-owned posts.
 
 Use `agent-sdk slack create` when Cursor should own the Slack app. Use
 `agent-sdk slack init --manual` when you own it. Commands and flags live
 in the [CLI reference](../reference/cli.md#slack). Coding agents should
-follow [`skills/setup-slack/SKILL.md`](../skills/setup-slack.md).
+follow [`skills/setup-slack/SKILL.md`](../../skills/setup-slack/SKILL.md).
 
 ## Define the channel
 
@@ -61,7 +62,7 @@ Slack gives an agent two places to show progress while a turn runs: the
 status chip under the thread ("Running grep…") and the reply message
 itself. It won't fill both at once. While a message is streaming, Slack
 shows its own "is working…" chip and hides any status text you set. Cards
-only exist inside a streamed message. `reply.mode` picks which one you get.
+only exist inside a streamed message. `reply.mode` picks the path.
 
 ### `post` (default): status chip, then one message
 
@@ -123,6 +124,54 @@ and `output(result)` the text to add when it finishes.
 `toolLabels` renames tools everywhere they appear: the chip, card titles,
 and the default `Running …` line.
 
+### `agentic`: the agent posts
+
+Opt in when the agent should own every message in the thread. Mentions
+and DMs still start turns. The channel does not write the status chip,
+tool cards, reasoning cards, or assistant text. Approval cards
+still post if you set `toolApprovals`.
+
+Mount `@cursor/july/extensions/slack-communication` so the agent can
+talk. The extension adds typed tools and the `slack-voice` skill. The
+channel watches those tool names (bare or `<namespace>__<name>`) and
+calls Slack through the channel client after a successful result. A
+rejected call, a dry-run stub, or a turn that never calls
+`post-update` stays silent. The framework does not also finalize
+assistant text.
+
+```ts
+// agent/extensions/slack.ts
+import slackCommunication from "@cursor/july/extensions/slack-communication";
+
+export default slackCommunication();
+```
+
+```ts
+// agent/channels/slack.ts
+export default slackChannel({
+  reply: { mode: "agentic" },
+});
+```
+
+| Tool | What it writes | Scope |
+| --- | --- | --- |
+| `post-update` | Mid-turn progress and the final reply (`chat.postMessage` / `chat.update`) | `chat:write` |
+| `post-card` | Collapsible task card (`chat.startStream` / `chat.appendStream`) | `chat:write` |
+| `post-file` | Workspace file on the reply (`files.getUploadURLExternal`) | `files:write` |
+| `react` | Emoji on a message `ts` (`reactions.add`). Omit `ts` for the thread root. | `reactions:write` |
+| `set-status` | Subtitle chip (`assistant.threads.setStatus`). Empty string clears it. | `assistant:write` |
+
+`agent-sdk slack create` already grants those scopes. Do not add a
+freeform Slack method tool.
+
+Pass `tone` to add agent-specific voice without forking the tools:
+
+```ts
+export default slackCommunication({
+  tone: "Lead with the merge decision. Name the risk next.",
+});
+```
+
 ### Migrating from `streaming` and `thinkingSteps`
 
 `streaming: false` is `reply: { mode: "post" }`. `streaming: true` is
@@ -267,7 +316,7 @@ The Slack app needs interactivity. Recreate it with `slack create` if
 clicks do nothing. Cards show redacted, truncated arguments. Execution
 still uses the full input, so review sensitive tools in the playground
 when the card may hide fields. The lifecycle is in
-[Human-in-the-loop](./human-in-the-loop.md).
+[Gate a tool on human approval](../reference/tools.md#gate-a-tool-on-human-approval).
 
 ## Run several agents on one host
 

package/docs/guides/webhooks.md

@@ -9,7 +9,8 @@ A custom channel gives the agent its own HTTP surface. You get routes
 with validated payloads, sessions keyed to something in your domain (a
 thread, a ticket, a PR), and replies delivered back to the caller. The
 [Slack](./slack.md) and [GitHub](./github.md) packs build on this
-mechanism. This page is the mechanism itself.
+mechanism. The [GitLab](./gitlab.md) and [Bitbucket](./bitbucket.md) packs
+use it too. This page is the mechanism itself.
 
 ## What you already have
 
@@ -361,7 +362,7 @@ A plain API key fits a personal integration. A production Linear agent
 is an OAuth application: installing it in a workspace mints an access
 token with an expiry plus a refresh token. The serve host can be
 replaced at any time, so the pair can't live in process memory.
-Persist it in [`host.kv`](../storage.md#author-kv-ctx-host-kv) instead.
+Persist it in `host.kv` instead.
 Route handlers receive `host` in their args, and event handlers get the
 same services on `ctx`.
 
@@ -371,9 +372,8 @@ Two prerequisites:
   [deployment secrets](../deployment.md). They're static, so
   deploy-time env vars fit them.
 - Back kv with durable storage. On Cursor-managed hosting, use
-  `cursorHostedStorage` in `agent/storage.ts`
-  ([Storage](../storage.md)). Without it, kv falls back to local disk
-  and a host replacement drops the tokens.
+  `cursorHostedStorage` in `agent/storage.ts`. Without it, kv falls back
+  to local disk and a host replacement drops the tokens.
 
 Save the pair when the install flow completes, then refresh on demand:
 
@@ -463,6 +463,7 @@ from any PR you can read. See the [GitHub guide](./github.md).
 Continue with these pages:
 
 - [Channels reference](../reference/channels.md): the full authoring API
-- [GitHub](./github.md) and [Slack](./slack.md): the packaged channels
+- [GitHub](./github.md), [GitLab](./gitlab.md),
+  [Bitbucket](./bitbucket.md), and [Slack](./slack.md): the packaged channels
 - [Sessions and streaming](../reference/sessions.md): events your
   channel can subscribe to

package/docs/hillclimbing.md

@@ -22,7 +22,7 @@ flowchart LR
 
 ## How do I hillclimb an agent with a coding agent?
 
-Have Cursor read [`skills/hillclimb/SKILL.md`](./skills/hillclimb.md).
+Have Cursor read [`skills/hillclimb/SKILL.md`](../skills/hillclimb/SKILL.md).
 
 Tell it:
 
@@ -36,10 +36,10 @@ Other skills cover the edges:
 
 | When you need… | Skill |
 | --- | --- |
-| The measured improvement loop | [`skills/hillclimb/SKILL.md`](./skills/hillclimb.md) |
-| An eval that locks a kept win | [`skills/evals/SKILL.md`](./skills/evals.md) |
-| Repeatable GitHub webhook inputs | [`skills/github/SKILL.md`](./skills/github.md) |
-| A run that misbehaves | [`skills/debug/SKILL.md`](./skills/debug.md) |
+| The measured improvement loop | [`skills/hillclimb/SKILL.md`](../skills/hillclimb/SKILL.md) |
+| An eval that locks a kept win | [`skills/evals/SKILL.md`](../skills/evals/SKILL.md) |
+| Repeatable GitHub webhook inputs | [`skills/github/SKILL.md`](../skills/github/SKILL.md) |
+| A run that misbehaves | [`skills/debug/SKILL.md`](../skills/debug/SKILL.md) |
 
 See [Building agents with agents](./building-with-agents.md) for every framework skill and a good first prompt.
 
@@ -72,9 +72,9 @@ Pin the input first. A moving fixture is noise. For GitHub agents, use `agent-sd
 
 ## How do I lock a hillclimb improvement with an eval?
 
-Every kept change needs an eval that would have failed before the change: a tool-choice gate, an `action.result` count bound, or an output-shape check. Run `agent-sdk eval --dir . --json` between rounds. Never weaken an existing gate to pass the round.
+Every kept change needs an eval that would have failed before the change: a tool-choice gate, a `maxToolCalls` bound, or an output-shape check. Run `agent-sdk eval --dir . --json` between rounds. Never weaken an existing gate to pass the round.
 
-Details live in [Evals](./evals.md). The evals skill will author the case with you.
+Details live in [Keep improvements with regression evals](./evals.md#keep-improvements-with-regression-evals). The evals skill will author the case with you.
 
 ## What habits help hillclimbing stay reliable?
 

package/docs/quickstart.md

@@ -1,45 +1,36 @@
 ---
-title: "Build your first PR reviewer"
+title: "Build a PR reviewer"
 description: "Create an agent that reviews pull requests by complexity, approves safe changes, and handles GitHub webhook events."
 ---
 
-# Build your first PR reviewer
+# Build a PR reviewer
 
 Build a GitHub PR reviewer that classifies changes as `trivial`,
 `moderate`, or `large`, then approves safe changes or requests human
-review. Add GitHub event handling so pull requests can trigger reviews.
+review.
 
-## Getting started
+## Prerequisites
 
-- **Get started with an agent in Cursor:** follow
-  [Scaffold an agent with Cursor](./scaffolding-agents.md) and ask Cursor
-  to read [`skills/create-agent/SKILL.md`](./skills/create-agent.md).
-- **Get started in the CLI:** continue below.
+- Node 22.13 or newer.
+- agent-sdk cli
 
-## Prerequisites
+```
+npm install -g @cursor/agent-sdk
+```
 
-- Node 22.13 or newer. Bun isn't supported.
-- Run commands as `agent-sdk <command>`, or use
-  `npx @cursor/july <command>` when the CLI isn't on `PATH`. See
-  [Run the CLI](/#run-the-cli) if `agent-sdk` is not on `PATH`.
 - A Cursor credential for model turns. Sign in once:
 
 ```bash
 agent-sdk login
 ```
 
-You can also set `CURSOR_API_KEY` instead of signing in.
-
-- Authenticate with `gh auth login` or `GITHUB_TOKEN`. You can read
-  public pull requests. Posting reviews requires repository write access.
-
 ## Create and run the project
 
 Initialize the project and start the development server:
 
 ```bash
-npx @cursor/july init ./sdk-pr-reviewer
-cd sdk-pr-reviewer
+npx @cursor/agent-sdk init ./pr-reviewer
+cd pr-reviewer
 agent-sdk dev
 ```
 
@@ -79,35 +70,6 @@ For every pull request:
 End with one sentence: the verdict and why.
 ```
 
-Remove the demo echo tool:
-
-```bash
-rm agent/tools/echo.ts
-```
-
-## Add a shared helper
-
-Create `agent/lib/github.ts`:
-
-```ts
-export interface PullRef {
-  owner: string;
-  repo: string;
-  number: number;
-}
-
-/** Split https://github.com/owner/repo/pull/123 into its parts. */
-export function parsePullUrl(prUrl: string): PullRef {
-  const url = new URL(prUrl);
-  const [owner, repo, pulls, number] = url.pathname.split("/").filter(Boolean);
-  const parsed = Number.parseInt(number ?? "", 10);
-  if (pulls !== "pull" || owner === undefined || Number.isNaN(parsed)) {
-    throw new Error(`Not a pull request URL: ${prUrl}`);
-  }
-  return { owner, repo, number: parsed };
-}
-```
-
 ## Add the inspect tool
 
 Create `agent/tools/inspect_pr.ts`:
@@ -115,18 +77,18 @@ Create `agent/tools/inspect_pr.ts`:
 ```ts
 import { defineTool } from "@cursor/july/tools";
 import { z } from "zod";
-import { parsePullUrl } from "../lib/github.js";
 
 export type Complexity = "trivial" | "moderate" | "large";
 
-/** Rate complexity from fixed line and file-count thresholds. */
 function rateComplexity(linesChanged: number, changedFiles: number): Complexity {
   if (linesChanged <= 25 && changedFiles <= 2) {
     return "trivial";
   }
+
   if (linesChanged <= 400 && changedFiles <= 15) {
     return "moderate";
   }
+
   return "large";
 }
 
@@ -135,6 +97,7 @@ function trimPatch(patch: string | undefined): string | undefined {
   if (patch === undefined || patch.length <= 3000) {
     return patch;
   }
+
   return `${patch.slice(0, 3000)}\n[... patch trimmed ...]`;
 }
 
@@ -147,17 +110,24 @@ export default defineTool({
       .describe("Pull request URL: https://github.com/owner/repo/pull/123"),
   }),
   async execute({ prUrl }, ctx) {
-    const { owner, repo, number } = parsePullUrl(prUrl);
+    const url = new URL(prUrl);
+    const [owner, repo, pulls, number] = url.pathname.split("/").filter(Boolean);
+    const pull_number = Number.parseInt(number ?? "", 10);
+    if (pulls !== "pull" || owner === undefined || Number.isNaN(pull_number)) {
+      throw new Error(`Not a pull request URL: ${prUrl}`);
+    }
+
     const octokit = await ctx.host.github.getOctokit();
     const { data: pr } = await octokit.rest.pulls.get({
       owner,
       repo,
-      pull_number: number,
+      pull_number,
     });
+
     const { data: files } = await octokit.rest.pulls.listFiles({
       owner,
       repo,
-      pull_number: number,
+      pull_number,
       per_page: 100,
     });
 
@@ -165,6 +135,7 @@ export default defineTool({
       pr.additions + pr.deletions,
       pr.changed_files
     );
+
     return {
       title: pr.title,
       author: pr.user?.login,
@@ -178,7 +149,6 @@ export default defineTool({
         path: file.filename,
         additions: file.additions,
         deletions: file.deletions,
-        // Large changes get a stats-only skim; a human reads the code.
         ...(complexity === "large" ? {} : { patch: trimPatch(file.patch) }),
       })),
     };
@@ -214,7 +184,6 @@ Create `agent/tools/submit_review.ts` to post each verdict:
 ```ts
 import { defineTool } from "@cursor/july/tools";
 import { z } from "zod";
-import { parsePullUrl } from "../lib/github.js";
 
 export default defineTool({
   description:
@@ -229,7 +198,13 @@ export default defineTool({
       .describe("One or two sentences explaining the verdict."),
   }),
   async execute({ prUrl, verdict, summary }, ctx) {
-    const { owner, repo, number } = parsePullUrl(prUrl);
+    const url = new URL(prUrl);
+    const [owner, repo, pulls, number] = url.pathname.split("/").filter(Boolean);
+    const pull_number = Number.parseInt(number ?? "", 10);
+    if (pulls !== "pull" || owner === undefined || Number.isNaN(pull_number)) {
+      throw new Error(`Not a pull request URL: ${prUrl}`);
+    }
+
     const review =
       verdict === "approve"
         ? { event: "APPROVE" as const, body: `PR reviewer: ${summary}` }
@@ -242,7 +217,7 @@ export default defineTool({
     await octokit.rest.pulls.createReview({
       owner,
       repo,
-      pull_number: number,
+      pull_number,
       event: review.event,
       body: review.body,
     });
@@ -280,20 +255,16 @@ const REVIEW_ACTIONS = new Set(["opened", "reopened", "ready_for_review"]);
 
 export default githubChannel({
   botName: "sdk-pr-reviewer",
-  webhookEvents: ["pull_request"],
-  deliverReplies: false,
-  progress: { reactions: false },
+  cursorAccount: { repos: ["acme/checkout"] },
   onPullRequest: (ctx, pr) => {
     if (!REVIEW_ACTIONS.has(pr.action) || pr.draft) {
       return null;
     }
+
     return {
       auth: defaultGitHubAuth(ctx),
       title: `Review ${ctx.repository.fullName}#${pr.number}`,
-      context: [
-        "",
-        `Review ${pr.url}. Inspect it first, then submit your verdict with submit_review.`,
-      ],
+      context: `Review ${pr.url}. Inspect it first, then submit your verdict with submit_review.`,
     };
   },
 });
@@ -313,56 +284,24 @@ trigger, both tool calls, and the verdict.
 ## Run options
 
 1. **CLI message**
-
-   ```bash
+  ```bash
    agent-sdk run --dir . --message "Review https://github.com/acme/checkout/pull/42"
-   ```
-
+  ```
 2. **Local replay**
-
-   ```bash
+  ```bash
    agent-sdk github replay https://github.com/acme/checkout/pull/42 \
      --dir . --action opened
-   ```
-
-3. **Forward or `--cursor-events`**
-
-   Pull Cursor events:
-
-   ```bash
-   agent-sdk serve --dir . --cursor-events --repo owner/repo
-   ```
-
-   Forward GitHub webhooks:
-
-   ```bash
-   agent-sdk github forward --dir .
-   ```
-
-   Keep the local `dev` or `serve` process running.
-
-4. **Hosted deployment**
-
-   Deploy once, set the GitHub App secrets, then redeploy:
-
-   ```bash
-   agent-sdk deploy
-   agent-sdk secrets set sdk-pr-reviewer GITHUB_APP_ID GITHUB_APP_PRIVATE_KEY
-   agent-sdk deploy
-   ```
-
-See [GitHub](./guides/github.md) for local event delivery and
-[Deployment](./deployment.md) for hosting.
+  ```
 
 ## Where to go next
 
 - [PR autofixer template](./templates/pr-autofixer.md): drive a PR on a
-  Cursor cloud VM
+Cursor cloud VM
 - [Evals](./evals.md): freeze these two PRs as regression checks so
-  prompt changes can't flip a verdict
+prompt changes can't flip a verdict
 - [Tools](./reference/tools.md): more on typed tools, approvals, and
-  direct calls
+direct calls
 - [GitHub](./guides/github.md): fixtures, forwarding, and pulling
-  events from Cursor
+events from Cursor
 - [Building agents with agents](./building-with-agents.md): have a
-  coding agent extend the project for you
+coding agent extend the project for you

package/docs/reference/channels.md

@@ -8,7 +8,8 @@ description: "The authoring reference for defineChannel, the built-in HTTP chann
 A channel is the surface an agent lives on. The built-in HTTP session
 channel is always mounted. Custom channels declare their own routes
 under `/v1/channels/<id>`. The Slack and GitHub packs are prebuilt
-channels with platform transports. This page is the authoring reference;
+channels with platform transports. GitLab and Bitbucket packs cover their
+hosted and self-managed products. This page is the authoring reference;
 for the walkthrough, see the [Webhooks guide](../guides/webhooks.md).
 
 ## Built-in HTTP channel
@@ -18,22 +19,6 @@ session create, follow-up, stream, stop, the sessions list, approvals,
 deterministic tool calls, health, and info. For the route-by-route
 contract, see the [HTTP API reference](./http-api.md).
 
-Author `agent/channels/http.ts` only to override its defaults:
-
-```ts
-import {
-  bearerAuth,
-  httpChannel,
-  localDevStrict,
-} from "@cursor/july/channels";
-
-export default httpChannel({
-  auth: [localDevStrict(), bearerAuth(process.env.AGENT_TOKEN ?? "")],
-  onMessage: (message, { auth }) =>
-    `[caller ${auth?.principalId ?? "anonymous"}] ${message}`,
-});
-```
-
 ## Define a custom channel
 
 Author `agent/channels/<id>.ts`. The filename is the channel id and the
@@ -134,7 +119,7 @@ Handlers receive the Fetch `Request` and an args object:
 `workspaceFiles`, `workspaceDir`, `cloud` (attach cloud repos for this
 session), `auth` (defaults to the request principal), `state` (starting
 channel state for new sessions), `title` (session display title), and
-`purpose` (`"eval"` skips sticky A/B enrollment).
+`purpose` (`"eval"` marks the session as regression traffic).
 
 ## Events
 
@@ -215,7 +200,19 @@ model turn), `{ task }` (host work), or `null`, and CLI tooling for
 replay and live forwarding. Author `agent/channels/github.ts` with
 `githubChannel()`. Opt-in `progress.commitStatus` and `progress.banner`
 converge a merge-box check and sticky PR comment from default stream
-events. Guide: [GitHub](../guides/github.md).
+events. Supports GitHub.com and GitHub Enterprise Server. Guide:
+[GitHub](../guides/github.md).
+
+**GitLab** (`@cursor/july/channels/gitlab`): verified project hooks for
+merge requests, notes, pipelines, pushes, and custom event types. Supports
+GitLab.com and self-managed GitLab. Author `agent/channels/gitlab.ts` with
+`gitlabChannel()`. Guide: [GitLab](../guides/gitlab.md).
+
+**Bitbucket** (`@cursor/july/channels/bitbucket`): verified repository hooks
+for pull requests, comments, pushes, and custom event types. Supports
+Bitbucket Cloud and Bitbucket Data Center through one normalized hook API.
+Author `agent/channels/bitbucket.ts` with `bitbucketChannel()`. Guide:
+[Bitbucket](../guides/bitbucket.md).
 
 **Deployments** (`@cursor/july/channels/deployments`): pull deploy
 events. Declare `events` and handle each one in `onEvent`. Each event