Skip to content

Auto · Apps

Auto applications

Edit code and documents, work with commands, carry out development tasks, and organize personal knowledge. Four main applications address these activities; system apps and demos introduce everyday desktop tools and their interactions.

Four main applications

Each application has its own use cases while sharing Auto, AutoUI, and common ecosystem capabilities. Features and readiness are described individually.

AutoEdit own-source workspace · VM/Iced, dark · Windows · 2026-10-10 · f9ae2a64
AutoEdit workspace
01Code and text

AutoEdit

A lightweight text workspace for browsing, editing, and comparing files. Native desktop use, code review, and small focused edits guide its development.

  • Project files and multiple editing tabs
  • Find, replace, and search across files
  • File, directory, and buffer comparisons
Explore this application
AutoShell · colored ls directory results
AutoShell native main interface
02Commands and scripts

AutoShell

Everyday shell commands, field-based data pipelines, and AutoScript in one session. Use it interactively or call it from the command line.

  • A persistent command session
  • Structured file and JSON queries
  • Multiline scripts and CLI automation
Explore this application
AutoMusk conversation and tool activity · password-generator example · dark · provided 2026-10-12
AutoMusk project workspace
03AI-assisted development

AutoMusk

A coding agent that organizes development around Plans and Specs, keeping requirements, execution, verification, and project knowledge traceable.

  • Project conversations and tool calls
  • Planning, execution, review, and consolidation
  • Model, role, and skill configuration
Explore this application
AutoJade workspace · dark · product manual sample · provided 2026-10-10 · release preparation
AutoJade document workspace
04Documents and knowledge

AutoJade

An editor for AutoDown documents and local knowledge bases. Writing, page links, search, and directory organization form a developing personal knowledge workspace.

  • Document editing and multiple pages
  • Links, backlinks, tags, and search
  • Page organization and local draft recovery
Explore this application

System applications and demos

Explore Auto applications through real interfaces, then learn their purpose, operations, and runtime requirements. This catalog covers 28 applications and examples, with integration and readiness described individually.

28 items · select an image to enlarge it

Work and daily life

Native VM window · basic calculation mode.
Calculator actual running interface

Calculator #

A compact tool for everyday arithmetic, with scientific and programmer modes available from the same window.

Operations and requirements
A typical workflow
  1. Enter numbers and operators to inspect the expression and result.
  2. Switch between Basic, Scientific, and Programmer modes.
  3. Clear the current input and start a new calculation.
Requirements and current scope

Basic arithmetic needs an AutoUI runtime and no application backend.

This introduces calculator input and modes; operator coverage depends on the implementation version.

Capture runtime:VM · 2026-10-01

View source
Native VM window · local time at capture.
Clock actual running interface

Clock #

Clock, world time, alarms, stopwatch, and timer share one application. A desktop widget keeps time visible outside its main window.

Operations and requirements
A typical workflow
  1. Inspect the local time and date.
  2. Select world time, alarms, stopwatch, or timer.
  3. In the desktop runtime, keep the app running and minimize it to see its widget.
Requirements and current scope

Timers require a running application; desktop widgets require the AutoOS host.

The standalone window and desktop widget are separate presentations. The widget currently appears after launching the application.

Capture runtime:VM · 2026-10-01

View source
Native VM window · four built-in example tasks.
Tasks actual running interface

Tasks #

A task list for adding, completing, filtering, and clearing everyday items. It also introduces application state connected to a backend.

Operations and requirements
A typical workflow
  1. Add a task using the input field.
  2. Toggle completion and switch between all, active, and completed items.
  3. Inspect the remaining count and clear completed items when needed.
Requirements and current scope

Requires the task backend or a local VM runtime that executes its backend logic.

The capture uses application seed tasks. This introduction page does not provide cross-device task synchronization.

Capture runtime:VM · 2026-10-01

View source
Native VM window · built-in demonstration weather for Beijing.
Weather actual running interface

