Start with Ysra

Ysra Developer

From engineering objective to reviewable change.

Connect a repository and give Ysra an engineering objective. Stay in the loop when you want; come back to a tested candidate when you don’t.

Start a software task →See the proof
app.ysra.ai/sessions/organization-invitesSimulation

Add organization invites

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

Ready to reviewOpen PR

Conversation

Add organization invites. Admins invite by email; invitees land in the right workspace. Prove the happy path in the browser.

  1. Brief receivedYsra has the brief, the repository, and a $5.00 limit.
  2. Repository understoodRead the app structure, auth, and how settings pages are built before editing.
  3. Plan activeFour steps, with the acceptance criterion taken from your brief.
  4. Files changedAdded the invite model and routes; extended the members page.
  5. Native checksRan the repository’s own test, typecheck, lint, and build.
  6. Browser scenarioInvited a member, opened the link, accepted, reached the workspace.
  7. Independent reviewReviewed against the request, separately from the implementation.
  8. Ready for reviewCandidate retained with its evidence. Delivery waits for you.
SelectUselocalhost:3000
AcmeOverviewProjectsMembersBilling
Welcome to Acme, SamYou joined as Member

Browser verification

4 of 4 steps · desktop 1280×800

Review

  • ✓Requirementsmet
  • ✓Correctnessno findings
  • ✓Change riskauth surface reviewed
  • ✓Evidencebound to candidate

candidate 7f3a2c1 · evidence 11 items

Illustrative simulation of a Developer session. Repository, names, and figures are fictional.

The path

Understand. Plan. Build. Run. Inspect. Repair. Verify. Deliver.

The sequence matters less than the fact that it stays attached to one exact candidate — with the proof and a way back.

  1. 01

    Connect or choose a repository

    Continue an existing codebase or start a new private repository. Ysra works in an isolated workspace on its own branch.

  2. 02

    Give it the whole brief

    Long requirements, attachments, constraints, and acceptance criteria. Paste a long brief and it becomes a chip.

  3. 03

    Agent mode — or plan firstPlan first: rolling out

    Agent mode starts immediately and reports back with a candidate you can review. Plan-first sessions let you approve a full specification before work begins.

  4. 04

    Understand before changing

    Ysra reads the structure, conventions, and the code a change will touch before it edits anything.

  5. 05

    Edit, run, inspect, repair

    It edits files, runs commands, starts services, looks at the running result, and repairs what fails — on one durable candidate.

  6. 06

    Evidence from the repository itself

    Native tests, type checks, lint, and builds. For runnable web products, browser workflows with screenshots.

  7. 07

    Independent review

    The candidate is assessed against what you asked for, separately from the implementation that produced it.

  8. 08

    Review everything together

    The diff, the preview, the cost, and the Build Report — in one workroom, or on your phone.

  9. 09

    Deliver when you are ready

    Commit, push, or open a pull request only under the delivery authority you grant. Supported deployments are planned from the reviewed candidate, per workspace.

  10. 10

    Resume, rewind, export

    Checkpoints keep retained work. Interruptions pause the session — they don’t erase it — and partial work stays inspectable.

Work profile

Choose the bar. Choose the budget.

Every session carries a profile. Try the controls — each explains what it actually changes.

Session profile

Reconstruction
QualityHow complete should the result be?
ComputeHow much bounded agent work to allocate?
ReasoningHow deeply should it think per step?
ReviewWhat should review decide?
Browser verificationEnabled

acme/web · agent · Beta · Medium reasoning · Balanced · main → new branch

Quality

Beta — Complete core workflows and engineering gates

Core workflows are completed and the repository’s engineering gates are expected to pass.

Compute

Balanced — Normal evidence and repair budget

The default: enough headroom to investigate, verify, and repair.

Reasoning

Medium — Balanced depth

A sensible default for most engineering work.

Review

Advisory — Findings reported with the candidate

Findings are attached to the Build Report; you decide what to do with them.

A higher setting buys more room to work. It does not guarantee correctness — the evidence does.

Browser verification

Not code that looks plausible. Behaviour that was exercised.

For runnable web products, Ysra can run the product, exercise the workflow in a browser, and attach the evidence to the exact candidate it reviewed. It applies where there is a browser product to run and the review profile calls for it.

Example verification replay
localhost:3000/dashboard
Your tasksNew task
  • Draft Q4 plan
  • Review onboarding copy
  • Call the venue about Friday

↻ reloaded · 200 OK · item still present

Candidate 7f3a2c1Screenshot 6/6Requests observed: POST /api/tasks · 201

What teams hand to Developer

Engineering outcomes, not autocomplete.

Feature work

Issues and product briefs into reviewable changes.

Use case →

Debugging and regression repair

Reproduce, find the cause, fix narrowly.

Use case →

Refactors and migrations

Structural change with the repository’s own checks as the guard.

API and backend work

Endpoints, data access, and the behaviour around them.

Web application workflows

User journeys exercised in a real browser where applicable.

New product repositories

Start from a neutral private repository and build from a complete brief.

Use case →

Maintenance and technical debt

The backlog nobody gets to, handled with review attached.

Repository research

Ask how something works and get an explanation grounded in the code.

Recovery

An interruption should pause the work — not erase it.

  • CheckpointsResume a durable session from where it stopped, or rewind to a checkpoint and take another path.
  • Budgets that holdThe session limit is a real authorization. Ysra stops before the next paid call and asks.
  • Honest partial resultsWhen Ysra cannot prove a requirement, it says so, names what remains, and preserves the candidate.
  • Your work, exportablePreserved work can be downloaded or delivered as a branch, even when it is unfinished.

Hand Ysra the issue.
Keep the merge button.

Connect a repository, set a budget, and review a candidate with its evidence attached.

Start a software task →Talk to us