Get

Use cases

Start with the work.
Follow the real flow.

The landing page explains the idea. This page shows the actual work: eight narrated flows captured from the real AirCode Ø interface, from the first agent session to an app people can install.

  • 8narrated workflows
  • Real UIproduction interaction paths

Choose an outcome

From one session to an operating system for agent work.

Start with the phase that matches your current job. The same host connects all four paths.

Start & operate

Launch across repositories, keep parallel work alive and see where attention is needed.

01

Start & operate

Launch a real coding session

Choose the project, engine, permissions, model and effort, then send the first prompt from the actual AirCode Ø workbench.
Use this when

A task needs a deliberate engine, model, runtime and permission setup.

Outcome

A reproducible session that can be reopened from any connected AirCode Ø client.

  1. 1

    Select a repository available on the host.

  2. 2

    Set the engine, permissions, model and effort.

  3. 3

    Launch once and keep the complete session state.

02

Start & operate

Manage repositories in parallel

Keep work across a dozen repositories visible in one interface, arrange sessions in resizable groups, and create named docks without restarting anything.
Use this when

You are coordinating several repositories and separate IDE windows no longer scale.

Outcome

One workbench shows every repository and agent while persistent host sessions remain reachable from connected machines.

  1. 1

    Open agents from independent repositories as workbench tabs.

  2. 2

    Drag tabs into groups and resize every split.

  3. 3

    Create named docks and return to their saved client layouts.

03

Start & operate

Monitor every active session

Use one Active Sessions Dashboard to find working, waiting-for-you and ready agents across every repository, then inspect their latest replies.
Use this when

More repositories and sessions are active than you can sensibly monitor one window at a time.

Outcome

One operational view shows every repository’s progress, attention requests and latest agent returns.

  1. 1

    See working, waiting and ready session counts.

  2. 2

    Read each agent’s latest response in place.

  3. 3

    Filter attention requests and reopen the exact session.

Build & verify

Follow execution, inspect evidence and connect planned work to isolated agent runs.

04

Build & verify

Follow live agent work

Watch the plan, commands and test result update, then inspect token, time and cost statistics split by question.
Use this when

You need to understand what an agent is doing without losing the task-level thread.

Outcome

Commands, results and question-level consumption stay attached to the work they explain.

  1. 1

    Follow readable task progress as it happens.

  2. 2

    Open commands and their output without leaving the session.

  3. 3

    Review runtime, tokens and cost by question.

05

Build & verify

Review every change in Git

Open the real Source control surface, inspect a side-by-side working-tree diff, then move from implementation to test.
Use this when

An agent says the work is complete and you need repository evidence before accepting it.

Outcome

Implementation, tests and exact line changes can be reviewed beside the originating session.

  1. 1

    Open the repository working-tree status.

  2. 2

    Inspect additions and deletions side by side.

  3. 3

    Move directly between implementation and test diffs.

Understand & reuse

Measure where resources go and turn verified project history into reusable agent context.

06

Understand & reuse

Understand token consumption

Track tokens, sessions, runtime and API-equivalent cost, then split usage by project, app, provider and task.
Use this when

You need to explain consumption, compare projects or find an expensive workflow.

Outcome

Usage is attributable from the organization view down to projects, sessions and questions.

  1. 1

    Read the total token, session, runtime and cost picture.

  2. 2

    Compare consumption across projects and clients.

  3. 3

    Drill into providers, dates, sessions and questions.

Build & distribute

Turn a working app into an installable product and publish it for others to discover.

08

Build & distribute

Build and publish an app people can install

Create the app with a coding agent, prepare it for phones and tablets, generate its Showcase, then submit the reviewed listing to AirCode Ø Marketplace.
Use this when

You want people to try an app in their browser and add it to their Home Screen without preparing a separate Store release.

Outcome

A review-ready Marketplace listing connected to the live Application, with Try and Install available after approval while the app is online.

  1. 1

    Build and verify the app, then run it as a saved Application.

  2. 2

    Give it a Home Screen name and icon, and generate its Showcase.

  3. 3

    Review the listing and submit the exact revision to AirCode Ø Marketplace.

Try the workflow

Give every agent a persistent place to work.

Launch from the screen you have. Continue on the screen you want.