Weather #

City weather, hourly changes, and related measurements introduce information layout and desktop widgets.

Operations and requirements
A typical workflow
  1. Select a city and inspect its temperature and overview.
  2. Read hourly conditions, humidity, wind, and other measurements.
  3. Launch the app in the desktop host to display its weather widget.
Requirements and current scope

Built-in weather data can be shown offline; the widget requires the AutoOS host.

The current data is demonstration weather, not a live weather feed or travel forecast.

Capture runtime:VM · 2026-10-01

View source
Native VM window · built-in notes and editing area.
Notes actual running interface

Notes #

Short notes combine a list and a text editor, with folders, tags, and pinning for organization.

Operations and requirements
A typical workflow
  1. Choose a note from the left-hand list.
  2. Edit its title and body or create another note.
  3. Organize notes using folders, tags, and pinning.
Requirements and current scope

Requires the notes backend or local VM backend logic; persistence depends on the runtime.

This is a short-note application. Page relationships and knowledge-base work are described separately for AutoJade.

Capture runtime:VM · 2026-10-01

View source
Native VM window · initial sample month and selected date.
Calendar actual running interface

Calendar #

A month grid for looking up dates, switching months, and keeping the current selection.

Operations and requirements
A typical workflow
  1. Inspect the displayed month.
  2. Move between months and select a date.
  3. Use Today to return to the application’s current-day location.
Requirements and current scope

The month view needs no business backend; a desktop widget needs the host and a running app.

This introduces a calendar and date selection. The captured initial month is sample state, not a full collaborative scheduling service.

Capture runtime:VM · 2026-10-01

View source

Reading and communication

Native VM window connected to the actual chat backend · built-in contacts and messages.
Chat actual running interface

Chat #

Contacts, message history, and an input area introduce a messaging interface connected to its own application backend.

Operations and requirements
A typical workflow
  1. Select a contact and read the conversation.
  2. Enter a message or choose a quick reply, then send it.
  3. Observe changes to the conversation and contact summary.
Requirements and current scope

Requires the chat API; event notifications also need the corresponding streaming service and runtime support.

Contacts and messages are built-in examples. The AutoBot label does not establish a live model connection, and this app is not connected to WeChat.

Capture runtime:VM · 2026-10-01

View source
Native VM window connected to the actual reading backend · three sample books.
Book reader actual running interface

Book reader #

A library leads into books, chapters, and reading settings, introducing navigation and reading progress.

Operations and requirements
A typical workflow
  1. Select a book from the library.
  2. Open a chapter, read its text, and move between chapters.
  3. Inspect progress and settings, then return to the library.
Requirements and current scope

Requires book and chapter APIs; the local example backend supplies built-in books and text.

The capture shows the built-in library. It does not establish an online bookstore or general ebook import.

Capture runtime:VM · 2026-10-01

View source
Native VM window · built-in article list.
Blog reader actual running interface

Blog reader #

Browse articles by category and open their text and author information. The list and article views introduce a content application.

Operations and requirements
A typical workflow
  1. Choose a topic or category from the article list.
  2. Open an article and read its author information and text.
  3. Return to the list to explore another article.
Requirements and current scope

Requires the article backend or local VM backend logic.

Content comes from built-in articles rather than an external blog aggregation service; writing features depend on the version.

Capture runtime:VM · 2026-10-01

View source

Media and creation

Native VM window · built-in video content cards.
Video community example actual running interface

Video community example #

Video cards, categories, and watch pages introduce a portal-style content application, distinct from the local-file video player.

Operations and requirements
A typical workflow
  1. Browse video cards and categories on the home page.
  2. Choose an item to open its watch page.
  3. Inspect its information and return to the home page.
Requirements and current scope

Lists and metadata need the application backend; playback additionally needs valid media and decoding support.

The capture shows built-in titles and cards. It records content browsing, not successful playback of every listed video.

