Aside Browser Guide: Setup, Pricing, Permissions, and Practical Workflows

한국어로 읽기

Aside Browser goes beyond reading websites and answering questions: it uses browser, account, and file context you authorize to carry out multistep tasks. You might research products, build a comparison table, or consult a signed-in service and prepare a draft for review.

The useful question is not whether it can “do everything,” but which sources it should use, what it should produce, and where it must stop. This guide covers setup, permissions, practical requests, and pricing using official documentation. It is not a benchmark of task success rates or time saved.

Sources checked September 16, 2026. Features, menus, and plan terms may change.

1. What changes when AI works in your browser?

The distinction is context and actions, not longer answers. Instead of repeatedly copying information into a chat, you can attach a page and specify websites and deliverables. Official documentation covers browsing, file operations, history searches, authorized credential autofill, and approval requests within multistep work. That does not guarantee equal support across websites or eliminate human review.

Goal	Delegate	Review yourself
Understand a document	Summary with supporting passages	Missing conditions or exceptions
Compare pages	Consistent research and a table	Sources, dates, billing differences
Work with an account	Authorized retrieval and preparation	Account, access scope, external changes

Other chatbots also offer search and tools. Judge Aside by how much browser context you currently move manually, and whether you can delegate work in small, reviewable pieces.

2. Set up without replacing everything at once

The official getting-started guide specifies macOS 15.0 or later. The download site also lists Windows 10 22H2 or later, or Windows 11. These steps describe Mac setup; Windows users should follow the installer instructions for their operating system. Recheck chip compatibility and other requirements when downloading.

1. Download from the official site. Use the Aside download page. On Mac, open Aside.dmg from Downloads, drag Aside into Applications, and launch it.
2. Sign in to Aside. This is separate from signing in to services used for tasks. Check your organization's external-tool policy before connecting work services.
3. Choose the correct browser profile. Onboarding imports cover history, cookies, and bookmarks. Verify the profile name rather than mixing personal and work context.
4. Check passwords and model connections. Installation does not automatically resolve every website login or model entitlement. Documentation distinguishes Aside's default models, Subscription, and API connections under Settings → Models → Providers. Menu labels may vary; check provider names and connection status.
5. Start with a public page. Request a source-backed summary before using sensitive material or sending anything.

Successful setup means the right sites open, account contents stay distinct, and you can run a task and inspect its sources. Keep your existing browser data; there is no need to migrate all important work immediately.

Already paying for an AI subscription? Jump to section 7 for eligibility, connection steps, and troubleshooting.

3. Specify the target, output, and limits

The new-tab input offers Search and Ask AI modes. Documentation labels the task field Ask AI a task, @ for context; @ attaches available context. From an existing page, open the side panel and verify the attached page title and hostname before submitting.

Read the product’s official pricing page currently open in this tab.
Separate free-plan limits, paid billing cycles, and conditions you cannot verify in a table.
Include source links. Do not make payments or change account settings.

Completion means every entry is traceable, not merely that a table exists. Check that annual prices expressed monthly are not presented as monthly-billed prices, and that missing limits were not guessed. Naming the exact site also helps avoid similarly named services.

4. File access and tool permissions are different controls

New tasks offer permission modes such as Read only, Guard, and Full access. Official documentation describes Guard as the default: it works within approved folders and requests access elsewhere. Full access broadens file reading and writing on the computer. These file-scope descriptions do not mean every website action is automatically approved.

File scope and tool rules are separate controls. Full access is not blanket approval for every web action.

Settings → Agents separates Sandbox, File permissions, and Tool permissions. Tool rules use Allow, Ask, and Deny, with Deny taking precedence. Task-specific settings also apply, so inspect the current task as well as global settings. Initially allow only necessary folders and operations, and explicitly require a stop before sending, publishing, or deleting.

