# Frequently asked questions.

FAQ

Start with a concise answer, then follow the canonical page when you need the full context.

## What is an Oysterun Host?

The Host runs beside a supported agent provider for the same operating-system user and owns the Sessions, files, and runtime state that your Clients reach. [Review the architecture.](/overview/en/index.html#architecture)

## Do the phone app and browser create different Hosts?

No. They are two Clients for the same Host identity and Session state when you open the same current Host URL. [See how Oysterun works.](/overview/en/index.html#how-it-works)

## Where should I start?

Follow [Getting Started](/getting-started/en/index.html) for one current path from Host readiness to a useful Session you can recognize and reopen.

## What do I need before setup?

Use a currently supported macOS or Linux Host with Node.js 20 or newer, npm, and a supported provider authenticated for the same operating-system user. [Check the complete first-time path.](/getting-started/en/index.html)

## Does Connected or Working mean my response is complete?

No. Wait until the working state clears and the provider's final response is visible. [Learn how to read agent activity.](/docs/understand-agent-activity/en/index.html)

## Where are task instructions?

Use [Docs](/docs/en/index.html) to search the current published guides or browse them by task group.

## Is every provider, Host configuration, and future feature guaranteed?

No. Oysterun is Beta software, and available surfaces depend on the current provider and Host configuration; roadmap dates are not delivery promises. [Review current features and maturity.](/overview/en/index.html#features)