Capture runtime:VM · 2026-10-01

View source
Native VM window connected to the real media scan service · local WAV test track.
Music player actual running interface

Music player #

Local music scanning, a library, queue, and record stage present tracks and playback controls together.

Operations and requirements
A typical workflow
  1. Configure an accessible media directory and scan the library.
  2. Select a track to inspect its title, format, and position.
  3. Use playback controls, the queue, and volume to organize listening.
Requirements and current scope

Needs the real media scanning/streaming service, audio files, and playback support in the chosen runtime.

The capture uses a local WAV test tone. The Hi-Res interface label is not evidence of the file’s sample rate or audio quality.

Capture runtime:VM · 2026-10-01

View source
Vue runtime · a real local WebM test video opened and positioned.
Video player actual running interface

Video player #

A large viewport, timeline, and queue focus on local video playback, separate from the video community example.

Operations and requirements
A typical workflow
  1. Scan a local media directory or choose a playable video file.
  2. Open the video and seek to the desired position.
  3. Adjust volume, speed, or queue options and collapse the sidebar as needed.
Requirements and current scope

Needs real media and scanning/streaming services. Vue uses browser decoding; native playback additionally depends on libraries such as libmpv.

The capture decodes a local WebM test clip. A Vue capture does not verify every native format or playback capability.

Capture runtime:Vue · 2026-10-01

View source
Native VM window · a real 320×240 test image opened.
Image viewer actual running interface

Image viewer #

Open an image or directory and inspect it using fit, zoom, rotation, and navigation in a large viewport.

Operations and requirements
A typical workflow
  1. Open an image or directory and select an image.
  2. Use fit, 1:1, or zoom controls to inspect details.
  3. Rotate or pan the image, then move to a neighboring file.
Requirements and current scope

Requires accessible image files; supported formats and decoding depend on the runtime libraries.

This is a viewer rather than an image editor. The capture opens scenic-320x240.png from the source test fixtures.

Capture runtime:VM · 2026-10-01

View source
Native VM window · a grid pattern drawn through real clicks.
Pixel paint actual running interface

Pixel paint #

Draw cell by cell on a 16×16 grid with pencil, eraser, fill, and picker tools, with colors and history kept in application state.

Operations and requirements
A typical workflow
  1. Choose a color and click grid cells to draw.
  2. Switch to eraser, fill, or picker to adjust the pattern.
  3. Undo, redo, or save and reload the canvas.
Requirements and current scope

Local interaction needs no business backend; saving uses the runtime’s Storage support.

The current interaction is cell clicking. This is not presented as continuous drag painting or a general image-export editor.

Capture runtime:VM · 2026-10-01

View source

System and data

Native VM window · actual capture-machine resource samples.
System monitor actual running interface

System monitor #

Inspect CPU, memory, and process information in a full window, with a compact desktop widget for ongoing status.

Operations and requirements
A typical workflow
  1. Read the resource usage overview.
  2. Inspect process or resource panels for details.
  3. Keep the app running and minimize it in the desktop to display its monitoring widget.
Requirements and current scope

Requires host system sampling; available measurements vary across platforms.

The capture records the capture machine at that moment, not the website visitor’s device.

Capture runtime:VM · 2026-10-01

View source
Native VM window · built-in table structure and sample records.
Database interface example actual running interface

Database interface example #

A database tree, records, editing controls, and query panel introduce the structure of a data workspace.

Operations and requirements
A typical workflow
  1. Choose a table from the database tree.
  2. Inspect columns, records, and editing controls.
  3. Switch to the query panel to inspect input and result layout.
Requirements and current scope

The application can display sample data; real connections, execution, and persistence need their corresponding backend.

The capture uses built-in Northwind-style data. SQLite labels and query/transaction controls do not prove a real database connection; transaction behavior includes simulation.

Capture runtime:VM · 2026-10-01

