FrootAI.dev AgentSpace
On this page 6
Start Browser-local

Provider-optional quickstart

Close one governed human-owned work loop in three minutes before connecting any paid model or external runtime.

Status: Available Architecture: F · Foundations Read: 3 min Verified: 2026-11-16

Outcome and trust boundary

In under three minutes you will establish an operating boundary, inspect Launchpad readiness, move a work item through Workstream, attach required evidence, resolve a Decision Gate, and record a verified outcome.

Zero external side effects

In browser-local mode, AgentSpace stores workspace state in your browser. It does not send emails, mutate external SaaS tools, provision cloud resources, or incur model token spend.

1. Complete the operating boundary

  1. Open the AgentSpace workspace

    Navigate to /agent-space from any desktop or mobile browser.

  2. Define workspace identity and accountable owner

    Enter your workspace name, operating purpose, privacy posture, and the named human participant accountable for approvals.

  3. Defer provider credentials intentionally

    Select Defer provider setup. AgentSpace treats model and connector setup as optional until your human workflow and acceptance rules are clear.

  4. Confirm budget and approval defaults

    Review monthly spend caps and write/destructive action guardrails, then complete onboarding.

2. Read Launchpad readiness

Open Launchpad in the left navigation. Instead of a single misleading green light, Launchpad separates three distinct readiness claims:

Readiness dimension What it proves Required in local quickstart?
Operating readiness Recorded boundary, accountable human owner, validated workflow graph, and active budget/approval controls. Yes
First useful loop At least one task has progressed through evidence attachment, decision sign-off, and verified state. Yes (completed in Step 3)
Automation readiness Registered agent participant, ready execution environment, and approved connector data path. Optional — deferred by design

3. Close the first governed loop

  1. Create or select a bounded work item

    Open Workstream, create a task with a concrete Definition of Done, and bind it to a validated workflow and human owner.

  2. Advance work and attach typed evidence

    Move the task to in_progress, open the right-hand inspector, and attach the evidence artifact required by the workflow (for example, source citations or acceptance test notes).

  3. Resolve the linked Decision Gate

    Open Decisions (or resolve inline from the inspector), review attached evidence, record a written rationale, and approve the gate.

  4. Transition to review and verified

    With evidence present and gates approved, move the work item to review and then verified.

Verification checklist

  • Launchpad reports both Operating Readiness and First Useful Loop complete.
  • Workstream preserves the accountable owner, workflow version, Definition of Done, evidence links, and decision sign-off.
  • Ledger displays the append-only audit trail for task creation, evidence attachment, gate approval, and verification.
  • Automation readiness remains clearly marked optional until you explicitly configure a runtime adapter.

Failure and recovery

Why verification can be blocked

If AgentSpace refuses a transition to verified, inspect the blocker banner in the task drawer. It names the exact missing evidence type or unresolved Decision Gate—complete those records rather than bypassing governance.

If local demonstration data becomes cluttered during experimentation, open Settings → Workspace reset to restore the clean baseline fixture without affecting external systems.

Verified against repository suites
tests/backend/workspace-lifecycle.test.ts
Markdown specification

Provider-optional quickstart