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 and three integrations. Pro includes multiple workspaces under one account. Plan usage is shared across its workspaces.

Read the workspace setup guide.

Install and authorize project setup

Install the command and authorize the separate project setup channel:

npm install -g @seamward/cli@alphaseamward setup authorize

Confirm the terminal code in the browser, select the workspace, and approve Sandbox project setup. Return to the terminal after authorization succeeds. Account management uses a separate seamward login and is not required for this agent setup flow.

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

Reuse the verified source revision. In the dashboard, open the Integration and configure its Live connection. Review selected contract and rule copying; copied rules start disabled. A workspace owner or admin places the Live Connection key and one-time ingest token directly in hosting secrets under the exact names used by your instrumentation. Deploy the source and check for the intended observation in Live.

Do not add SEAMWARD_ENVIRONMENT. The configured Connection key and ingest token select the exact connection and mode. Management CLI login does not affect SDK routing and does not export production secrets.

Next: independent management CLI, manual dashboard and SDK integration, or automatic setup details.