Quickstart

Set up one backend project in Sandbox and verify its first observation. Seamward discovers the Integration boundaries, proposes source and remote changes, and keeps every write behind review. Incident detection and repair start after real observations exist.

Before you begin

You need a Seamward workspace invitation, Node.js 22 or later to run the CLI, and a backend with one webhook or external API operation that can receive safe test traffic. The backend can use supported Node.js, Laravel 12, or Laravel 13 source. Laravel automation also requires PHP 8.3 or later. The reviewed apply installs the published alpha PHP and Laravel collectors from Packagist.

Seamward is in early access. If you do not have an account yet, request early access; accepted teams receive an owner invitation by email. Signed-in users with verified email can create another workspace from the workspace switcher.

Create your account

Open the workspace invitation email. Invitations are valid for seven days; ask the sender for a new one if it has expired.

The invitation link opens the account setup page with your email address fixed. Enter your name, choose a password of 12 characters or more, and create the account. Then open the verification email and verify the address; sign-in is blocked until you do.

Invite later members from Workspace settings → Members.

Use a separate workspace for each project or business. Open the workspace switcher and select Create workspace to add one under your account's plan. The Developer plan includes three active workspaces. Paid plans include multiple workspaces under one account. Plan usage is shared across its workspaces.

Read the workspace setup guide.

Install and authorize the CLI

Install the command once:

npm install -g @seamward/cli@alphaseamward login

Login is the only command that opens the browser. Press Enter, sign in, select the workspace, keep Sandbox selected, and approve access. The Seamward success screen tells you to return to the terminal. The CLI then completes the authorization without using a browser callback page.

Run seamward login before seamward setup; setup reuses the approved Sandbox session and stays entirely in the terminal.

Set up the project

From the deployable backend service directory, run:

seamward setup

The command does not open a browser and never reads or edits an environment file. It installs project-scoped MCP configuration. Restart the coding agent, then send one prompt:

Set up Seamward in this project.

The setup handoff also offers review-only, status, and local credential-review prompts. See Choose your next prompt. These alternatives do not grant approval to apply changes or save credentials.

The same prompt detects the project's runtime and chooses the Node.js or Laravel collector internally. The agent discovers inbound and outbound HTTP, webhook, queue, and scheduled feed boundaries. It proposes Integration names and contracts from the code, previews every source and remote change, applies approved source changes, runs the repository verification command, connects the reviewed Sandbox Integrations, and hands off local credentials to your terminal. You do not copy setup IDs or create Integrations manually.

Review the complete automatic setup lifecycle.

Verify the observation

In your project terminal, save and check Sandbox credentials:

seamward setup credentials

Select the ignored .env or .env.local file you use, review the variable names, and approve saving. The CLI then checks all saved pairs with Seamward, without starting your application. CONNECTION VERIFIED means those credentials matched the expected Integrations and environment now. It does not prove application traffic. If checking fails, the saved file remains intact; resolve the reported cause and run seamward setup verify to repeat only the connection check.

Start your application normally with the selected file loaded. If the agent reports waiting_for_traffic, run the safe local request, webhook, queue, or notification script that exercises each reviewed boundary. Ask the agent to check setup status again. The quickstart is complete when every Integration reports an accepted observation.

Deploy to Live

Live reuses the verified source. It does not instrument the server or require running the setup agent on the production host:

seamward login --liveseamward setup --liveseamward deployment env --live

Review the remote Live changes, store the printed values in the hosting provider's secret manager, and deploy the same source revision. Do not add SEAMWARD_ENVIRONMENT; each Connection key and ingest token already selects the correct Integration and environment.

Checking this status in the browser does not require a workspace API key. Workspace API keys remain an advanced option for headless automation and CI. The normal setup flow uses short-lived, browser-approved CLI authorization.

Diagnose a missing observation.