---
title: Web
description: >-
  Use the complete Atoi product shell for threads, projects, tasks, search,
  automation, and configuration.
order: 1
---
The web app is Atoi’s broadest product surface. It combines the conversational front door with project workspaces, durable task detail, attention, retrieval, connected channels, automation, customization, and account settings.

## Navigate from Home

After sign-in and onboarding, `/` opens the persistent home orchestration thread. Use it to plan across projects, route work, and return to an ongoing conversation. Other threads have canonical `/c/<id>` routes. The same chat component is used for project-associated threads; a project association does not create a separate chat implementation.

The sidebar provides access to recent threads and projects. Expanding a project reveals Home, Threads, Tasks, and Views. The thread switcher and project menus preserve canonical thread routes so links remain stable outside the lens where you found them.

## Work inside a project

Project Home shows identity, shared instructions, files, documents, runtime context, and recent threads. The Documents section supports project notes and briefs. Threads provides project-scoped search and view controls. Tasks provides status and receipt-backed work rows. Views stores recurring lenses.

When a task is opened, the product uses `?task=<id>` to show the receipt in place. That address works on thread and project routes, preserving the surrounding context while you inspect Changes, Checks, Output, Artifacts, and Technical details.

## Use the supporting surfaces

The authenticated route tree includes:

- **Inbox** for approvals, decisions, and work requiring attention.
- **Search** for accessible threads, projects, messages, documents, and files.
- **Views** for global saved lenses.
- **For you** for daily summaries, suggestions, and scheduled outputs.
- **Automations** for reusable and scheduled work.
- **Channels** for linked conversation surfaces.
- **Skills** and **Customize** for installed capabilities and connections.
- **Settings** for models, providers, approvals, data, projects, agents, and skills.

These are product views over shared state. An approval resolved from Inbox updates the task. A thread opened from Search remains the same thread. A task discovered through a project still carries the receipt created by its execution path.

## Configure work without leaving the shell

Settings → Models is the main BYOK surface. Add or replace provider credentials, enable the models you want in the picker, and choose a default. Settings → Approvals controls Strict, Balanced, or Relaxed posture and whether attached terminal sessions can resolve approvals.

Project settings hold general identity, repository binding, runtime configuration, guidance and memory, decisions and permissions, workflows, and the archive or restore boundary.

Use web when you need full configuration or the richest inspection surface. When you move to native or terminal clients, return through the same project, thread, or task identity rather than recreating the work.