View source
Native VM window · real files in a dedicated media fixture directory.
File manager actual running interface

File manager #

Navigate directories in list or grid form and find files by name, size, or date, with operations organized around a real filesystem.

Operations and requirements
A typical workflow
  1. Open an accessible directory using the address bar.
  2. Switch list/grid views and use sorting, search, or hidden-file controls.
  3. Inspect selected files and check target paths before rename, copy, or delete operations.
Requirements and current scope

Real reads and writes require filesystem capabilities and permissions; Vue needs the corresponding file API.

The capture browses real files in a dedicated fixture directory. Local filesystem use is distinct from static-web fallback demonstration state.

Capture runtime:VM · 2026-10-01

View source
AutoOS VM virtual desktop · actual launcher in icon view.
Application launcher actual running interface

Application launcher #

Find and launch applications in list or icon form. The desktop version uses the host registry; the standalone example introduces launcher interaction.

Operations and requirements
A typical workflow
  1. Open the launcher.
  2. Search by keyword or browse applications in icon view.
  3. Choose an application to launch and return to existing desktop windows.
Requirements and current scope

Actual launching requires the AutoOS desktop host, application registration, and the relevant runtime capabilities.

The main image is an existing desktop launcher capture. The standalone 028 example’s data is not identical to the current desktop registry.

Capture runtime:VM · retained / 留存素材

View source
Standalone VM window · three built-in demonstration log records.
System log actual running interface

System log #

A filterable list combines time, source, level, and message. The desktop host can supply system and application events.

Operations and requirements
A typical workflow
  1. Inspect log times, sources, and levels.
  2. Filter messages by level or keyword.
  3. Return to the complete list and observe running events.
Requirements and current scope

Real host logs need a desktop-injected log source; standalone mode can display built-in records.

This standalone capture contains three demonstration records labeled mock. They are not actual operating-system failures or live host events.

Capture runtime:VM · 2026-10-01

View source
Native verification material · Windows shell session (retained 2026-09-22 image).
AutoTerm terminal actual running interface

AutoTerm terminal #

A general desktop terminal runs host shells and interactive programs in tabs and split panes. AutoTerm hosts terminal sessions; AutoShell supplies a command language and engine.

Operations and requirements
A typical workflow
  1. Open the terminal into its configured shell.
  2. Create another tab and split panes horizontally or vertically as needed.
  3. Enter commands in the active pane and inspect output and scrollback.
Requirements and current scope

Native interaction needs autoterm-core, platform PTY support, and a configured shell. The Vue viewport is currently read-only.

An existing native verification image records a Windows command session. Its capture version is tracked separately from current sources and is not a new full feature acceptance.

Capture runtime:Rust native (retained verification capture) · 2026-09-22

View source
Existing native capture material · skills configuration list.
AutoOS settings actual running interface

AutoOS settings #

A graphical workspace organizes AutoOS and AI-tool settings such as models, roles, agents, skills, and themes.

Operations and requirements
A typical workflow
  1. Select the configuration module to manage.
  2. Inspect existing entries and their fields.
  3. Save changes using the application’s controls, then let the consuming tool read them.
Requirements and current scope

Read/write operations require configuration-file permissions; models, agents, and daemons need their own services.

This reuses the website’s existing skills-management capture. An entry in settings does not establish a running service or model connection.

Capture runtime:Native configuration UI (existing website capture) · retained / 留存素材

View source

Games

Native VM window · actual board after starting a game.
Tetris actual running interface

Tetris #

Falling blocks, rotation, movement, and dropping introduce a real-time game, with score, level, and next-piece information around the board.

Operations and requirements
A typical workflow
  1. Start the game and inspect the current and next pieces.
  2. Move and rotate with the keys shown by the interface, then drop a piece.
  3. Pause or restart and inspect scores and records.
Requirements and current scope

Requires continuous timing and keyboard input; records use the corresponding storage or backend.

