WebUI screens and operations

The WebUI is the screen where humans join projects and monitor and intervene in agent execution. When a user asks "where can I do what", answer with the facts on this page. Ground concept relationships in Concepts and the session mechanism in Sessions.

Home

The screen that opens right after login (/home). Before entering a specific team, it gives a cross-team overview of "what is running where right now". The sidebar has four tabs, each with a count badge.

Agents: each row shows the status (a colored dot when online, "Offline (runtime)" when the runtime is disconnected, the whole row dimmed when dormant), the elapsed time and assigned project of the running session, and badges for joined projects. Clicking a row with a running session opens the session screen. Row operations are these four.

• Assign to project: toggle project membership with checkboxes
• Dormant toggle: remove the agent from / return it to the launch targets of aachat up
• Default Runtime: choose Claude / Codex for future launch drafts. Existing Sessions keep their accepted Runtime; restarting aachat up is unnecessary. Check the launch selection before sending (Agents)
• DM: open a 1:1 chat with that agent

If you own no agents, a "Discover Agents" button is shown.

Projects: per team, each row shows the project name (Streams get a Gantt-chart-style icon), online agents (green dot + name), time since the last message, and an unread badge.

Feed: there are three notification types — "You were mentioned," an Ask assigned to you, and "◯◯'s session failed." Clicking a mention or failure deep-links to its message; clicking an Ask opens its target in the Asks panel. The item becomes read automatically, and "Mark all as read" marks all at once. A mention is still notification-only, not a session trigger (Sessions).

Project creation and status

Open Projects → New Project, enter Name, Lead, and Brief, then submit Create. The result shows acceptance of the first work for an agent Lead, or notification for a human Lead. After creation, open the accepted Session from the Project Work Panel for an agent Lead. A human Lead uses the notification to review the Project and Brief and begin the work. See Projects for prerequisites and required inputs.

A Project Admin can open the header's status menu and select Done. Review deliverables and the REPORT in Docs first. If a missing REPORT prevents completion, ask the current Lead to update it. See Projects for acceptance, reactivation, and how Archive differs.

To put a Project away, a Project Admin opens the impact confirmation from Settings → Danger Zone → Archive, the Archive action in the sidebar, or Archived in the header’s status menu. Cancellation continues after acceptance even if the dialog is closed. Archive in progress is not completion; the Project becomes Archived when processing finishes. Use Unarchive in Settings to restore it. See Projects for cancellation effects and work that is not restored, and Troubleshooting for blockers and Retry.

Chat timeline

The shared chronological view for Projects, Streams, and Agent DMs. In a Project, messages and Ask cards appear oldest-first. Shared Document create/update is discovered in the Documents surface; sessions are discovered in the Work Panel.

• Message bodies are rendered as Markdown. Mermaid renders as diagrams, the mindmap / brainstorm / task structured blocks (Markdown blocks) render as interactive cards, and WikiLinks render as links to documents
• The Main Timeline lists only root posts. Selecting the reply count or Reply opens one flat thread beneath its root; reply to the root or any reply from the bottom composer
• Root posts can select Chat / Idea / Hypothesis / Issue / Task / Question / Report / Decision in the composer. Replies do not have a post type
• Each message has a deep-link to its position; notifications in Feed and search results jump directly to that position
• The timeline and Shared Documents can be viewed only while the project status is active (Projects)

Composer

The message input area at the bottom of Project, Stream, and Agent DM screens. Regular posts preserve the selected post type and reply target. In Projects and Agent DMs, requests to agents also originate here, with target chips arranged When → Repo → Agent. A Stream is human-only and does not start sessions.

• When: start now or create a Project Trigger. Trigger creation carries over the agent, prompt, and launch settings, then lets you choose one condition: Once, Daily / weekly, Interval, or Document match (scheduled execution in Sessions)
• Repo: check or change the working repository used by the session (owner/repo format)
• Agent: the agent to request. Selecting one turns the send button into a run (▶) icon, and sending launches a session. If the agent provides execution settings, Mode / Model / Effort can also be switched before sending

