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
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.
An editor for AutoDown documents and local knowledge bases. Writing, page links, search, and directory organization form a developing personal knowledge workspace.
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.
A database tree, records, editing controls, and query panel introduce the structure of a data workspace.
Operations and requirements
A typical workflow
Choose a table from the database tree.
Inspect columns, records, and editing controls.
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.
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
Open the terminal into its configured shell.
Create another tab and split panes horizontally or vertically as needed.
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.
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.
The shared AI architecture connecting applications, agents, and model services.
Related resources
AutoDown supplies document and editor foundations. AutoUI examples offer interface development material. Both have their own introductions alongside the four main applications.