Documentation describes an autofill boundary that keeps saved password values hidden from the agent. This does not mean customer records or signed-in documents can never leave your device. The privacy policy says task history and artifacts are stored locally, but selected context needed to fulfill a request may be sent to hosted models. Local storage is separate from data transmitted to models or external services. For sensitive work, review the policy, your model provider's terms, and organizational rules together.

5. Three concrete requests to adapt

A. Compare AI tools consistently

Supply candidate names, official URLs, and required features. Limit the deliverable to a table of capabilities, restrictions, price conditions, and the date checked.

Using only official documentation for the three tools listed below, compare Korean-language support, file uploads, and team sharing.
Mark anything you cannot verify as “Unverified,” and include evidence links.
Do not sign up, install anything, or make payments.

Review whether each row compares equivalent features. Accepting Korean input is different from offering a Korean interface. Turn missing evidence into follow-up questions instead of filling gaps with assumptions.

B. Audit published blog posts

Provide actual public post URLs. Request a read-only audit with issue locations and suggested fixes, not simultaneous edits in the administration interface.

Check the titles, body images, and source links in the public posts listed below.
For each issue, provide a table with the post URL, location, observed evidence, and suggested fix.
Distinguish images outside the viewport that have not loaded yet from broken images. Do not edit the posts.

Revisit the reported location before deleting anything. Authorize the specific post and edit scope separately. For a code-and-illustration article such as the Diagram Design guide, also check where commands should be entered and whether image descriptions explain the visuals.

C. Prepare a recurring product-update report

Choose products and official release-note sources. Validate the report format and evidence standards manually before scheduling recurring work.

Every Monday at 9:00 a.m. Korea Standard Time, check the specified products' official release notes.
Summarize changes since the previous report, affected users, and restrictions requiring verification.
If nothing changed, say so. Do not send reports externally or publish to a blog.

Review instructions, schedules, and enabled status in Settings → Routines. Cron starts a new task on a schedule; Heartbeat continues an existing conversation. Registration is not proof of execution. Check the first result, login state, pending approvals, and the environment that will run it.

6. Separate browser-plan pricing from model costs

The official pricing page lists Free, Pro, and Max. Free includes 500 credits per month and up to three active routines. Credits are not question counts: consumption can vary by task and model. Do not read this as “500 free questions.”

Plan	Monthly billing price	Listed differences
Free	US$0	500 credits/month; up to 3 active routines
Pro	US$20/month	Higher usage, Ultrabrowse, unlimited active routines, Channels
Max	US$200/month	Pro features, greater usage, early-access programs

Monthly-billing figures from the official price list. Check annual billing, taxes, and final charges separately. Remote control through Channels is not the same as smartphone browser-app availability.

Connecting an existing AI subscription or API key is separate from Aside plan credits. Installing the browser does not cancel connected services' subscription or API charges. Check the actual billing provider and usage under Settings → Plan & Usage and model connections. Consult the official pricing page for current amounts and feature availability; upgrade when the required benefits are clear.

7. Connect an existing AI subscription

Aside can connect certain existing AI subscriptions, so the model service you already pay for can be selected in the browser. This is different from merely being signed in on an AI provider’s website. A web session alone does not connect a model to Aside, and it is not permission to copy a password, token, or API key into a chat. Keep those credentials private and use the provider connection flow shown in Aside.

According to the Aside AI documentation, open Settings → Models → Providers, then choose Connect and Subscription. Complete the provider’s OAuth sign-in in the popup and return to Aside. Connected entries are labeled Subscription; some providers also show usage indicators. That label confirms the connection type, not unlimited use or access to every model.

Subscription listed by Aside	What the connection uses	Important check
ChatGPT Subscription	ChatGPT Plus or Pro; OAuth sign-in to the eligible account	Confirm the correct personal or work account before authorizing.
Claude Subscription	Claude Pro or Max, as listed by Aside	Read the Claude policy note below and verify the current implementation before connecting.
GitHub Copilot	OAuth sign-in to the eligible GitHub account	Check organization policy and the account’s Copilot entitlement.

