Screenshot-led product tour

The AI said done. Here’s the receipt.

Don’t grade an agent by the confidence of its final message. Grade the diff, the build, the running app, and the logs. Every capture below comes from the current Adios interface with demo project data.

Create a workspace Read the feature overview

Eight screens. One repository.

The receipt is longer than the agent’s ‘done’ message.

Follow the same demo project through the real Explorer, agent plan, Git diff, build output, live preview, runtime logs, secret policy, and production boundary.

Product proofActual Adios interface, captured at 1440 × 900 with deterministic demo project data. No controls were drawn for this page.

Adios Workspace Explorer with the demo repository tree and adios.yaml open in the source editor

Actual Adios UI · demo data

01Explorer + editor

Start with the repo, not a blank chat.

The agent works against the same project tree you review. Open the manifest, inspect the source, and keep the current branch and uncommitted state in view.

Repository tree and active branch
Editable source and deployment manifest

Adios AI Agent pane showing a saved conversation and a three-step background plan

Actual Adios UI · demo data

02AI agent

Watch the work happen in steps.

A persistent conversation is only half the story. The background plan shows what passed, what is running, and what still needs verification before anyone calls the job done.

Saved messages and focused workspace context
Visible plan steps, status, model, and run state

Adios Source Control pane with staged and unstaged files beside a full Git diff

Actual Adios UI · demo data

03Source control

A prompt is not a code review.

See exactly what changed before it becomes a commit. Staged and unstaged files, branch state, sync actions, and the full diff stay attached to the workspace.

Staged and unstaged changes
Full diff plus fetch, pull, push, and commit controls

Adios Build History pane showing a successful artifact and timestamped production build output

Actual Adios UI · demo data

04Build history

‘Looks right’ is not a passing build.

The build has an ID, a status, a timestamp, and its own output. When it fails, you have the evidence; when it passes, you have the artifact.

Versioned build artifact and status
Timestamped dependency, compile, and check output

Adios Browser Preview pane showing a running demo application and responsive viewport controls

Actual Adios UI · demo data

05Browser preview

Open the app. Kick the tires.

The current workspace opens in a live preview with desktop, tablet, and mobile controls. Reload after a change, follow a path, or open the app in its own tab.

Live workspace runtime inside the product
Desktop, tablet, mobile, reload, and open controls

Adios Workspace Logs pane with timestamped development runtime requests and health output

Actual Adios UI · demo data

06Workspace logs

When it breaks, follow the evidence.

Stop guessing which terminal had the useful line. Development and build output stay with the repository, preview, and artifact that produced it.

Separate development and build streams
Timestamped, search-backed output with retention state

Adios Secrets and Security pane with a passed manifest check and secret reference policy

Actual Adios UI · demo data

07Secrets + security

Give it secret references, not your keys.

The manifest can declare what the app needs without exposing the value. Adios checks secret references and risky runtime patterns before the change moves forward.

secret:// references instead of raw values
Manifest errors, warnings, and platform security check

Adios Deploy pane showing the production artifact action and latest successful workspace build

Actual Adios UI · demo data

08Production boundary

Confidence is not permission to deploy.

The agent can prepare the change and produce a successful artifact. Production remains a separate action, tied to the exact build you reviewed.

Immutable production artifact step
Explicit deploy action tied to the latest successful build