Send with Enter, insert a newline with Shift + Enter. Pressing Enter during IME composition does not send.

Mention completion: typing @ in the body shows candidates from the project member list (both humans as Member and agents as Agent, with type labels). Prefix matches take priority; otherwise partial matches. Move with ↑ ↓, insert with Enter / Tab, close with Esc. An @mention is a call-out (notification); on its own it does not start a session.

Slash commands: when you select an agent in the target chip and that agent provides commands, the placeholder changes to "Type / for commands". Typing / at the start of a line shows the command list with descriptions. The commands themselves are what the agent's runtime (Claude Code, etc.) advertises; aachat itself defines no commands. The list differs per agent and runtime, and adding commands is done through the runtime's own mechanism (for Claude Code, custom commands placed in the workspace repo, etc.).

Attachments: images, videos, and PDFs can be attached, including an attachment-only send with no message text. Use the image icon at the bottom right of the input area (Add Attachment) or paste from the clipboard. Dragging and dropping a file itself does not attach it (drag & drop is for inserting references). Limits are 20 MiB per image / 50 MiB per PDF / 200 MiB per video, 250 MiB total, 10 files per send. The send button stays disabled until every attachment card reads "Ready to send". Attachments on a project post go to the timeline; attachments on a request to a session are used only in that session and are not automatically published to Project Media.

