F Forsig Developer console
Docs
Private Beta

Developer access

Sign up the first time with the email and access code from your admin. After that, sign in with email and password.

Private Beta

Create a new password

Use at least 10 characters with uppercase, lowercase, number, and special character.

F Dashboard
Docs Need help?

Inbox

Operational queue for active, test, and shadow approval requests. Open a row to inspect context and send a signed decision.

Dashboard

Monitor approval activity, jump to operational work, and finish setup tasks.

Recent escalations

Latest requests visible in this workspace.

O

Finish onboarding

Generate a key, copy a setup snippet, and approve a test escalation when you are ready.

Onboarding wizard

Generate a key, install Forsig, then approve a test escalation.

1Generate API keyShown once, then safely masked.

Create a server-side key and store it as FORSIG_API_KEY.

2Install SDK or AI agentCopy Node, Python, cURL, or framework examples.

Use these examples as a guide for creating Forsig checkpoints from your app.

No secrets in review context. Send only what a reviewer needs. Avoid API keys, passwords, payment details, full customer records, and unnecessary personal data.
Open docs
3Approve test escalationSee the exact reviewer workflow before going live.

Create a test escalation, open it in Inbox, then approve, reject, edit, or take over. The agent receives a structured JSON decision.

AI installer

Let your coding assistant install Forsig.

Describe the risky actions you want controlled. Forsig drafts a production-ready prompt for Codex, Cursor, or Claude Code that finds the right execution points, adds checkpoints, tests decisions, and starts safely in shadow mode.

1Choose riskRefunds, emails, deployments, spend, or custom tool calls.
2Pick rolloutStart in shadow mode, then switch to active approval.
3Paste promptYour coding assistant adds Forsig with tests and a small diff.

Shadow simulations

Shadow mode logs where approval would have been required without blocking your agent.

Select an escalation to review.

Agents

Agents group escalations, default reviewers, environment, and audit history. Use development or staging first, then create a production agent when the checkpoint is trusted.

API keys

Create keys for server-side integrations. Full keys are shown once, then only a prefix is visible.

Audit trails

Review every key, agent, escalation, shadow simulation, and decision event in one exportable timeline.

Select an audit event to review.

Settings

Workspace

Log preferences

Audit trails always include real, test, and shadow events for review. This setting only changes the Inbox list.

Email notifications

Default reviewers are used by setup snippets, AI installer prompts, and new escalations unless an agent overrides them.

Team invites

Invite UI is ready for beta. Backend role enforcement should map Owner, Admin, Reviewer, Developer, and Viewer before team launch.

Usage and referral

Free beta includes one workspace, one starter workflow, and limited monthly approvals. Invite another builder to extend beta limits after referral tracking is enabled.

My profile

Account

Create agent

Agents group escalations by workflow, environment, reviewer defaults, and audit history. Start with development or staging first.

Create API key

Store this key securely. Forsig will show the full value once, then only the masked prefix.

API key created

Copy this key now

This is the only time Forsig will show the full API key.

Next: run a checkpoint

Set this key as an environment variable, then open Dashboard for copy-paste code.