The capture shows an actual started game. Piece positions change as the game runs.

Capture runtime:VM · 2026-10-01

View source
Native VM window · actual dealt Klondike board.
Solitaire actual running interface

Solitaire #

Move cards between stock, tableau, and foundations using Klondike rules, with undo, restart, and appearance controls.

Operations and requirements
A typical workflow
  1. Start a game and inspect the tableau and stock.
  2. Draw cards or move them according to the rules.
  3. Undo a move, deal again, or inspect game records.
Requirements and current scope

Basic play needs an AutoUI runtime; persistent records depend on its backend or storage.

The main image shows an actual dealt board. It does not establish a completed game or full rule verification.

Capture runtime:VM · 2026-10-01

View source
Native VM window · actual beginner board with cells opened.
Minesweeper actual running interface

Minesweeper #

Open safe cells and mark mines using numerical clues, with difficulty, timer, and remaining-marker information.

Operations and requirements
A typical workflow
  1. Choose an easy, medium, or hard board.
  2. Open a cell and continue using its clues.
  3. Mark suspect cells or start another game when needed.
Requirements and current scope

Basic play needs no external service; pointer and marking gestures follow the current interface.

The capture shows a real beginner board after opening a safe area. Difficulty and first-move behavior come from the application.

Capture runtime:VM · 2026-10-01

View source

Application structure

Native VM window · built-in workspace and task cards.
Kanban example actual running interface

Kanban example #

Workspaces, columns, and cards organize task states and introduce how a task moves between stages.

Operations and requirements
A typical workflow
  1. Select a workspace or board.
  2. Inspect cards in different columns and open task details.
  3. Adjust task content or state and observe the board.
Requirements and current scope

Requires the example backend or local VM backend logic.

This is the 022-kanban example, distinct from the separate auto-kanban product project. The capture uses built-in workspace data.

Capture runtime:VM · 2026-10-01

View source
Vue gallery runtime connected to its actual backend · built-in articles and tags.
RealWorld application example actual running interface

RealWorld application example #

An article-community structure introduces routing, account entry points, feeds, and details, connecting multiple pages to backend data.

Operations and requirements
A typical workflow
  1. Browse articles and tags in Global Feed.
  2. Open an article and inspect its content and comment entry point.
  3. Study sign-in and writing routes and their backend contracts as needed.
Requirements and current scope

Requires the RealWorld API; account and content operations use the example backend rather than a public community.

The main capture is a Vue runtime connected to the actual example backend with built-in articles. Other runtime coverage needs separate verification.

Capture runtime:Vue · 2026-10-01

View source
Native VM window · line chart rendered from local sample data.
Chart workshop actual running interface

Chart workshop #

Switch chart types, series, and presentation settings to explore how data and graphics relate in a configurable workspace.

Operations and requirements
A typical workflow
  1. Select a chart type such as line or bar.
  2. Change series and desktop/mobile/tablet presentation settings.
  3. Play or reset example data and observe updates.
Requirements and current scope

The current workshop uses local sample data; live business data requires separate integration.

The capture shows built-in example series rather than real project business measurements.

Capture runtime:VM · 2026-10-01

View source

Ways to explore further

These v0.5 pages provide static introductions and real captures. The web virtual desktop and online app experiences are planned for v0.5.1. A UI Playground will first be evaluated with a few examples before broader application integration.

Photo, video, and file tools need real resources; monitoring and terminals need host capabilities. Some examples use built-in data, identified in their introductions. These 28 entries have different readiness levels and do not define a fixed desktop registry count.

Development example gallery (some features need a backend) →

Descriptions as of 2026-10-01. New captures identify their runtime; retained images identify their origin and version separately.

Applications in the ecosystem

Related resources

AutoDown supplies document and editor foundations. AutoUI examples offer interface development material. Both have their own introductions alongside the four main applications.

Released under the MIT License.