Unverified Commit d2608c10 authored by Jiwon Choi's avatar Jiwon Choi Committed by GitHub

Document agent upgrades across Next.js (#99293)

### Why?

Document the supported `next upgrade --agent` workflow without
presenting the unfinished `experimental-future` policy as the
recommended path in feature guides.

### How?

- Add a human-facing Agent Upgrade guide and an
`experimental.agentUpgrade` API reference.
- Link the workflow from the App and Pages upgrade docs, CLI reference,
and AI agent guide.
- Document the `security`, `latest`, and `experimental-future` policies
in the upgrade guide, CLI reference, and config reference.
- Keep the dedicated Skills as the recommended path for Cache
Components, Partial Prefetching, and the combined Instant Navigation
migration.
- Explain that version upgrades provide the applicable migration guides
and Skills to the coding agent.
- Show the interactive agent, model, reasoning, Auto-permission, and
worktree prompts.
- Document the non-blocking `next dev` and `next build` reminders, the
DevTools Vulnerability Insight, and the default `security` policy from
#99311.

### Verification

- Prettier passes on all changed documentation files.
- Targeted ESLint passes with no errors.
- Alex reports no new warnings in the changed content.
- Feature guides recommend the dedicated Skills instead of
`experimental-future`.

<!-- NEXT_JS_LLM -->

Closes NAR-944

---------
Co-authored-by: 's avatarAurora Scharff <aurora.sofie@gmail.com>
Co-authored-by: 's avatarClaude Opus 5.5 <noreply@anthropic.com>
parent 8e0700c7
...@@ -482,10 +482,8 @@ yarn next upgrade ...@@ -482,10 +482,8 @@ yarn next upgrade
bunx next upgrade bunx next upgrade
``` ```
Upgrading also updates the documentation bundled inside the `next` package at `node_modules/next/dist/docs/`. New features arrive with their docs, and existing pages pick up new guidance and pitfalls discovered along the way. [AI coding agents](/docs/app/guides/ai-agents) in your project then work from the version you have installed rather than their training data. After an upgrade, you can prompt your agent to catch up: Upgrading also updates the documentation bundled inside the `next` package at `node_modules/next/dist/docs/`. New features arrive with their docs, and existing pages pick up new guidance and pitfalls discovered along the way. [AI coding agents](/docs/app/guides/ai-agents) in your project then work from the version you have installed rather than their training data.
```prompt To have a coding agent perform and verify the upgrade, run `npx next@canary upgrade --agent=latest`. See [Upgrade with a coding agent](/docs/app/guides/upgrading/agent-upgrade) for other policies.
Let's get our Next.js knowledge up to speed, and give me a summary of what's new for you
```
See [Upgrading](/docs/app/getting-started/upgrading) for version guides and manual upgrade steps, or the [preview docs](https://preview.nextjs.org) to explore features before they ship in a stable version. See [Upgrading](/docs/app/getting-started/upgrading) for version guides and manual upgrade steps, or the [preview docs](https://preview.nextjs.org) to explore features before they ship in a stable version.
...@@ -36,6 +36,14 @@ Versions before Next.js 16.1.0 do not support the `upgrade` command and need to ...@@ -36,6 +36,14 @@ Versions before Next.js 16.1.0 do not support the `upgrade` command and need to
npx @next/codemod@canary upgrade latest npx @next/codemod@canary upgrade latest
``` ```
To have a coding agent perform and verify the upgrade, run:
```bash filename="Terminal"
npx next@canary upgrade --agent=latest
```
See [Upgrade with a coding agent](/docs/app/guides/upgrading/agent-upgrade) for other policies and upgrade reminders.
If you prefer to upgrade manually, install the latest Next.js and React versions: If you prefer to upgrade manually, install the latest Next.js and React versions:
```bash package="pnpm" ```bash package="pnpm"
......
...@@ -10,9 +10,10 @@ related: ...@@ -10,9 +10,10 @@ related:
- app/getting-started/upgrading - app/getting-started/upgrading
- app/api-reference/config/next-config-js/agentRules - app/api-reference/config/next-config-js/agentRules
- app/api-reference/config/next-config-js/agentFeedback - app/api-reference/config/next-config-js/agentFeedback
- app/api-reference/config/next-config-js/agentUpgrade
--- ---
AI coding agents may rely on training data that predates the Next.js version installed in a project. To help agents use current APIs and verify their work, Next.js provides and evaluates version-matched documentation, managed project instructions, runtime tools, structured errors, reusable Skills, and optional agent feedback. See the results in the [Next.js agent evaluations](https://nextjs.org/evals). AI coding agents may rely on training data that predates the Next.js version installed in a project. To help agents use current APIs and verify their work, Next.js provides and evaluates version-matched documentation, managed project instructions, agent-guided upgrades, runtime tools, structured errors, reusable Skills, and optional agent feedback. See the results in the [Next.js agent evaluations](https://nextjs.org/evals).
For more background, read about the AI tooling introduced in [Next.js 16.2](/blog/next-16-2-ai) and [Next.js 16.3](/blog/next-16-3-ai-improvements). For more background, read about the AI tooling introduced in [Next.js 16.2](/blog/next-16-2-ai) and [Next.js 16.3](/blog/next-16-3-ai-improvements).
...@@ -108,6 +109,16 @@ Next.js updates only the content between the agent feedback markers and preserve ...@@ -108,6 +109,16 @@ Next.js updates only the content between the agent feedback markers and preserve
Automatic agent feedback is experimental, disabled by default, and available only when [Next.js Telemetry](/telemetry) is enabled. It does not run in CI. See the [`agentFeedback` API reference](/docs/app/api-reference/config/next-config-js/agentFeedback) to enable it. Automatic agent feedback is experimental, disabled by default, and available only when [Next.js Telemetry](/telemetry) is enabled. It does not run in CI. See the [`agentFeedback` API reference](/docs/app/api-reference/config/next-config-js/agentFeedback) to enable it.
## Agent-guided upgrades
`next upgrade --agent` checks for an available upgrade, gathers the version-matched migration guides, and hands the task to a coding agent. The agent applies the changes and verifies the app:
```bash filename="Terminal"
npx next@canary upgrade --agent=latest
```
The experimental [`agentUpgrade`](/docs/app/api-reference/config/next-config-js/agentUpgrade) option shows security upgrade reminders during `next dev` and `next build` by default. See [Upgrade with a coding agent](/docs/app/guides/upgrading/agent-upgrade) for the available policies and workflow.
<span id="step-2-give-agents-runtime-visibility" /> <span id="step-2-give-agents-runtime-visibility" />
## Runtime visibility ## Runtime visibility
......
---
title: Upgrade with a coding agent
nav_title: Upgrade with a coding agent
description: Use a coding agent to upgrade and verify a Next.js app.
version: experimental
related:
links:
- app/getting-started/upgrading
- app/api-reference/cli/next
- app/api-reference/config/next-config-js/agentUpgrade
- app/guides/ai-agents
---
Use `next upgrade --agent` to have a coding agent upgrade and verify your app. The command determines the target version from the configured policy, prepares the relevant migration guides and Skills, and hands the task to the agent.
The command supports App Router and Pages Router projects. Without `--agent`, [`next upgrade`](/docs/app/api-reference/cli/next#next-upgrade-options) runs the interactive codemod workflow instead.
## Start an upgrade
Run the latest upgrade CLI from your app's directory:
```bash filename="Terminal"
npx next@canary upgrade --agent=latest
```
From a workspace root, pass the app directory:
```bash filename="Terminal"
npx next@canary upgrade apps/web --agent=latest
```
Using `next@canary` runs the latest upgrade tooling, even when the app uses an older Next.js version. The CLI reads the version installed in the app and selects a canary target only when the app already uses a canary version. If the project's package manager sets a minimum release age, the CLI uses the newest canary that policy allows.
## Choose a policy
| Policy | Behavior |
| --------------------- | ------------------------------------------------------------------------------------------------------------------- |
| `security` | For an affected stable version, selects the latest safe release in the earliest eligible major. |
| `latest` | Moves stable, RC, beta, and preview apps to npm's `latest` stable release, or a canary app to the `canary` release. |
| `experimental-future` | Applies the `latest` policy, then adopts applicable [Future Defaults](#adopt-future-defaults). |
Omit the policy to use the string value from [`experimental.agentUpgrade`](/docs/app/api-reference/config/next-config-js/agentUpgrade). Otherwise, the command uses `security`:
```bash filename="Terminal"
npx next@canary upgrade --agent
```
`--agent` cannot be combined with `--revision`.
`security` supports stable installations. Canary installations can use `latest` or `experimental-future`. RC, beta, and preview installations can use `latest` to move to a newer stable release. Other prerelease channels are not supported.
### Adopt future defaults
Future Defaults are features Next.js plans to enable by default, such as Cache Components and Partial Prefetching. The `experimental-future` policy is an early version of how upgrades will help apps adopt them, even when the app already uses the latest Next.js version. Moving to a new default then becomes part of the upgrade instead of a separate migration.
For App Router projects on Next.js 16.3 or later, the policy currently prepares the Cache Components guide and adoption Skill:
```bash filename="Terminal"
npx next@canary upgrade --agent=experimental-future
```
Pages Router projects can use it for version upgrades, but it does not offer Cache Components until the project uses the App Router.
To adopt new features today, use their adoption Skills directly. See [Migrating to Cache Components](/docs/app/guides/migrating-to-cache-components#use-the-adoption-skill-recommended) and [Adopting Partial Prefetching](/docs/app/guides/adopting-partial-prefetching#use-the-adoption-skill-recommended).
## What the command does
Before starting an agent session, the CLI checks the installed version, release metadata, and any security data required by the selected policy. It stops with an explanation when no upgrade is needed or it cannot establish a target.
For a ready upgrade, the CLI copies the relevant migration guides into a temporary directory, prepares the applicable Skills, and creates a task for the selected target. For a major upgrade, the task includes the guide for every major version crossed. It also asks the agent to check for duplicate work, use a separate Git worktree when available, run the relevant checks, and verify the result.
The task also asks the agent to save the selected policy as `experimental.agentUpgrade` in `next.config` for future upgrade reminders. To disable reminders, set the option to `false`.
When you run the command inside a coding agent, the CLI prints the task for the current agent to follow. In an interactive terminal, it can start an installed Codex or Claude Code session, or copy the task for another agent. In a non-interactive terminal, it prints the task.
## Choose how to run the agent
When you start the command from an interactive terminal, it asks which installed agent to use. For a new agent session, you can also choose its model, reasoning effort, whether to use Auto permissions, and whether to use a separate Git worktree. The available choices depend on the selected agent and CLI version.
The terminal shows prompts similar to the following:
```txt filename="Terminal"
Multiple coding agents detected. Which one would you like to use?
Use ↑/↓ to choose, then press Enter.
❯ Continue with Codex
Continue with Claude Code
Copy prompt for another coding agent
Cancel
Which Codex model should run the upgrade?
❯ Terra
Sol
Cancel
Which reasoning effort should the upgrade use?
low
medium
❯ high
xhigh
max
ultra
Cancel
Use Auto permission mode for Codex?
❯ Yes
No, ask for approval
Cancel
Open the upgrade in a separate Git worktree?
❯ Yes
No
```
When you run the command from an existing coding agent, it provides the prepared task to that agent instead. The agent keeps the model, reasoning effort, and permissions already configured for its session.
## Configure upgrade reminders
Upgrade reminders are enabled by default with the `security` policy. Set [`experimental.agentUpgrade`](/docs/app/api-reference/config/next-config-js/agentUpgrade) to choose another policy or disable reminders:
```ts filename="next.config.ts"
import type { NextConfig } from 'next'
const nextConfig: NextConfig = {
experimental: {
agentUpgrade: 'latest',
},
}
export default nextConfig
```
Set the option to `false` to disable reminders.
The option does not upgrade the app automatically. In an interactive terminal, `next dev` or `next build` continues while the reminder is open and buffers its output. **Upgrade now** stops the command before starting the upgrade. **Skip** returns to the running command and replays that output. **Skip until next version** dismisses the reminder for the installed version. See [Reminder behavior](/docs/app/api-reference/config/next-config-js/agentUpgrade#reminder-behavior) for details.
When a coding agent encounters a reminder, it reports the available upgrade and can continue the original task after retrying the command.
During `next dev`, Next.js DevTools can also show a **Vulnerability Insight** when the installed version is affected by a known security vulnerability. The insight provides a copyable prompt for starting a `security` upgrade with a coding agent.
The CLI needs access to release metadata and, for stable targets, security advisory data. If it cannot establish a target, it reports the reason without starting an agent session.
...@@ -26,6 +26,8 @@ Replacing `<transform>` and `<path>` with appropriate values. ...@@ -26,6 +26,8 @@ Replacing `<transform>` and `<path>` with appropriate values.
Upgrades your Next.js application, automatically running codemods and updating Next.js, React, and React DOM. Upgrades your Next.js application, automatically running codemods and updating Next.js, React, and React DOM.
To have a coding agent run the codemods, complete the remaining migration work, and verify the app, run `npx next@canary upgrade --agent=latest` instead. See [Upgrade with a coding agent](/docs/app/guides/upgrading/agent-upgrade) for details.
```bash filename="Terminal" ```bash filename="Terminal"
npx @next/codemod upgrade [revision] npx @next/codemod upgrade [revision]
``` ```
......
...@@ -4,4 +4,4 @@ nav_title: Upgrading ...@@ -4,4 +4,4 @@ nav_title: Upgrading
description: Learn how to upgrade to the latest versions of Next.js. description: Learn how to upgrade to the latest versions of Next.js.
--- ---
Learn how to upgrade to the latest versions of Next.js following the versions-specific guides: Learn how to upgrade Next.js, with a coding agent or by following a version-specific guide:
...@@ -6,58 +6,34 @@ description: Upgrade your Next.js Application from Version 15 to 16. ...@@ -6,58 +6,34 @@ description: Upgrade your Next.js Application from Version 15 to 16.
{/* The content of this doc is shared between the app and pages router. You can use the `<PagesOnly>Content</PagesOnly>` component to add content that is specific to the Pages Router. Any shared content should not be wrapped in a component. */} {/* The content of this doc is shared between the app and pages router. You can use the `<PagesOnly>Content</PagesOnly>` component to add content that is specific to the Pages Router. Any shared content should not be wrapped in a component. */}
## Use an AI agent (recommended) ## Use a coding agent (recommended)
An AI coding agent can run the mechanical parts of the upgrade, inspect the diff, fix follow-up breakages, and verify the app. The prompt below asks the agent to read version-matched docs, use the codemods where appropriate, explain important changes, and verify the result. Some runtime verification tools are only available after the app is upgraded. Run the latest upgrade CLI from your app's directory:
Give the agent this prompt: ```bash filename="Terminal"
npx next@canary upgrade --agent=latest
```prompt
Upgrade this app to Next.js 16.
Before editing code, make sure AGENTS.md points at version-matched Next.js docs. If it is missing or outdated, follow [Set up AI agent docs](/docs/app/guides/upgrading/version-16#set-up-ai-agent-docs), then read AGENTS.md.
Then follow the [Next.js 16 upgrade guide](/docs/app/guides/upgrading/version-16) as the source of truth for the migration. Use the [codemod](/docs/app/guides/upgrading/version-16#using-the-codemod) when you're ready to run the mechanical upgrade.
Briefly explain the upgrade plan in user-facing language before making broad changes. Follow the documented defaults and keep moving unless the guide requires a project-specific decision, the change is destructive, credentials or environment setup are missing, or the correct migration is ambiguous. Keep the migration scoped to the upgrade, inspect the diff, run the relevant checks, and fix remaining breaking changes.
After the app is upgraded, use the runtime verification flow from the [AI Coding Agents guide](/docs/app/guides/ai-agents) to confirm it still works. Prefer the `next-dev-loop` skill when it is available (Next.js 16.3 or later with Turbopack); otherwise fall back to the best available `next dev`, browser, and build checks. Open the key interactive UI states and check the Next dev indicator plus browser and server logs. Summarize what changed, what was verified, and what could not be verified.
Before finishing, repeat the post-upgrade check in [Set up AI agent docs](/docs/app/guides/upgrading/version-16#set-up-ai-agent-docs) so the project is ready for future agent work.
``` ```
The CLI prepares the Next.js 16 migration guides and codemod command for the agent, then asks it to apply the changes and verify the app. See [Upgrade with a coding agent](/docs/app/guides/upgrading/agent-upgrade) for details.
## Or upgrade manually ## Or upgrade manually
Upgrading manually follows a few steps, in order: Upgrading manually follows a few steps, in order:
1. [Set up AI agent docs](#set-up-ai-agent-docs) if you use an assistant now or want future agent work grounded in version-matched docs. 1. [Set up AI agent docs](#set-up-ai-agent-docs) if you use a coding agent now or want future agent work grounded in version-matched docs.
2. [Run the upgrade codemod](#using-the-codemod). 2. [Run the upgrade codemod](#using-the-codemod).
3. If you prefer not to run the codemod, [install packages manually](#install-packages-manually). 3. If you prefer not to run the codemod, [install packages manually](#install-packages-manually).
4. Continue through the breaking changes below, run the relevant checks, and fix any remaining issues. 4. Continue through the breaking changes below, run the relevant checks, and fix any remaining issues.
## Set up AI agent docs ## Set up AI agent docs
The prompt above asks the agent to do this before it edits code. You can also prepare the project yourself before starting the upgrade. See the [AI Coding Agents guide](/docs/app/guides/ai-agents) for the full setup. Before upgrading, point `AGENTS.md` at version-matched Next.js docs so a coding agent can help with the remaining steps:
```bash filename="Terminal" ```bash filename="Terminal"
npx @next/codemod@canary agents-md npx @next/codemod@canary agents-md
``` ```
After upgrading, verify `AGENTS.md` still points at the docs for the installed Next.js version. On Next.js 16.2 and later, that should be the bundled docs in `node_modules/next/dist/docs/`. If the pre-upgrade setup downloaded docs into `.next-docs/`, update `AGENTS.md` to point at the bundled docs, then remove `.next-docs/` once nothing references it. After upgrading, check that `AGENTS.md` points at the docs bundled with the installed version in `node_modules/next/dist/docs/`. On Next.js 16.2 and later, `next dev` keeps this block up to date when it detects a coding agent. If the setup downloaded docs into `.next-docs/`, remove that directory once nothing references it. See [Version-matched documentation](/docs/app/guides/ai-agents#version-matched-documentation) for the managed block and setup details.
The managed block should look like this:
```md filename="AGENTS.md"
<!-- BEGIN:nextjs-agent-rules -->
## This is NOT the Next.js you know
This version has breaking changes — APIs, conventions, and file structure may all differ from your training data. Read the relevant guide in `node_modules/next/dist/docs/` (resolved from this file's directory; in monorepos the `next` package may not be visible from the repo root) before writing any code. Heed deprecation notices.
This block is written and re-added by `next dev` — verify at `node_modules/next/dist/server/lib/generate-agent-files.js`. Removing it from a diff only re-creates the uncommitted change; committing it with your work keeps the tree clean.
<!-- END:nextjs-agent-rules -->
```
## Using the codemod ## Using the codemod
......
...@@ -10,7 +10,7 @@ related: ...@@ -10,7 +10,7 @@ related:
The `experimental.agentFeedback` option controls whether `next dev` creates and updates instructions that let detected AI coding agents prepare Next.js issue reports for your review. It is disabled by default and requires [Next.js Telemetry](/telemetry) to be enabled. Agent feedback does not run in CI. The `experimental.agentFeedback` option controls whether `next dev` creates and updates instructions that let detected AI coding agents prepare Next.js issue reports for your review. It is disabled by default and requires [Next.js Telemetry](/telemetry) to be enabled. Agent feedback does not run in CI.
Set `experimental.agentFeedback` to `true` to enable this behavior: New apps created with the recommended `create-next-app` settings enable agent feedback in the generated Next.js config. For other apps, set the option manually:
```ts filename="next.config.ts" switcher highlight={5} ```ts filename="next.config.ts" switcher highlight={5}
import type { NextConfig } from 'next' import type { NextConfig } from 'next'
......
---
title: agentUpgrade
description: Configure coding agent upgrades and reminders.
version: experimental
related:
links:
- app/guides/upgrading/agent-upgrade
- app/guides/ai-agents
- app/api-reference/cli/next
---
The `experimental.agentUpgrade` option selects the default policy for [`next upgrade --agent`](/docs/app/guides/upgrading/agent-upgrade) and controls upgrade reminders during `next dev` and `next build`. It uses the `security` policy by default.
```ts filename="next.config.ts" switcher highlight={5}
import type { NextConfig } from 'next'
const nextConfig: NextConfig = {
experimental: {
agentUpgrade: 'latest',
},
}
export default nextConfig
```
```js filename="next.config.js" switcher highlight={4}
/** @type {import('next').NextConfig} */
const nextConfig = {
experimental: {
agentUpgrade: 'latest',
},
}
module.exports = nextConfig
```
The option accepts these values:
| Value | Behavior |
| --------------------- | ------------------------------------------------------------------------------------------------------------------------------------------ |
| `false` | Disables upgrade reminders. |
| `security` (default) | Checks stable installations for security advisories and recommends a safe upgrade when one is available. |
| `latest` | Recommends a newer major or minor release on the app's current stable or canary channel. |
| `experimental-future` | Uses the `latest` policy and also recommends applicable [Future Defaults](/docs/app/guides/upgrading/agent-upgrade#adopt-future-defaults). |
The option does not upgrade the app automatically. It only controls reminders and the policy used when `next upgrade --agent` does not include a value.
## Reminder behavior
In an interactive terminal, an eligible reminder during `next dev` or `next build` offers these actions. The command continues behind the prompt and buffers its output while you decide.
- **Upgrade now** stops the current command and starts `next upgrade --agent` with the configured policy.
- **Skip** returns to the running command and replays its buffered output.
- **Skip until next version** saves the dismissal for the installed version and policy.
If you don't choose within ten seconds, or the buffered output grows past about 10 MiB, the reminder skips automatically.
When a coding agent runs `next dev` or `next build`, the first eligible reminder stops the command with instructions to report the upgrade. Retrying the same command promptly continues the original task with a warning.
Reminders require the installed Next.js version to support `experimental.agentUpgrade`. Running the current canary upgrade CLI does not add reminders to an older installation.
During `next dev`, Next.js DevTools can also show a **Vulnerability Insight** when the installed version is affected by a known security vulnerability. The insight provides a copyable prompt for starting a `security` upgrade with a coding agent.
## Version History
| Version | Changes |
| --------- | ------------------------------------------------------- |
| `v16.4.0` | `experimental.agentUpgrade` configuration option added. |
...@@ -216,12 +216,13 @@ To ensure `next-env.d.ts` is present before type-checking run `next typegen`. Th ...@@ -216,12 +216,13 @@ To ensure `next-env.d.ts` is present before type-checking run `next typegen`. Th
The following options are available for the `next upgrade` command: The following options are available for the `next upgrade` command:
| Option | Description | | Option | Description |
| ----------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------- | | ----------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| `-h, --help` | Show all available options. | | `-h, --help` | Show all available options. |
| `[directory]` | A directory with the Next.js application to upgrade. If not provided, the current directory will be used. | | `[directory]` | A directory with the Next.js application to upgrade. If not provided, the current directory will be used. |
| `--revision <revision>` | Specify a Next.js version or tag to upgrade to (e.g., `latest`, `canary`, `15.0.0`). Defaults to the release channel you have currently installed. | | `--revision <revision>` | Specify a Next.js version or tag to upgrade to (e.g., `latest`, `canary`, `15.0.0`). Defaults to the release channel you have currently installed. |
| `--verbose` | Show verbose output during the upgrade process. | | `--verbose` | Show verbose output during the upgrade process. |
| `--agent [type]` | [Upgrade with a coding agent](/docs/app/guides/upgrading/agent-upgrade) using `security`, `latest`, or `experimental-future`. Defaults to [`experimental.agentUpgrade`](/docs/app/api-reference/config/next-config-js/agentUpgrade), or `security`. Cannot be combined with `--revision`. |
### `next analyze` options ### `next analyze` options
......
...@@ -3,4 +3,4 @@ title: Upgrading ...@@ -3,4 +3,4 @@ title: Upgrading
description: Learn how to upgrade to the latest versions of Next.js. description: Learn how to upgrade to the latest versions of Next.js.
--- ---
Learn how to upgrade to the latest versions of Next.js following the versions-specific guides: To have a coding agent perform and verify an upgrade, run `npx next@canary upgrade --agent=latest`. See [Upgrade with a coding agent](/docs/app/guides/upgrading/agent-upgrade) for details. To upgrade manually, follow a version-specific guide:
Markdown is supported
0% or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment