The workroom

The conversation, the candidate, and the proof — in one place.

One composer for Build or Knowledge. A rail of durable sessions. And a session view where the conversation, the running result, and the evidence sit side by side.

app.ysra.ai/sessions/organization-invitesReconstruction

Add organization invites

acme/web · ysra/session-invites · $1.84 of $5.00

Ready to reviewOpen PR⋯

Conversation

Add organization invites. Prove the happy path in the browser.
Repository understood0:42
Plan · 4 steps1:10
6 files changed6:31
Native checks8:02
Browser verification9:47
Independent review11:05
Ask for a change — paste a long brief and it becomes a chip
SelectUsePreview ↗Browser use
AcmeOverviewProjectsMembersBilling
Members
Invite member
AKAna Kovač AdminJTJon Tal MemberSMSam Mora Invited
Point-to-edit“Make this the primary button colour.”
EditorPlanReviewChecksShellAudit

Browser verification

Welcome to Acme, Samdesktop 1280×800 · step 4/4

Review

  • ✓Requirementsmet
  • ✓Correctnessno findings
  • ✓Change riskreviewed
  1. 1Session rail
  2. 2Conversation & activity
  3. 3Live preview, point-to-edit
  4. 4Plan, checks, review, audit
  5. 5Delivery under your authority

Three ways through it

A serious work surface, not an admin console.

Build

Start, steer, deliver

  1. 1Choose Build, pick a repository, write the brief
  2. 2Watch activity and the preview update in place
  3. 3Steer mid-run — or point at the preview to request an exact edit
  4. 4Read Checks and Review, then Open PR

Knowledge

Ask, verify, hand off

  1. 1Switch the start screen to Knowledge
  2. 2Ask; open citations in the Sources panel
  3. 3Approve an exact Jira or Slack action
  4. 4Hand to Build — the evidence comes along

Workspace

Set the boundary once

  1. 1Connect GitHub, Slack, and Jira in Integrations
  2. 2Write Rules & instructions and Playbooks
  3. 3Define Managers & automations and Projects
  4. 4Watch spend in Wallet & usage

Inside a session

Six panels. One candidate.

Every panel looks at the same retained candidate, so what you review is what was checked.

Editor
Changed files, per-file line statistics, and comments on the diff.
Plan
The plan — or the full specification in plan-first sessions — and where the work is against it.
Review
Browser verification with screenshots and viewports, and independent review findings.
Checks
Repository-native verification: the project’s own tests, type checks, lint, and build.
Shell
Terminal detail for the commands that ran, when you want it.
Audit
Technical evidence: model calls, tool executions, artifacts, cost, and delivery events.

Workspace

  • Rules & instructions
  • Playbooks
  • Managers & automations
  • Projects
  • Integrations
  • Wallet & usage
  • Settings

Everything that sets Ysra’s boundary lives in one Workspace. Marketing demos show only connections that are live in a workspace.

Give Ysra the outcome. Keep the authority.

Start a software task, ask from company context, or put a repeatable workflow on a schedule.