Authentication

Each operation declares how it connects to its target. Public operations run immediately. Cookie and header operations read site credentials. Browser operations use a managed or existing browser session.

Start with the error envelope

Run the operation once. When login is required, Uni-CLI returns auth_required with the matching setup command.

unicli auth setup <site>

This shows the fields expected by the adapter and where Uni-CLI will read them.

Import a browser login

List local browser profiles:

unicli browser profiles --json

Import credentials from a selected browser:

unicli auth import <site> --browser chrome

Then validate the saved site credentials:

unicli auth check <site>

auth list shows the sites configured for the current user.

unicli auth list

Use a live browser session

Some operations work through a signed-in tab. Start by reading browser health:

unicli browser doctor --json

For background control of an existing Chrome profile:

unicli browser --background start

For visible foreground control:

unicli browser --focus start

A browser command can also require the expected domain and path, which keeps the action attached to the intended page.

Where credentials live

Explicit imports are stored per site under ~/.unicli/cookies/. Live browser values stay with the active browser session. Uni-CLI reports the selected source in its diagnostic output.

Diagnose a login problem

unicli auth check <site>
unicli doctor cookies
unicli browser doctor --json

Use the checks[].next_step field from browser doctor as the next command. It reflects the installed browser, available profiles, broker state, and managed policies on the current machine.