linear-browser-automation

# Linear Browser Automation

Automate Linear workflows through UI interactions in the OpenClaw-managed browser.

## Execution mode

- Always use browser profile: `openclaw`
- Always run actions against host browser control
- Reuse an already-open, logged-in Linear tab in the managed browser whenever available.
- Do not open a new Linear tab if an existing authenticated Linear tab can be reused.
- Keep actions in one tab unless explicitly opening a new tab is required by user request.

## Standard workflow

1. Ensure managed browser is running (`profile="openclaw"`).
2. Check existing open tabs in managed browser and prefer a tab already on Linear.
3. If an existing Linear tab is found:
   - focus and reuse that tab
   - snapshot and detect auth state
4. If no Linear tab exists, open/navigate to `https://linear.app/`.
5. If on public landing page / unauthenticated state:
   - automatically navigate to `/login`
   - show a browser alert asking the user to log in to continue
   - wait for authenticated dashboard/workspace state
6. After login is complete and dashboard is visible, continue automatically from the same task context and same tab.
7. Resolve references from the snapshot.
8. Execute deterministic actions (click/type/select/press).
9. Re-snapshot and verify expected state before finishing.

## Required-input policy (hard rule)

For all Linear actions, always collect and confirm required details in chat before executing.

### 1) Create issue

Required fields:
1. Team (or project context that implies team)
2. Title

Optional fields (prompt if missing): description, priority, assignee, labels, due date.

Before submission, always present a summary block and ask:
- **`Proceed? (yes/no)`**

Only proceed on explicit **yes**.
Any other response (no/cancel/edit/silence) means do not submit.

### 2) Edit issue and comment on issue

Required fields:
1. Team name
2. Issue number/identifier (e.g., `POW-123`)

Hard rule:
- Do not run these automations when either team nam...