A3S Web is a desktop, local-first AI workspace that lets a user start with an outcome, work directly with real files, supervise execution, and retain control of every meaningful change.
The product is not a generic chat client and does not make Office and coding
compete as separate destinations. Work at #home is the single task surface;
file type and user intent determine the scene.
- Outcome first. The home composer asks what the user wants to accomplish.
- One work identity. Home, files, Office, code, and AI use one conversation list and one active draft.
- Real files remain visible. Local paths and source fingerprints are user-facing identities, not implementation details hidden behind uploads.
- Review before consequence. Sensitive tool use, destructive filesystem actions, compatibility loss, and structured AI changes require explicit review.
- Inline for routine work. Naming, rename, and reversible row actions stay in context; dialogs are reserved for real risk.
- Evidence over confidence. Delivery separates passed, pending, failed, and residual-risk checks.
- Local by default. The app remains useful without an A3S OS account and keeps local state recoverable during disconnection.
Open #home
→ describe an outcome, resume a conversation, or open a file
→ inspect and select context
→ submit through the shared composer
→ supervise execution and decisions in the AI Assistant
→ open resulting files in the applicable Work scene
→ edit, review, save, and validate
→ optionally package selected sources into Knowledge
- Work;
- Knowledge;
- enabled A3S Use activities;
- Memory;
- Plugin Marketplace;
- Settings.
There is no separate Code or Office entry.
The left sidebar is the unified conversation list:
- new conversation;
- search;
- selected conversation;
- inline rename and delete;
- truthful running state.
Historical sessions remain visible regardless of which earlier product created them. New sessions use the default agent.
The center renders one scene at a time:
- AI-native home and managed artifact library;
- local file manager;
- Office/PDF editor;
- code/text/Markdown editor.
The active scene is local UI state. It does not change the canonical Work route or conversation identity.
The resizable right pane displays the active conversation, execution, tool decisions, recovery, evidence, artifacts, and the same composer used by Home. On compact desktop widths it becomes an overlay.
The home page follows a task-first hierarchy:
- concise Work identity and outcome promise;
- production task composer;
- implemented capability shortcuts;
- templates, folders, and recent files.
The assistant starts closed and opens once after task submission. Prompt starters populate an editable draft and never auto-send.
The file manager follows familiar Finder and Windows Explorer behavior:
- real folder selection and persisted workspace;
- back, forward, up, breadcrumbs, grid/list, filtering, sorting, and search;
- marquee, checkbox, additive, range, and keyboard selection;
- copy, cut, collision-safe paste, drag and drop, favorites, reveal, and Quick Look;
- background and item context menus;
- inline create, rename, and duplicate naming;
- a stable selection action shelf;
- permanent deletion confirmation.
The empty-space context menu is a first-class folder command surface. It must not act on a stale item selection.
Opening a non-binary text file enters the Work code scene with a lazy explorer, multiple Monaco tabs, language services, diagnostics, semantic navigation, safe saving, and external-change conflict review. Markdown shows source and live preview together.
DOCX, spreadsheet, presentation, and PDF handlers use consistent Work chrome, format-specific editing, explicit save-back, compatibility review, preview, print, and export flows. Heavy dependencies load only when needed.
Editor context actions add bounded selected content to an editable request. Actionable AI output uses a structured proposal with trusted before/after values and per-target approval. A stale target is skipped rather than overwritten.
Execution stays inside the active conversation. Tool calls show requested scope, permission state, progress, output, and recovery. Completed file entries open through Work's current file handlers.
The delivery summary reports verification evidence. “Prepare review” adds an evidence-based review request to the same conversation; it never navigates to a deleted task workspace.
One or many selected files and folders can create a managed knowledge base. Creation records and copies the source package but does not compile it.
Compilation is a second action:
- explicit user request; or
- opt-in automatic policy after stability, quiet-window, minimum-interval, retry, and bulk-change safeguards pass.
Only a successfully promoted OKF wiki generation becomes searchable.
Memory is a standalone system surface at #memory. It loads the complete local
store for search, filters, timeline, and bounded graph projection. Entering it
preserves the current Work conversation and draft.
Verified A3S Use packages can contribute Activity Bar views. A contribution is isolated and can propose reviewed context and an optional Skill back to the current Work draft. Unknown or disabled keys recover safely.
Settings is a global modal with Account, Appearance, Model, Agent, Context,
Integrations, Channels, About, and Help. Canonical channel routes are nested
under #settings/channels/.
- time from opening
#hometo a meaningful action; - successful conversation continuation across scenes;
- file operation completion and recovery rate;
- rate of AI context requests that remain within selected scope;
- proposal approval, stale-target, and rollback outcomes;
- knowledge creation-to-compile conversion;
- route, keyboard, narrow-width, and dark-theme regressions.
The release excludes:
- separate Code or Office products;
- legacy product-prefixed Work routes;
- silent destructive organization;
- automatic publication of memory or failed knowledge generations;
- controls whose destination or recovery path is not mounted.