Firecrawl is now available on the Vercel Marketplace, allowing Vercel teams to power AI agents and applications with structured web data without managing crawling infrastructure.

This integration helps developers scrape websites into LLM-ready formats, search and retrieve full page content, and interact with dynamic pages for retrieval and agent workflows.

Key capabilities include:

• Scrape pages into markdown, HTML, structured data, or screenshots

• Search the web and retrieve full page content in a single call

• Interact with dynamic websites using AI prompts or code

Get started with Firecrawl on the Vercel Marketplace.

This week we are gradually rolling out an update to Vercel Microfrontends routing for aliases and branch-assigned domains.

Aliases inherit Microfrontends routing
Aliasing a Microfrontends URL with vc alias now preserves the full microfrontends routing config from the source deployment. Previously, the new alias only inherited the deploymentId. Update to the latest Vercel CLI to pick up the change.

Branch domains route across all projects
A project domain assigned to a git branch now routes to that branch in every project in the Microfrontend that shares the branch name. Previously, the domain only routed to that branch within the project that owned the domain.

See the Microfrontends documentation for details on routing, aliases, and domain assignment.

You can now access anomaly alerts and their details directly through the Vercel CLI.

With the vercel alerts command, you can list all alerts for a team or given project. For each alert, you can view the start time, the type of alert, and whether or not the alert is still active.

With the --ai option, the AI investigation results appear alongside each alert. You and your agent can act on alerts without leaving the terminal.

vercel alerts --ai

Available on Observability Plus.

Learn more about vercel alerts in the CLI documentation.

Qwen 3.7 Max from Alibaba is now available on Vercel AI Gateway. The model is designed as an agent foundation, with capabilities spanning coding, office workflow automation, and long-horizon autonomous execution.

Qwen 3.7 Max shows improvements in frontend prototyping and complex multi-file engineering. The model supports office and productivity tasks through multi-agent orchestration and sustains coherent reasoning across long-horizon tool-calling sessions.

To use Qwen 3.7 Max, set model to alibaba/qwen-3.7-max in the AI SDK.

1
import { streamText } from 'ai';
2

3
const result = streamText({
4
  model: 'alibaba/qwen3.7-max',
5
  prompt: `Refactor this service into smaller modules and update callers across the repo.`,
6
});

AI Gateway provides a unified API for calling models, tracking usage and cost, and configuring retries, failover, and performance optimizations for higher-than-provider uptime. It includes built-in custom reporting, observability, Bring Your Own Key support, and intelligent provider routing with automatic retries.

Learn more about AI Gateway, view the AI Gateway model leaderboard or try it in our model playground.

You can now configure weighted traffic splits for Vercel Flags with the new vercel flags split command in the Vercel CLI. This allows you to send a percentage of traffic to one variant and the rest to another.

Run the command interactively, or pass the environment, bucketing attribute, and variant weights as flags:

1
vercel flags split redesigned-checkout \
2
  --environment production \
3
  --by user.id \
4
  --weight off=95 \
5
  --weight on=5

Update to the latest version of the Vercel CLI and read the documentation to get started.

Grok Build 0.1 is now available on Vercel AI Gateway.

This is a beta coding model trained for agentic coding, currently in early access, and powers the Grok Build CLI app. Reasoning effort is not configurable, and there is no non-reasoning mode.

To use Grok Build 0.1, set model to xai/grok-build-0.1 in the AI SDK.

1
import { streamText } from 'ai';
2

3
const result = streamText({
4
  model: 'xai/grok-build-0.1',
5
  prompt: 'Refactor this module to use async/await and add tests.',
6
});

AI Gateway provides a unified API for calling models, tracking usage and cost, and configuring retries, failover, and performance optimizations for higher-than-provider uptime. It includes built-in custom reporting, observability, Bring Your Own Key support, and intelligent provider routing with automatic retries.

Learn more about AI Gateway, view the AI Gateway model leaderboard or try it in our model playground.

Chat SDK now ships a built-in AI SDK toolset through the new chat/ai subpath. One createChatTools(chat) call wires Chat SDK's read and write actions into your agent.

import { Chat } from "chat";
import { createChatTools } from "chat/ai";
import { ToolLoopAgent } from "ai";

const chat = new Chat({ userName: "mybot" /* ... */ });

const agent = new ToolLoopAgent({
  model: "openai/gpt-5.4",
  instructions: 'You are a helpful assistant.'
  tools: createChatTools(chat, { preset: "messenger" }),
});

• Approval by default: write tools are gated by a requireApproval option.

• Presets: reader, messenger, and moderator scope the toolset.

• Lazy loading: only the tools your preset allows are constructed.

toAiMessages and its supporting types have moved to chat/ai. The previous chat re-exports are flagged @deprecated.

Read the documentation to get started, or try one of our templates.

You can now read the parent issue or pull request when your bot is mentioned in a Linear or GitHub comment. message.subject resolves to that parent with title, status, URL, and the full typed payload.

bot.onNewMention(async (thread, message) => {
  const subject = await message.subject;

  if (subject) {
    await thread.post(
      `This is about: ${subject.title} (${subject.status})\n${subject.url}`
    );
  }
});

message.subject is cached per message, so repeated access only hits the API once. It resolves to null on Slack and other chat platforms, where there's no parent resource.

Link to headingDirect access to platform SDKs

The GitHub, Linear, and Slack adapters now expose their underlying platform SDKs. Use them to extend your bot by calling provider APIs directly.

// Add a "triaged" label to issue #42
const { octokit } = bot.getAdapter("github");
await octokit.rest.issues.addLabels({ owner: "vercel", repo: "chat", issue_number: 42, labels: ["triaged"] });

// Create a new issue in a team
const { linearClient } = bot.getAdapter("linear");
await linearClient.createIssue({ teamId: "TEAM_ID", title: "Investigate flaky test" });

// Pin a message in a channel
const { webClient } = bot.getAdapter("slack");
await webClient.pins.add({ channel: "C123ABC", timestamp: "1234567890.123456" });

The previous .client getter remains as a @deprecated alias on the adapters.

Read the documentation to get started, or explore one of our templates.