# Automations introduction

The first visit to the Your automations tab opens a short walkthrough of recurring runs and
the deployment's available features. Finishing or dismissing it is remembered
in this browser for the current user, server, and app mount. The info button
beside the Automations heading reopens it.

## Sub-features

- `first-visit`: show the introduction after identity, capabilities, and the
  automation list load successfully.
- `walkthrough`: Next and the numbered feature buttons select a step; Done,
  Maybe later, Close, and Escape dismiss it. Outside clicks do not dismiss it.
- `reopen`: the info button ("About automations") beside the Automations
  heading reopens the guide at its first step after it was dismissed. Closing
  it returns focus to that button.
- `examples`: See examples swaps the steps for three example automations, each
  with its schedule and prompt: a Slack bot answering product questions, a
  first look at new PagerDuty incidents, and a daily Dependabot merge. Back
  returns to the step the viewer left; Done dismisses the guide.
- `capabilities`: show periodic Jira/Slack/GitHub/Linear/PagerDuty checks only with session
  continuity and orchestration; show continuity and sandbox copy only when
  supported. Use the deployment's app name.
- `remember-dismissal`: local storage keeps dismissal across reloads, separately
  for each user, server, and mount. Another tab's dismissal closes an open guide.
- `responsive`: desktop uses two columns; narrow screens stack the illustration
  and show the selected feature's description.

## How to get to it (user POV)

- **Standalone web:** select Automations in the sidebar or Go to Automations in
  the command palette, or open `/tasks` directly.
- **Mobile web:** open Automations from navigation or open `/tasks` directly.
- **Managed embedded:** open Automations through the host app's navigation.
  The same page and dialog render inside the embedded app.

## Driving it with the repro environment

Preconditions: use a fresh browser context with no saved introduction dismissal.
No agent turn or provider credentials are needed.

- `tests/e2e_ui/scheduled/test_scheduled_tasks_page.py::test_automations_introduction_first_visit`
  covers desktop sidebar entry, mobile direct entry, the examples and Back, all
  four steps, Done, focus returning to New automation, and after a reload,
  reopening from the info button and opening New automation.
- For the command palette, select Go to Automations in a fresh browser context,
  dismiss with Maybe later, navigate away, and return. The guide stays closed.
- For managed, repeat in a deployment containing this UI version. Check the
  deployment's branding, dialog styling, scrolling, and dismissal after reload.
  Component coverage in
  `web/src/components/scheduled/AutomationsIntro.test.tsx` checks the embedded
  portal, user/server/mount isolation, capabilities, storage failures, and every
  dismissal action; it does not prove a deployed managed build.

## Gotchas

- Clearing local storage, using a different browser/device, or changing users or
  servers shows the guide again. Completion is not synced to an account.
- If an embedded host does not identify its backend, dismissal lasts only until
  the guide unmounts or the host configuration changes; it is not saved or shared with other tabs.
- If browser storage is blocked, the guide still closes but cannot remember the
  dismissal after remounting.
- Next, selecting a feature, and opening the examples do not mark the
  introduction as seen.
- The examples are read-only text with placeholder names (`#product-questions`,
  Payments API, `acme/web`); nothing copies them into the create dialog.
- Trigger templates check services periodically; this guide does not promise
  webhook delivery or a separate persistent memory store.
- Opening the Templates tab directly does not automatically show the guide.
  Its info button still opens it. Task detail pages do not show the guide or
  info button; returning to Your automations opens the guide if not dismissed.
- Automations task creation, execution, and detail pages are separate journeys.