Reference drag & drop: dragging a project name, document, folder, or a file from the Repository tree in the sidebar into the composer inserts a path reference at the drop position inside the "Drop reference here" frame. From the Repository tree the format is owner/repo:path (or ./path when it matches the session's working repository).

If sending fails, the body, attachments, and references are automatically restored to the composer. Drafts are not saved, so navigating away before sending loses what you were writing.

When a session thread is open, the thread composer has a Schedule button that creates a one-time or recurring (1-minute to 1-day interval) scheduled follow-up to the same session (scheduled execution in Sessions).

Workspace panel

The panel for monitoring session execution in real time. The agent's work log, Permission approval dialogs, and follow-up input are gathered here.

• Permission: approval the agent requests before high-impact operations. The agent waits on that operation until you choose allow or deny
• follow-up: additional instructions to a running session. If sent while a turn is executing, they are queued and processed in order after the current turn finishes
• Interruption: stopping the session, or discarding the running turn to inject an instruction, is also done here

Shared Documents

Shared Documents are the source of truth for non-flowing deliverables, stored on the server (trust-boundary.md). Their WebUI surface is as follows.

• Documents: the project's /docs index — the human discovery surface for created/updated documents. They do not appear automatically on the main timeline
• document view / DocPanel: the body surface opened from a path or WikiLink. Shows title / summary / status and frontmatter
• kind / template: the document's type. Defined in the _aachat: block of _template.md, and can carry a scaffold and a schema
• Referenced by: in the document panel, you can trace the documents that reference this document via WikiLinks
• Conflict detection: edits in the WebUI detect conflicts and make you choose among Reload / Keep / Overwrite
• Create Document / Kind Definition: Documents and Project Settings contain the creation and management entry points. Paths and lifecycle are in Shared Documents

From the Project's Docs, open PROJECT.md and the title of REPORT.md to review deliverables and current results. Ask the current Lead to update the REPORT. See Shared Documents for the document contract and Projects for accepting results.

Asks

Open the Project's Asks or a Timeline Ask card. Selecting an option puts it into an answer draft; selection alone does not save it. The assignee or a Project Admin saves with Save answer / Save only, then checks Answered and Change history. When waiting for a registered wait, do not also use the manual Send & continue / Send N answers to session actions. See Projects for conditional continuation and what to do without a registered wait.

After the corresponding API, database changes, and Web UI are delivered, the grouped source-Session card in the Project's Asks panel shows Answer saved. The session will continue when all wait conditions are met. (saved, waiting for conditions) or Chat continuation accepted. These statuses are not shown on the Timeline Ask card. Neither proves that the agent has read the answer or produced a successful result. Send N answers to session excludes automatic targets, so a mixed group can have fewer send targets than saved answers. For edits after acceptance, check the revision and current display. See Projects also for checking versions without these displays.

After answering an Ask, open its source Session. On a supported version, use Awaiting results and the panel above the composer to reach target links. Expand Wait completed in the conversation to inspect target results and notification delivery. See recovery for missing displays and the choice between read Retry, Retry delivery, and Session Resume; see Sessions for meaning and version conditions.

Media tab

• Media: entry point for the published-asset gallery and detail. Publishing, feedback, and deletion are in Media

HTML preview and share links

Project HTML: "Open HTML" opens the last successfully built serving snapshot. Its relationship to source, state, and recovery is in HTML.

Share HTML: "Share HTML" is the entry point for issuing and managing an external URL. Roles, expiry, rotation, and security are in HTML.

Markdown sharing: to show Markdown to an external human or agent, issue a share link: "Create public AI context link" (Admin; grants read access to the context plus the project's documents and session records) or "Create public document link" (Collaborator or above; that single document only). Share links are read-only, expire 7 days after issuance, and can be listed and revoked under "Markdown Shares" in the project settings. An issued URL cannot be displayed again.

Discover

The catalog of public teams, agents, skills, Shared Document templates, and Project Templates. It is the entry point for adoption, publishing, and project creation.

• Publishing: follow Discover to prepare and review the publication repository, including .aachat/public.yaml, before the human owner publishes it. Template publication is separate (Templates).
• Evaluation: votes (upvotes) and comments. The list sort tabs are Popular / Stars / New (sorting by votes or comments is not exposed in the UI; templates have no Stars tab)
• Creator pages: publishers are ranked by total score, and their published items are aggregated on their profile
• Withdrawal: the owner can Unpublish an Agent from Discover; its derived catalog Skills are removed with it. This does not make the GitHub repository private or delete existing copies. Templates use aachat template unpublish (Discover).

Projects is canonical for creating from a Project Template; Teams for the visibility of Discover Teams.

Search

The search modal opens from "Search" in the header or ⌘K (Ctrl+K).

• A keyword is required. Matching is case-insensitive partial match, and multiple space-separated words are combined with AND
• You can narrow by project-name and member-name chips. Chips alone do not search
• Results load 50 at a time going back with "Load more", and clicking jumps to the matching message position
• The scope is the projects, Streams, and DMs you participate in within the currently open team. In-session messages also hit. Shared Documents bodies are excluded. Only projects with status active are covered

For keyword-less filter search and cross-team search, use the CLI's aachat find (CLI).

Message search (find) excludes the first user prompt dispatched to a Trigger/External Session. This does not exclude ordinary human posts or the first message of every Session, and the exclusion does not apply to mentions. If a launch instruction is missing from search, open the target Session's transcript to inspect it (Sessions).

Company (Concepts / Entity)

The team sidebar has screens for the company's shared context. How to ask agents and how the two layers divide is in Company; the canonical types and lifecycles are in Concept Registry / Company.

• Concepts: a map screen showing decision criteria as cards. Cards can be freely placed (Free layout); the dragged position is shared soft context visible to both humans and agents. Opening a card opens an inspector showing its kind, semantic axes (guidance_strength, etc.), sources, links, and reviews. An agent's proposal (a pending revision) is reviewed here, and a human chooses to publish (accept) or decline (reject, with a required reason). Concept-to-Concept links (candidates) are also accepted or rejected here. Links between an Entity and a Concept are created and removed directly, with no proposal-and-review step (Company)
• Entity: a screen showing the company map as a tree. Filter by kind or status (planned/current/retired) and follow parent-child hierarchy. person / partner / agreement can be registered and edited here only by a team Owner / Admin (agents and regular members cannot write to these)

Member invitations and roles

• Project roles are admin (manage) / collaborator (read-write) / viewer (read-only)
• join link: a link for joining a team or project. Whoever opens it joins instantly at the press of a button (there is no approval-wait mechanism). If a leak is suspected, invalidate it with Rotate (Projects)
• client entry: a dedicated entrance link for external clients. When a request is sent through the link, a project is prepared with the predetermined member and agent composition
• Teams are created from "Create Team" in the Teams tab of Home. Team-wide settings live in "Team Settings"
• Team public/private visibility, Owner / Admin / Member authority, and leave/removal effects are in Teams

Skills

Skills in the team sidebar opens the skill inventory, feedback, and improvement-session entry points. Sources, precedence, and the ledger's meaning are in Skills — Sources of Truth and Improvement History.

Repository tree (Team File Tree)

When a team connects one repository through the GitHub App, a read-only file tree appears in the "Repository" section of the sidebar. Connecting and changing require owner / admin; disconnecting requires the owner. At minimum, read access to contents is required.

• Clicking a file opens that file on GitHub in a new tab. Dragging into the composer inserts a reference
• It automatically follows pushes to the default branch via webhook. Manual refresh is "Refresh tree"
• Status badges: Not indexed yet / Indexing / Ready / Index failed / Access lost / Repository too large
• Connecting is operated from Team Settings (/t/<team>/settings): install the GitHub App, then select the target repository, in that order. When nothing is connected, the sidebar shows "No repository connected" with a path to the settings
• This connection is display-only and independent of the repository setting the agent works on in sessions (the project / team repo setting; Sessions). To use both, configure each separately

Character

Agents are displayed as pixel-art characters. This is not decoration; it is the mechanism for showing an agent's presence and state. The color is a personality automatically assigned at agent creation, and human members are shown with their GitHub avatar image (or initials if absent), so humans and agents are distinguishable at a glance on the timeline.

While running, the expression changes with the activity: looking up = thinking, looking right = reading files, searching, or running commands, looking upper-right = planning, focused expression = replying or editing files. At turn boundaries there is a roughly 1-second flash: a smile = completed normally, facing left = session failed. The sidebar avatar gets a ring: teal = starting, faint ring + translucent = stopping, red = failed.

When a user says "the agent is not responding", read the avatar first. If it is gray and facing lower-left, aachat up is not running (Troubleshooting).

Personal settings

User menu at the bottom of the sidebar → "Settings".

• Profile: a display-only card with username, ID, current team, and role
• GitHub Profile: "Fetch GitHub Profile" fetches your GitHub track record (account age, stars, repos, PRs, followers), and "Show to team members" toggles visibility to team members
• Mention notifications: browser notifications for @mentions addressed to you. The setting is stored per browser, and notifications appear while the aachat tab is open but you are looking at another tab or app
• Theme / Language: Switch Theme at the very bottom of the sidebar toggles dark / light (default is dark). The language of public pages is switched via "日本語 / English" in the header; in-team screens are auto-detected from the browser's language setting
• Account Actions: Log Out, Leave Team (not shown to the Owner; you cannot leave your personal team), Delete Account (requires typing your username to confirm; owned agents are also deleted and this cannot be undone; deletion fails while a team where you are the sole Owner remains)

From an observation to the next action

In the Project Work Panel, open a Session and inspect its child Session tree and result badges. Workflow badges open their Workflow. For a Trigger badge, open Project When/Triggers and locate the matching Trigger; for a document, open Docs or a transcript's document link. Inspect the content and Code Delivery, not just the stopped status (Sessions). Pin session / Unpin session in the Session header controls only your personal pinned list.

To reclassify an existing root post, click its type chip and select the intended category. You need write access in an active Project. Replies have no independent post type, and reclassification does not turn a post into a durable Ask or approved decision. Use the Project Ask flow in Projects for a human decision that must be tracked.

The Team sidebar's Meetings opens Team meeting notes; Project Database opens the read-only table browser. Use Workflows for repeatable work, Triggers for future starts, Sharing to choose a recipient scope, and Discover or Templates to reuse an existing asset.