Subscription providers are separate from the API-provider list. Aside’s documentation includes Google among API options, but it does not list a paid Gemini subscription in its Subscription list. That distinction is not evidence that a Gemini subscription can never be supported; it means the current public list should be checked before making a purchasing or connection decision.

Example: connect a ChatGPT subscription

1. Confirm eligibility first. Sign in to the ChatGPT account that actually has Plus or Pro, and decide whether organizational rules allow the connection.
2. Open Providers. In Aside, go to Settings → Models → Providers.
3. Start a subscription connection. Select Connect, then Subscription.
4. Select ChatGPT Subscription. Choose ChatGPT Subscription for your Plus or Pro account, rather than an API-key option.
5. Review the official popup. In the provider’s OAuth window, verify the account and requested permissions, then sign in. Do not enter credentials into the Aside task chat.
6. Confirm the return state. Back in Aside, check that the provider is shown as Subscription. If available, inspect the displayed usage information.
7. Choose the task model and test carefully. Open Settings → Models → Task models, select the default model or relevant categories, then ask for a summary of a public document. Check the task’s actual model selection or result details, rather than assuming the newly connected provider was used.

Five checkpoints summarizing the detailed connection steps. Select the image to enlarge it.

Claude policy note: Anthropic’s legal and compliance documentation says third-party applications must not provide a Claude.ai login or relay requests using subscription credentials. It also describes a conditional allowance for an end user directly logging in with their subscription in an unmodified Claude Code binary. Aside’s public documentation does not establish whether its implementation meets that condition. Before connecting Claude, verify the current implementation and policy, and do not seek token-extraction workarounds. Aside listing a provider is not a provider guarantee.

Common connection problems

• The sign-in popup never appears. Allow popups for Aside and retry the normal connection flow. A blocked OAuth window cannot be replaced by pasting credentials.
• The wrong account or an organization restriction appears. Sign out of the unintended account in the provider flow, then review the account, workspace, and company policy before authorizing.
• The provider is connected but tasks still use another model. Revisit Settings → Models → Task models. Do not assume a successful connection changed the default model or every category.
• A limit or reauthentication prompt appears. Subscription limits, provider-side access rules, expiry, and renewed authorization can all affect a task. OAuth success does not promise unlimited usage or every-model access.

Quick FAQ

Can I connect a paid Gemini subscription? Check the current Providers screen and official Aside documentation. Google is listed among API options, while a paid Gemini subscription is not in the published Subscription list, so do not assume the two routes are interchangeable.

Does ChatGPT Plus include OpenAI API usage? No. OpenAI explains that ChatGPT billing and API-platform billing are managed separately, so ChatGPT Plus or Pro does not by itself pay API charges. Read OpenAI’s billing guidance before selecting an API route.

The provider type determines which account’s billing and usage limits you need to check.

Do I need a paid Aside plan? Aside’s pricing page lists Bring your own subscription on Free. That option is separate from paid Aside features and separate from each provider’s own subscription or API billing. Review both the plan and provider terms when deciding what to connect.

8. When a task stalls or goes off course

• Find the waiting condition. Look for approval requests, questions, or login checks. Reauthentication and multifactor verification are different from task errors.
• Correct the direction explicitly. Steer delivers instructions during a running task; Queue applies a new message after the current run. Name the intended sites and prohibited actions.
• Reduce the scope. Separate collection, review, editing, and external changes. Verify retrieval and table creation first, then expand from a successful small task.
• Compare the completion message with reality. Open files, check links, and verify that websites accepted changes. When reporting an error, include time, site, expected result, and actual result, without credentials or sensitive data.

Bottom line: Start with one small reading task. Attach the target page, define the output and prohibited actions, then verify sources and completion evidence. Expand into file operations and routines once you have repeatable review criteria.

Official references

• Get started: installation, imports, and first tasks
• Set agent permissions: file scope and tool rules
• Use routines: recurring tasks and management
• Aside pricing

Input locations and task behavior also reference Browser basics, Run tasks, and Side panel.