# Agent runs
Source: https://docs.strawberrybrowser.com/ai/agent-runs
Understand agent work, work traces, sub-agents, feedback requests, interrupted work, and how to review what Strawberry did.
An agent run is a companion doing work, not just replying. It may search, open tabs, read web pages, use connected apps, create files, run code, ask for feedback, or spawn sub-agents.
## What agent runs can do
Depending on permissions and available tools, a companion can:
* Search the web
* Read and compare pages
* Open and navigate tabs
* Use connected app tools
* Read and write workspace files
* Create reports, spreadsheets, documents, and artifacts
* Ask follow-up questions
* Run sub-agents for scoped investigations
## Work traces
Strawberry shows work traces so you can inspect what happened. A work trace can include:
* Searches
* Tool calls
* File operations
* Browser actions
* Sub-agent activity
* Questions and feedback requests
* Progress from a `PLAN.md`
Use the work trace to audit sources, understand decisions, and resume from partial work.
Completed connected-app actions may include a short **Go to ...** button that opens the created or updated item, such as a document, spreadsheet, email, draft, or calendar event.
## Sub-agents
Sub-agents help split complex work into smaller tasks. For example, a market research task might spawn separate sub-agents for competitors, pricing, customer reviews, and source validation.
Each `strawberry.startAgent()` sub-agent can get its own `PLAN.md` in that sub-agent's session folder.
## Feedback requests
Companions can ask for feedback when they need a decision, permission, missing data, or human judgment. Some feedback requests appear in the chat, sidebar, or right-side panel.
## Interrupted sub-agents
If a sub-agent is interrupted, Strawberry can show a banner so you can reopen or resume the thread. Review the context before continuing, especially if the task involved browser state, credentials, or an external app.
## Best practices
* Give clear success criteria before starting a broad agent run.
* Ask for source links and confidence levels when research quality matters.
* Review work traces before relying on a generated file.
* For sensitive workflows, say what the companion may do automatically and what requires approval.
* For long tasks, ask Strawberry to create a plan first.
# Chat
Source: https://docs.strawberrybrowser.com/ai/chat
Use Strawberry chat, queued follow-ups, steering, stopping, attachments, context, and companion selection.
Chat is the main place where you talk to companions, attach files, reference tabs, review work, and continue tasks.
## Chat history
Chat history is saved to your Strawberry account and restored across signed-in Strawberry clients.
Chat titles and lightweight metadata are stored separately from the encrypted chat payload. Messages, drafts, and detailed chat data are encrypted before they are saved on Strawberry servers.
History search can find chat titles and conversation text. Results depend on what has been indexed on this device, so older chats may take time to appear.
## Queued follow-ups
When a chat is already responding, you can type another message and send it. Strawberry adds it to that chat's queue.
Queued messages:
* Run one at a time in the order sent.
* Stay specific to the current chat.
* Include their own attachments, files, selected text, windows, and tabs.
* Show a short text preview above the chat input.
When a queued message starts running, it leaves the visible queue. Remaining items stay visible.
## Steer a queued message
Click **Steer** on a queued message to make it run next. Strawberry stops the current response and sends the steered message first. Other queued messages stay queued.
## Stop and send immediately
Press `Cmd+Enter` on macOS or `Ctrl+Enter` on Windows/Linux while a chat is responding to stop the current response and send the typed message immediately instead of queueing it.
If the chat input is empty and queued messages are waiting, pressing `Enter` stops the current response and sends the next queued message.
## Attach files and context
You can paste an image or file into chat, drag files or folders onto the input, or use the file picker. Strawberry copies attachments into the chat before sending so the companion can see them and open the saved files.
A new chat waits for that copy to finish before it opens. If Strawberry cannot prepare an attachment, your message and attachments stay in the input so you can retry or remove the file.
You can also give a companion tab context, selected text, files, or explicit instructions about what to inspect.
When chat is open next to a page, Strawberry automatically includes the visible page context when you send. In split view, both visible pages are included. Selected text from the focused pane appears in the input like other selected text; current-page page chips appear after the message is sent.
Use `@` in the chat input to mention apps, open website tabs, and full Chats. The tab list includes
top-level website tabs that can host Chat and standalone Chats. Open pages inside a Chat stay with
that Chat instead of appearing as separate top-level choices. Chats use their current titles, so
you can find them by name.
## Companion selection
Use the companion picker in chat to choose who should handle the task. Press `Cmd + .` on macOS or `Ctrl + .` on Windows to cycle through companions. Use `Shift` to cycle backward.
## Good chat prompts
Good prompts explain:
* Goal
* Context to use
* Constraints
* Output format
* Whether the companion should ask before acting
```text theme={null}
Research these 25 companies.
Use their official websites and LinkedIn pages when possible.
Return a spreadsheet with company, website, HQ, size, target buyer,
evidence URL, and a one-sentence reason they fit.
Ask me before sending any outbound messages.
```
## Planning complex work
Ask your companion to draft an approach before acting when a task has important assumptions, risks, or several phases. A plan can be lightweight in chat or durable as a `PLAN.md` file with reviewable todos for substantial work.
# Companions
Source: https://docs.strawberrybrowser.com/ai/companions
Learn what companions are, how they differ, what they can access, and when to create separate companions.
Companions are Strawberry's AI assistants. They live inside the browser, can use the context you provide, and can be specialized for different kinds of work.
A companion can have:
* Its own instructions and personality
* Companion-specific files
* Companion-specific memory
* Companion-specific skills
* Companion-specific routines
* Access to built-in app connections for your Strawberry account, subject to permissions
* Shared access when you share the companion with another user or team
## When to use one companion
Use one primary companion when your workflows are closely related and should share the same context. For example, a founder might keep one companion that understands their company, tone, customers, and calendar.
## When to create multiple companions
Create separate companions when you want different instructions, memories, or routines:
* A sales companion for outreach and CRM work
* A recruiting companion for sourcing and candidate screening
* A research companion for market maps and competitive analysis
* An operations companion for recurring inbox, invoice, and reporting workflows
## Companion settings
Open a companion's settings to manage its general details, skills, routines, files, and models. Additional options, such as **Channels**, appear when available.
The **Files** tab opens that companion's folder. Choose **Open in Library** to continue browsing there. Select your personal or team workspace in Library to find other files.
Manage connected apps at `strawberry://settings/integrations`. Use **Share Companion** in the companion settings header to manage sharing.
## Companion-specific skills
When you create a skill from companion settings, Strawberry saves it in that companion's own skills folder. These skills appear before global skills in the chat slash menu and follow the companion when shared.
## Sharing companions
Companions can be shared with another Strawberry user, specific team members, or a whole team. Sharing grants access to that companion's synced folder, including instructions, memories, observations, and companion-specific skills.
Direct email shares between team members are accepted automatically. A teammate can open the shared companion right away. Shares outside your team can remain pending until the recipient accepts them.
Chat history is not shared. When someone opens a shared companion, they start their own chat with it.
> [!WARNING]
>
> Companion sharing currently grants edit access. Recipients can update the companion's settings,
> memories, and skills until sharing is stopped.
## Best practices
* Put stable, reusable context in memory or skills instead of repeating it in every chat.
* Use separate companions for workflows with different tone, instructions, or reference files. Creating a companion does not create a separate set of connected app accounts.
* Review companion sharing before putting sensitive files or instructions into a companion folder.
* Keep companion instructions specific enough to guide behavior, but not so rigid that the companion cannot ask clarifying questions.
# Credits and usage
Source: https://docs.strawberrybrowser.com/ai/credits-usage
Understand Strawberry credits, monthly plan credits, top-ups, rate-limit windows, agent costs, and why credits can drop.
Credits are Strawberry's usage unit for AI work.
## Core rules
* Browsing websites without companion help does not consume credits.
* Any companion AI response can consume credits, including normal chat replies.
* Agent runs, web research, app actions, and complex workflows usually consume more credits than simple chat messages.
## Which account pays
Without a team membership, your Personal account pays for AI work. If you belong to a team, a team is your paying account.
If you belong to several teams, open `strawberry://settings/account` and choose **Paying account**. On the web, use [Billing & usage](https://strawberrybrowser.com/account/billing). This choice applies to future work across your Strawberry account. Changing the team you are viewing in team settings does not change which team pays.
Strawberry uses the paying account's available credits first. If those cannot cover the work, eligible Personal credits can be used automatically, including remaining paid plan credits, top-ups, and eligible bonus credits. The free Personal allowance is excluded. Another team's credits are never used automatically.
Personal and team balances keep their ownership. Switching teams does not transfer credits, and using Personal credits as a reserve does not change your paying account.
## Why credits can drop without an agent run
A regular chat turn still calls an AI model. Model input and output tokens are billed as usage cost even when no separate agent block appears.
Adaptive thinking is used when the selected model supports it.
Your plan and companion settings can affect which model is used. Model choice and longer requests can use more credits.
## Start large tasks with a sample
For a large request, ask the companion to complete a small sample first. Review it before asking for the full batch. This can catch mistakes early and help you control usage on any plan.
## How to check usage
1. Open `strawberry://settings/account`.
2. Review **Credit Usage**, including **Available now**, your credit balances, and refill times.
3. If you belong to several teams, check **Paying account**.
4. In a chat, open the content panel to see that chat's usage and any active rate-limit window.
The web [Billing & usage](https://strawberrybrowser.com/account/billing) page also shows account usage and billing options.
## Understand your balances
* **Available now** shows credits you can currently use. It can be lower than your remaining monthly allowance when a rate limit is active.
* **Plan credits** includes subscription allowances and recurring team pools.
* **Extra credits** includes top-ups, bonuses, and other additional credits. These can have different expiry rules; purchased top-ups do not expire at month end.
* The credit breakdown shows which balances can pay next, including eligible Personal reserves when a team pays first.
Included credits are normally used before purchased top-ups when they are available. Top-ups can also pay while monthly credits remain but are temporarily held back by a rate limit. Follow the displayed order and refill times when deciding whether to wait or add credits.
## Rate limits versus plan credits
Plan credits are your monthly included usage. Rate-limit windows are short-term guardrails that can temporarily limit activity even if you still have monthly credits.
If a rate-limit window is exhausted, wait for the displayed refill time or use eligible extra credits. An ordinary top-up purchase adds credits you can use without restarting the plan's window.
## Running low
You can:
* Ask for a smaller task or a sample first.
* Wait for the displayed plan refill time.
* Buy top-ups when you can manage the paying account.
* Upgrade your personal plan, or ask a team admin or owner about your seat.
* Select another eligible team under **Paying account** if you belong to several teams.
Team admins and owners can buy shared top-ups. There is no automatic pay-as-you-go team overage. If no eligible credits are available, work pauses until credits become available.
# AI permissions
Source: https://docs.strawberrybrowser.com/ai/permissions
Control what companions can do through permission mode, connected app tool permissions, folder access, and chat-specific approvals.
AI permissions let you decide what companions can do automatically and what requires approval.
Open AI permissions at `strawberry://settings/ai-permissions`.
## Permission mode
1. Open `strawberry://settings/ai-permissions`.
2. Under **Permission Mode**, choose:
* **Default**: standard permission rules for each action type.
* **Ask Always**: ask before actions covered by approval controls when you have not already saved a permission for them.
Saved permissions still apply in **Ask Always** mode, and some actions, such as app reads without an approval control, can proceed without a prompt. Review **Permanent Permissions** and existing chat approvals as well as the mode. Folder access has its own controls.
## Connected app tool permissions
An app may offer permissions for specific actions. The actions listed vary by app; not every read or action has an individual control.
1. Open `strawberry://settings/integrations`.
2. Open an integration's detail page.
3. If the page has **Permissions**, set each listed action to:
* **Ask every time**
* **Always allow**
* **Disable action**
You can also see configured permissions at `strawberry://settings/ai-permissions` under **Permanent Permissions**.
## Permanent and chat-specific permissions
* **Permanent permissions** apply across chat sessions. Manage them per integration.
* **Chat-specific permissions** apply to that chat. Finishing a response or closing its tab does not create a new chat or remove its approvals.
## Action approval cards
When Strawberry asks you to approve a connected-app action, review the card before allowing it. Editable cards, such as email sends, let you change recipients, subject, and body before execution. For Gmail sends, your Gmail signature is inserted into the editable message body so you can change or remove it before sending.
## Folder access requests
When a companion needs access to local folders, Strawberry can ask for folder permissions. On Windows, folder grants are especially important for sandboxed file access.
Only grant folders that are relevant to the task.
## Sub-agent feedback requests
Sub-agents may ask for help when they need a decision, missing information, or approval. These requests can surface in chat and related UI.
## You stay in control
Use stricter permissions for workflows that can send messages, spend money, mutate business systems, delete data, or access sensitive local folders.
> [!WARNING]
>
> Do not set broad "Always allow" permissions for tools you do not fully trust. A narrow permission
> setup is usually better than a convenient one for sensitive apps.
# Plans and todos
Source: https://docs.strawberrybrowser.com/ai/plans-and-todos
Use Strawberry's PLAN.md system for durable planning, visible progress, and sub-agent work.
Strawberry has a built-in plan and todo system for multi-step work.
The source of truth is a `PLAN.md` file at the root of the chat session workspace. The companion creates and updates this file with normal file tools. Strawberry parses structured todo blocks and shows the current plan in the chat UI.
## How plans work
* One chat session has one canonical `PLAN.md`.
* Each sub-agent can have its own `PLAN.md`.
* Markdown headings and prose are used for plans, notes, sources, and decisions.
* Structured todo blocks represent user-visible execution state.
* Plans stream into the chat UI while they are written.
* Strawberry reparses the plan after successful file writes or edits.
## Todo format
Todos use XML-style blocks inside markdown:
```xml theme={null}
Find EU suppliers
in_progress
Capture URLs, pricing, lead times, and whether each supplier ships to Sweden.
```
Common states include `pending`, `in_progress`, and `completed`.
## What you see
In chat, Strawberry can show:
* The plan summary
* Current todo state
* Sub-agent progress
* Related tool activity
* A link to open the full plan file
## Ask for review
Tell your companion explicitly when you want it to pause after drafting an approach:
```text theme={null}
Create a plan first. Do not start execution until I approve it.
```
You can then approve or revise the approach in chat.
## Best practices
* Ask for a plan when the task has multiple phases, dependencies, or risk.
* Keep plan todos specific and testable.
* Ask Strawberry to update the plan when scope changes.
* Use plans for work you may need to resume later.
# Memory and skills best practices
Source: https://docs.strawberrybrowser.com/best-practices/memory-and-skills
Decide what belongs in Strawberry memory, what belongs in skills, and how to keep both useful over time.
Memory and skills solve different problems.
* **Memory** stores stable facts and preferences.
* **Skills** store reusable process.
Use both when you want companions to improve without long prompts.
Strawberry also ships a Memory Best Practices skill for companions. Use it when asking a companion to clean up, reorganize, migrate, or review memory files.
## Put facts in memory
Good memory:
```text theme={null}
Our ICP is B2B SaaS companies with 50-500 employees in the Nordics.
Primary buyer titles are VP Sales, Head of RevOps, and Founder.
```
Avoid:
```text theme={null}
Research these 12 companies by Friday.
```
That is a task, not durable memory.
## Put process in skills
Good skill:
```text theme={null}
When evaluating a prospect, inspect website, LinkedIn, funding news,
and CRM history. Score fit from 1-5 and cite evidence.
```
Avoid putting this process in memory unless it is a stable preference and not an executable workflow.
When a companion completes a repeatable workflow well, ask it to save the process while the details are fresh:
```text theme={null}
Create a skill for me from this workflow.
Ask me targeted questions if anything is missing before you save it.
```
## Keep both scoped
Use companion-specific memory and skills when only one companion should use the context.
Use global or shared memory and skills when all relevant companions should use them.
## Maintain over time
Review memory and skills when:
* Your product changes.
* Your ICP changes.
* You change tone or messaging.
* A routine starts producing noisy results.
* A companion repeats outdated assumptions.
* Saved memory has grown repetitive or includes long copied documents.
## Ask Strawberry to help maintain them
Useful prompt:
```text theme={null}
Review this chat and suggest only durable facts that should be saved to memory.
Do not save temporary task details. Separate facts from workflow improvements
that belong in a skill.
```
For cleanup:
```text theme={null}
Use the Memory Best Practices skill to review your memory files.
Keep reusable facts concise and keep detailed reference material in separate files.
```
If the same workflow should run on a schedule, create a routine instead:
```text theme={null}
Do this workflow every Tuesday morning.
Ask me what trigger, approval rules, and notification rules you need.
```
## Safety
Do not store secrets, credentials, personal data, or confidential customer data in memory or skills unless the scope is correct and there is a clear reason.
# Prompting best practices
Source: https://docs.strawberrybrowser.com/best-practices/prompting
Work with Strawberry companions by stating the outcome, planning together, asking targeted questions, and saving useful workflows as skills or routines.
Good Strawberry prompts are practical. Start by telling the companion what you want to do, then ask it to plan the work with you before it starts executing.
## Start with the outcome
For important tasks, begin with plain language:
```text theme={null}
I want to do [the thing].
Can we plan it out together before you start?
Ask me targeted questions that would help you do this better.
```
This works well because Strawberry can help define the scope, choose useful sources, spot missing context, and turn a vague request into a concrete plan.
## Example official skill
```text theme={null}
I want to build a shortlist of potential customers in Sweden and Denmark.
Can we plan it out together before you start?
Ask me targeted questions about ICP, source quality, output format, and what
you are allowed to do automatically.
```
After the companion asks questions, you can agree on details such as:
* Which sources to use
* How large the first sample should be
* What the final output should look like
* What requires approval
* How the companion should verify the work
## Give the companion permission boundaries
Say what it can do automatically and what it must ask about.
Useful boundaries:
* "Read only. Do not send, update, delete, or buy anything."
* "Draft emails but do not send them."
* "Create a sample of 10 rows first."
* "Ask before opening paid tools."
* "Use my CRM only for deduplication."
## Ask for verification
When accuracy matters, ask for:
* Source links
* Confidence notes
* Rows with missing data
* Assumptions
* A summary of how the companion checked its work
## Use memory and skills
Put stable facts in memory. Put repeatable process in skills. Then prompts can be shorter.
If a chat handles a workflow well, ask:
```text theme={null}
Create a skill for me from this workflow.
```
If the workflow should happen on a schedule, ask:
```text theme={null}
Do this workflow every Tuesday morning.
```
Strawberry can turn the successful pattern into reusable instructions or a routine, then you can review and adjust it.
## Common mistakes
* Asking for "everything" without a scope
* Omitting the source of truth
* Not saying what format you want
* Letting a companion infer approval rules
* Asking for a huge batch before testing a sample
* Repeating a successful workflow manually instead of turning it into a skill or routine
## Better follow-ups
Instead of restarting, steer the current task:
```text theme={null}
Keep the same table, but add a confidence column and only use official sources
for employee count.
```
# Research workflows
Source: https://docs.strawberrybrowser.com/best-practices/research
Run higher-quality Strawberry research with source rules, sampling, structured outputs, confidence, and review.
Research tasks are where Strawberry can save large blocks of time, but quality depends on clear instructions and review.
## Start with the decision
Tell Strawberry what decision the research supports.
```text theme={null}
I am deciding which 20 companies to prioritize for outbound this month.
Research fit, urgency signals, and likely buyer title.
```
The decision helps the companion choose sources and avoid irrelevant detail.
## Define source rules
Good source rules:
* Use official websites first.
* Use LinkedIn for company and people context.
* Use primary filings or databases when relevant.
* Avoid old blog posts unless they are the only available source.
* Mark uncertain data instead of guessing.
## Use samples before scale
For large tasks, ask for a representative sample first:
```text theme={null}
Do the first 10 companies, show me the output, and wait before scaling to 100.
```
This prevents wasted credits and catches formatting issues early.
## Request structured output
Use a table or spreadsheet when you need to compare results.
Include columns such as:
* Name
* URL
* Source
* Evidence
* Confidence
* Notes
* Next action
## Ask for gaps
Require a "missing or uncertain" section. This is better than forcing the companion to fill every cell.
## Review before acting
Before sending messages, updating CRM, or making business decisions, review:
* Source quality
* Data freshness
* Duplicates
* Uncertain rows
* Whether the output matches your constraints
## Best-practice prompt
```text theme={null}
Research 20 competitors in this market.
Use official websites, pricing pages, product docs, and recent primary sources.
Return a table with positioning, target customer, pricing model, strongest claim,
weakness, source URL, and confidence.
Do not guess. If data is missing, write "not found" and explain where you looked.
```
# Routine best practices
Source: https://docs.strawberrybrowser.com/best-practices/routines
Design useful routines that trigger at the right time, avoid noise, combine related actions, and ask for approval.
Routines are most useful when they are narrow, event-driven, and clear about what counts as worth notifying you.
You do not need to start from a blank routine editor. After a chat handles a workflow correctly, tell the companion:
```text theme={null}
Do this workflow every Tuesday morning.
```
Ask it to collect the missing details before it creates the routine.
## Start with the trigger
Choose the trigger that matches the job:
* Daily routine for morning briefings
* Interval routine for frequent checks
* Cron expression for advanced schedules
* App trigger for events such as new email
## Combine related instructions
If multiple actions happen from the same trigger and share the same context, put them in one routine prompt.
Good:
```text theme={null}
When new emails arrive, identify receipts, extract amount and vendor,
save attachments to the accounting folder, and draft a note to my bookkeeper.
```
Less efficient:
```text theme={null}
Create one routine for identifying receipts and another routine for saving receipts.
```
Each routine execution runs its own AI call, so related instructions are often cheaper and easier to review in one routine.
## Define notification rules
Tell the routine when to notify you.
```text theme={null}
Notify me only when a customer email is urgent, a payment looks overdue,
or a reply needs my approval. If nothing needs action, delete the automatic chat.
```
## Keep routines scoped
Avoid routines that inspect every connected app without a reason. Scope by account, folder, label, channel, project, or keyword when possible.
## Use approval gates
For routines that can send messages or update systems, ask Strawberry to draft and notify first.
```text theme={null}
Draft the reply and notify me. Do not send until I approve.
```
## Review run history
Open `strawberry://routines/history` or a routine detail page to review run history. Use it to reduce noise, catch failures, and tune prompts.
If a routine improves after tuning, ask the companion to update the routine prompt or create a skill that captures the refined workflow.
## Good starter routines
* Daily calendar, email, and Slack briefing
* Weekly pipeline risk check
* Invoice and receipt forwarding
* Meeting follow-up drafting
* New lead deduplication and enrichment
* Competitor or target account monitoring
# Security and control best practices
Source: https://docs.strawberrybrowser.com/best-practices/security-and-control
Use Strawberry safely with permissions, app access, shared companions, public links, account deletion, and human review.
Strawberry is powerful because companions can use real context and tools. Use that power with clear boundaries.
## Start read-only
For a new workflow, start by allowing reading and drafting. Add write actions only after you trust the prompt and output.
Good default:
```text theme={null}
Read the relevant context and draft the update. Do not send, delete,
purchase, invite, or update records without asking me first.
```
## Use permission settings
Review:
* `strawberry://settings/ai-permissions`
* `strawberry://settings/integrations`
* Per-integration tool permissions
* Folder access prompts
* Routine permissions
Permission settings cover the actions listed for each app. Some reads do not have a separate control, and saved allowances still apply in **Ask Always** mode. Review the connected account itself when deciding what information a companion can access.
## Be careful with always-allow
Only use **Always allow** for low-risk actions you understand. Avoid always-allow permissions for tools that send messages, change records, delete data, invite users, or spend money.
## Treat shared companions as editable
Companion sharing currently grants edit access. Recipients can update settings, memories, and skills until you stop sharing.
Do not put sensitive files or private instructions into a companion you plan to share broadly.
## Public file links
Anyone with a public file link can view the current synced file or folder until you revoke the link. Later edits and files added to a shared folder can become public through the same link. Share a separate, unchanged copy if you want to publish a fixed version. Revoking a link does not remove downloaded copies.
## Destructive actions
Review destructive actions carefully:
* Account deletion
* Team deletion
* Clearing cookies and site data
* Disconnecting app accounts
* Removing members
* Revoking shared access
* Deleting files
## Human review checklist
Before approving an important action, check:
* Which account or profile is involved
* Which external app will be changed
* Whether the output cites sources
* Whether the companion is acting on current data
* Whether the action can be undone
# Personal billing
Source: https://docs.strawberrybrowser.com/billing/personal-billing
View plan and usage, upgrade, downgrade, switch billing interval, cancel, reactivate, buy top-ups, and open receipts.
Personal billing and profile settings are managed together at `strawberry://settings/account`.
## Personal billing and teams
Your Personal account pays when you have no team memberships. If you belong to a team, your team pays first and eligible Personal credits remain available as a reserve. If you belong to multiple teams, choose **Paying account** at `strawberry://settings/account`.
While you belong to a team, manage seat plans and shared top-ups through the team. Personal purchase and plan-change controls are unavailable. Receipts for earlier personal payments remain accessible when applicable.
See [Credits and usage](/ai/credits-usage) for the payment order and [Teams](/billing/teams) for team billing.
## View current plan and usage
1. Open `strawberry://settings/account`.
2. Check your plan card, renewal or expiry date, and **Credit Usage**.
3. Continue down the page for full plan details and receipts.
## Upgrade, downgrade, or switch interval
1. Open `strawberry://settings/account`.
2. Use the plan button, such as **View plans**, **Upgrade plan**, or **Change plan**, to open the available plans.
3. Choose the plan and billing interval you want.
4. Review the price, timing, and any payment due before confirming.
Notes:
* Upgrades apply immediately with prorated billing.
* Some downgrades are scheduled for period end and shown as **Downgrade scheduled**.
* If cancellation is scheduled, use **Keep plan** to reactivate before period end.
## Cancel subscription
1. Open `strawberry://settings/account#billing`.
2. Scroll to **Receipts and payment methods**.
3. Click **Open billing portal**.
4. In the Stripe billing portal, cancel the subscription.
Your plan stays active until the end of the current billing period.
To undo a pending cancellation, open `strawberry://settings/account` and click **Keep plan** in the cancellation banner.
## Open billing portal
1. Open `strawberry://settings/account#billing`.
2. In **Receipts and payment methods**, click **Open billing portal**.
3. Use Stripe customer portal for subscription, payment method, and invoice management.
## View receipts
Open `strawberry://settings/account#billing`, then use **Open billing portal** in **Receipts and payment methods** to view past invoices in Stripe.
# Pricing plans
Source: https://docs.strawberrybrowser.com/billing/pricing-plans
Compare plan options, included credits, team seats, and extra credits before choosing a plan.
Strawberry plans include credits for AI work. Browsing websites without companion help does not consume credits.
## See current plans and prices
Open `strawberry://settings/account` and use the plan button to see the plans available to your account. You can also visit [Strawberry pricing](https://strawberrybrowser.com/pricing).
Before confirming a purchase, check the included credits, billing interval, price, and renewal date shown in the plan selection and checkout. A credit allowance is not a guarantee of a particular number of work hours; usage depends on the task and model.
## Choose a personal plan
Start with the free option if you want to explore. Consider a paid plan when you need more frequent or larger AI tasks. Review your recent usage at `strawberry://settings/account` to choose an allowance that fits your work.
For changing or cancelling an existing personal subscription, see [Personal billing](/billing/personal-billing).
## Use Strawberry with a team
Teams support shared billing, member roles, seat plans, and shared files. Admins and owners can manage seat plans and buy shared top-ups. Available seats and prices appear at `strawberry://settings/team`.
Some teams have enterprise contracts with their own billing and shared-credit arrangements. Check your team's agreement for included services and support.
When you belong to a team, a team pays for your work first. Eligible Personal credits can serve as a reserve. See [Credits and usage](/ai/credits-usage).
## Included credits and top-ups
Included plan credits follow the refill or expiry dates shown in your account. Purchased top-ups do not expire at month end. They can pay when included credits run out or are temporarily unavailable because of a rate limit.
Teams use prepaid credits, including shared top-ups, rather than automatic pay-as-you-go overage. See [Top-ups and rate limits](/billing/top-ups-rate-limits).
# Team shared files
Source: https://docs.strawberrybrowser.com/billing/team-shared-files
Use the shared team workspace that syncs files across members and gives companions team-visible context.
When you create or join a team, Strawberry sets up a shared team workspace that syncs files across team members.
Open `strawberry://library` and choose your team from the workspace selector to browse shared files.
## What team shared files are for
Use team shared files as a shared company brain:
* Research folders
* Handoff notes
* Team docs
* Reusable instructions
* Customer context
* Sales collateral
* Recruiting process docs
* Reports and artifacts companions should reuse
## Access model
* Team members can read and write files in the shared workspace.
* File changes sync automatically through the cloud.
* The team workspace is separate from personal profile workspaces.
* Personal profile files are not shared with the team automatically. You can choose to share specific files or folders.
## Use team files in a chat
Tell the companion which team's files to use and name the relevant folder or document. If you belong to several teams, specify the team so it does not have to guess.
For example:
```text theme={null}
Use the onboarding guide in our Acme team files to draft a first-week checklist.
Save the draft in the team's Onboarding folder.
```
## Best practices
* Put team-wide stable knowledge in team workspace.
* Put personal preferences and private files in your own workspace.
* Avoid storing secrets in shared files.
* Keep folder names clear enough for humans and companions.
* Ask companions to cite which team files they used in important outputs.
# Teams and organizations
Source: https://docs.strawberrybrowser.com/billing/teams
Create a team, invite members, manage roles and seat plans, and buy shared credits.
Team settings live at `strawberry://settings/team`.
The settings sidebar shows **Create Team** when you have no team, or your team name when you belong to one. Open `strawberry://settings/team` to create or manage a team.
## Create a team
1. Open `strawberry://settings/team`.
2. Enter a team name.
3. Add members if desired.
4. Choose each member role, such as `member` or `admin`.
5. Click **Create team**.
## Invite members
1. Open `strawberry://settings/team`.
2. Click **Invite Members**.
3. Enter email and role.
4. Send the invitation.
5. Review pending invites in the members table.
Invite emails include a join link. New users should sign up with the invited email address before accepting.
You can also copy invite links from pending invites at `strawberry://team/invite/`.
## Roles
* **Owner**: full control over billing, subscription, danger zone, and member operations.
* **Admin**: manage members and roles, rename the team, change seat plans, and buy or configure shared top-ups. The owner manages the team subscription portal and team deletion.
* **Member**: read-only team view and can leave the team.
Admins cannot change their own role. Use **Leave Team** when you want to leave.
## Seat plans
1. Open `strawberry://settings/team`.
2. As an admin or owner, open a member row or choose **Edit member**.
3. Choose the role or seat plan in the dialog.
4. Review and confirm the change.
Paid seat changes require a payment card on file. If the team needs a card, an owner must add it before an admin can upgrade seats. Seat upgrades bill immediately with proration. Seat downgrades are deferred to period end.
## Team billing
1. Open `strawberry://settings/team`.
2. Add a card if prompted.
3. As the owner, find **Team receipts and payment methods** and choose **Open billing portal**.
Enterprise teams are billed by contract invoice instead of self-serve card setup. If your team has an enterprise contract, the team billing section shows the contract and shared credit pool state instead of the no-card prompt.
Joining your first team makes a team your paying account. Joining another team does not necessarily change the team already paying for you. To choose between teams, open `strawberry://settings/account` -> **Paying account**, or [Billing & usage](https://strawberrybrowser.com/account/billing) on the web.
The choice applies to future work. Viewing a different team in team settings does not switch the paying account or transfer credits. Eligible Personal credits can cover work after the paying team's available credits, but the free Personal allowance is excluded.
You can still view earlier personal receipts when available at `strawberry://settings/account#billing`.
## Shared top-ups
Team admins and owners can buy shared prepaid credits and configure automatic refills from `strawberry://settings/team`. Members can view the balance and ask an admin or owner to add more.
There is no automatic pay-as-you-go team overage. Work can continue with available seat credits, shared team credits, or eligible Personal reserves. If no eligible credits are available, work pauses.
For automatic refills, the monthly spending limit controls how much Strawberry may buy automatically. See [Top-ups and rate limits](/billing/top-ups-rate-limits).
## Ownership and exit
* Contact support to arrange a billing ownership transfer.
* Non-owners can use **Leave Team**.
* Owners can use **Delete Team** in **Danger Zone**. Review the confirmation carefully; team deletion cannot be undone.
# Top-ups and rate limits
Source: https://docs.strawberrybrowser.com/billing/top-ups-rate-limits
Buy extra credits, set up automatic refills, and understand when plan credits become available again.
Top-ups are prepaid extra credits. Personal top-ups belong to your Personal account. Shared team top-ups belong to the team and can be used by its members.
## Buy top-up credits
1. Open `strawberry://settings/account`. Team admins and owners can also open `strawberry://settings/team`.
2. Check the account named beside the balance, then choose **Buy Top-Ups** or **Buy team top-ups**.
3. Choose a preset amount or enter a custom dollar amount.
4. Select **Next**, review the purchase, and confirm payment.
Credits are added after successful payment. An ordinary top-up purchase adds extra credits without restarting your plan's rate-limit window.
You can also buy from [Billing & usage](https://strawberrybrowser.com/account/billing) on the web. Team members need an admin or owner to buy shared credits. Personal purchase controls are unavailable while you belong to a team.
## Automatic refills
Automatic refills buy more credits when the selected account's credits run low. You choose the amount to buy each time and a monthly spending limit. Strawberry sets when to trigger the refill based on that amount; there is no separate threshold to choose.
1. Open `strawberry://settings/account`, or `strawberry://settings/team` for shared team credits.
2. Open **Buy Top-Ups** or **Buy team top-ups**.
3. Enable **Refill automatically when credits run low**.
4. Choose the refill amount and **Monthly spend limit**.
5. Follow the dialog to save or complete checkout. If you need to add a payment method, refills turn on after the purchase succeeds.
Team admins and owners manage shared refills. Personal automatic refills are not triggered while you belong to a team.
Automatic purchases pause when the monthly spending limit is reached. If payment is declined or no payment method is available, automatic refills turn off and billing settings show why. Refills add credits without resetting the plan's rate-limit window.
## When top-ups are used
Strawberry normally uses available included credits before purchased top-ups. Top-ups can also pay while monthly credits remain but a rate limit is holding them back. Purchased top-ups do not expire at month end.
When a team pays for you, its available credits come first. Eligible Personal plan and extra credits can then serve as a reserve. The free Personal allowance is excluded, and another team's balance is not used automatically.
## Plan credits and rate limits
Plan credits are your included allowance. A rate-limit window can temporarily hold back some of that allowance even while your monthly balance is positive.
Check the refill time and **Available now** at `strawberry://settings/account`. Eligible top-ups and other extra credits let you continue while they remain. They do not increase or restart the plan's window.
## Control usage
* Ask for a small sample before a large batch.
* Limit the number of rows, companies, pages, or candidates.
* Agree on a plan before work starts.
* Reuse memory and skills.
* Stop or steer a chat if it is solving the wrong task.
## Team credits
Teams use prepaid credits and shared top-ups. There is no automatic pay-as-you-go overage or overage cap to raise. If no eligible credits remain, wait for a refill or ask an admin or owner to add shared credits or review your seat plan.
# Strawberry compared with Chrome
Source: https://docs.strawberrybrowser.com/browser/chrome-comparison
Compare Strawberry with Chrome for normal browsing, AI assistance, agents, connected apps, memory, routines, privacy, and migration.
Strawberry keeps the browser fundamentals users expect from Chrome-style browsers, then adds AI-native workflows directly into the browser.
## What feels familiar
Both Strawberry and Chrome support everyday browser work:
* Tabs and windows
* Address bar search
* Bookmarks
* Downloads
* Saved passwords
* History
* Profiles
* Extensions from the Chrome Web Store, subject to compatibility
* Default browser settings
If you know how to use Chrome, the basic Strawberry browser surface should feel familiar.
## AI help in both browsers
Chrome offers Gemini assistance using page content and shared tabs. You do not always need to copy content into a separate chatbot. See [Google's Gemini in Chrome guide](https://support.google.com/gemini/answer/16283624?hl=en).
Chrome also offers **auto browse** for multi-step tasks. Availability depends on eligibility, including region, account, and subscription. See [Google's auto browse requirements](https://support.google.com/chrome/answer/16821166?hl=en). Work and school access can also depend on [administrator settings](https://support.google.com/chrome/a/answer/16291696?hl=en).
In Strawberry, you can build ongoing workflows around:
* Companions with their own instructions, memory, files, and skills.
* Built-in app connections available across profiles signed into the same Strawberry account.
* Scheduled and app-triggered routines.
* Meeting recording, transcription, and follow-up work.
* Shared team files that companions and teammates can use.
Compare the tools available to your own accounts on a real task. Chrome feature availability was checked against Google's help pages in September 2026.
## When to use Strawberry instead of Chrome
Use Strawberry when the work benefits from context, delegation, or repetition:
* Research across many sources
* Extracting structured data from websites
* Preparing for meetings from calendar, email, web, and CRM context
* Creating reports or spreadsheets from browsing work
* Running scheduled checks or inbox workflows
* Using memory and skills to make repeated tasks more consistent
## When Chrome may fit your needs
Chrome may fit your needs when its browser and available Gemini features cover your work, you depend on an extension that Strawberry does not support, or your organization requires Chrome.
## Migration path
You do not need to switch everything at once. Start with one Strawberry profile, import bookmarks and passwords, connect one or two apps, and run a few workflows. After you trust the setup, make Strawberry your default browser at `strawberry://settings/default-browser`.
## Benchmark context
The Strawberry marketing site includes a browser benchmark page comparing Strawberry with other AI browsers on real-world agent workflows. Treat benchmarks as directional, then validate Strawberry on your own tasks.
# Downloads
Source: https://docs.strawberrybrowser.com/browser/downloads
Change download location, control save prompts, and open the downloads history page in Strawberry.
Open download settings at `strawberry://settings/downloads`.
## Change download location
1. Open `strawberry://settings/downloads`.
2. Open **Download location**.
3. Click **Change** to choose a folder.
4. Click **Reset** to return to the default Downloads folder.
## Ask where to save each file
1. Open `strawberry://settings/downloads`.
2. Toggle **Ask where to save each file before downloading**.
When enabled, Strawberry shows a save dialog for each download from web tabs.
Agent-controlled downloads keep the streamlined behavior and may bypass save-location prompts.
## View download history
Click **View downloads** or open `strawberry://downloads`.
Use the downloads page to review and manage downloaded files.
## Tips
* If you delegate download-heavy work to a companion, choose a folder that is easy to find later.
* For generated reports or artifacts, use the file preview and share controls in chat when available.
* If a file appears missing, check both the configured download folder and the chat or session files where the companion worked.
# Extensions
Source: https://docs.strawberrybrowser.com/browser/extensions
Install, manage, search, remove, and review permissions for browser extensions in Strawberry.
Open extension settings at `strawberry://settings/extensions`.
Strawberry can install extensions from the Chrome Web Store. Extensions are new in Strawberry, so extensions outside the curated compatibility set may show a note during installation. Use the feedback form to report issues.
## Manage extensions
1. Open `strawberry://settings/extensions`.
2. Search installed extensions.
3. Click **Add more extensions** to open the extension store route.
4. Open per-extension **Permissions** to review or revoke optional permissions.
5. Delete an extension from the extension list when you no longer need it.
## Installing extensions
* Extensions can be installed from the Chrome Web Store.
* Extensions outside Strawberry's curated list show a note during installation because extensions are new in Strawberry. Use the feedback form to report issues.
* Extensions known to be incompatible may be blocked.
## Permission notes
Required permissions are informational and cannot be revoked. Optional permissions and optional origins can be revoked or cleared.
For AI tool permissions, use `strawberry://settings/integrations` or `strawberry://settings/ai-permissions`. Browser extension permissions and companion app-tool permissions are separate controls.
## Best practices
* Install only extensions you trust.
* Prefer the few extensions you actually use.
* Review optional origins before granting broad website access.
* Remove extensions that duplicate built-in Strawberry AI workflows.
# Import from other browsers
Source: https://docs.strawberrybrowser.com/browser/import-from-other-browsers
Move bookmarks, passwords, history, cookies, and tabs from Chrome, Safari, Firefox, Arc, and other browser profiles into Strawberry.
Use browser import when you want Strawberry to feel useful immediately with your existing bookmarks, saved credentials, browsing history, cookies, and open tabs.
## Open import
1. Open `strawberry://settings/profiles`.
2. Find **Import from another browser**.
3. Choose the source browser and source profile.
4. Pick the data types to import.
5. Start the import and review the result summary.
## Supported data types
Depending on source browser, operating system, and local profile availability, Strawberry can import:
* Passwords
* Bookmarks
* History
* Cookies
* Open tabs
## Supported sources
Available sources include:
* Chrome-family browser profiles
* Safari
* Firefox
* Zen
* Arc
Arc migration includes Arc-specific bookmark and Space handling. Zen migration keeps Essentials as pinned tabs and imports Pins into bookmark-bar folders by Space. Chrome-family imports can include current tabs when local browser data is available.
## Password import notes
Password import can require access to your operating system keychain or secure storage. If Strawberry cannot access the source password store, it may skip passwords and import other selected data types.
On Mac, Strawberry explains the permission request before importing from Chrome, Arc, Brave, Microsoft Edge, Comet, or Dia. Choose **Continue import** when ready, or close the dialog to cancel.
If macOS asks for access to your browser's **Safe Storage**, enter your Mac login password in the system prompt and choose **Allow**. This lets Strawberry read the protected data selected for import.
Import progress pauses while Strawberry waits for the system prompt. If the request remains open, you can keep waiting, cancel the import, or continue without passwords and encrypted cookies. If access is denied, unavailable, or times out, choose **Try again** or continue without that protected data. A completed partial import tells you which protected data was skipped.
Safari password import requires a password CSV exported from Safari or Passwords. Select that file in the import flow; choosing passwords alone does not provide access to Safari's saved passwords. A password CSV contains readable passwords, so delete the exported file after verifying the import.
Firefox passwords protected by a **Primary Password** cannot be imported through this flow. You can still import other supported data types.
## Cookie import notes
Cookie import can help keep you signed in, but it depends on source browser encryption and session compatibility. Some sites may still require sign-in after migration.
## Best practices
* Close the source browser before importing if the profile database is locked.
* Import bookmarks and passwords first if you want a low-risk migration.
* Import cookies and tabs when you want to continue a browsing session.
* Keep your old browser installed until you verify the Strawberry import result.
## Troubleshooting
If an import fails or imports fewer items than expected:
1. Confirm the source browser profile exists locally.
2. Close the source browser and retry.
3. Try importing one data type at a time.
4. Check whether the source browser requires OS-level permission for passwords or cookies.
5. Report an issue from the Strawberry app menu if the problem persists.
# Privacy and data controls
Source: https://docs.strawberrybrowser.com/browser/privacy-and-data
Manage ad blocking, browsing data, site permissions, AI permissions, link safety, account deletion, and local reset.
Open privacy settings at `strawberry://settings/privacy`.
## Ad blocker
Toggle **Block ads and trackers** at `strawberry://settings/privacy`.
## Clear browsing data
Use the correct cleanup action for the outcome you want:
* **Clear Cache** removes cached content and service workers used by websites for features such as offline access. It keeps cookies and local site databases, so it usually keeps you signed in, but a site may need to reload or rebuild offline content.
* **Clear Cookies and Site Data** removes cookies, local storage, IndexedDB, service workers, and site caches. This can sign you out of websites and remove site preferences.
* From site settings, **Clear site data** removes that site's cookies, local storage, IndexedDB, WebSQL, service workers, and cache storage.
* From site settings, **Clear cache** also removes that site's service workers. The site may need to reload or rebuild offline content.
For chat images, large chats, and app storage, use `strawberry://settings/storage`.
## Report issue logs
Use **Report Issue** from the application menu to send an issue report. App logs and diagnostics are attached automatically. The report can include details about the app, open pages, and files involved in a problem.
When available, **Include chat** and **Include a screenshot of this tab** are selected by default. Review these choices and any attachments before submitting. See [Support logs and issue reports](/troubleshooting/support-logs).
## Website pop-ups and device permissions
Privacy settings and site settings control site-level behavior such as pop-ups, new tabs, camera, microphone, and other device permissions.
## AI permissions
AI action permissions live at `strawberry://settings/ai-permissions` and per integration at `strawberry://settings/integrations`.
Use AI permissions to control whether companions must ask before actions, can always perform specific actions, or cannot use an action at all.
## Account deletion
Contact [support@strawberrybrowser.com](mailto:support@strawberrybrowser.com) to request account deletion. If your app offers **Delete account**, it is in **Danger zone** at `strawberry://settings/account`.
> [!WARNING]
>
> Account deletion is immediate and irreversible. Clearing browser data or resetting this computer
> is not the same as deleting your Strawberry account.
## Chat links
Strawberry has link safety controls for chat markdown links and chat navigation. Treat links from generated content like any other untrusted link, especially when they lead to sign-in, payment, or download pages.
## Chat history data
Chat history is stored with your Strawberry account so chats can be restored across signed-in clients. Chat titles and lightweight metadata are stored separately from encrypted session data. Messages, drafts, and detailed chat data are encrypted before they are saved on Strawberry servers.
Chat history search can find titles and conversation text indexed on this device. Older chats may take time to appear in search results.
# Profiles and appearance
Source: https://docs.strawberrybrowser.com/browser/profiles-and-appearance
Manage browser profiles, themes, colors, search engine, default browser, bookmarks, and saved passwords.
Profiles let you separate browsing contexts. A profile can have its own color, browsing data, workspace, and appearance settings. Built-in app connections are shared across profiles signed into the same Strawberry account.
## Browser profiles
Open `strawberry://settings/profiles`.
You can:
1. Rename the current profile.
2. Change the profile color.
3. Switch profiles.
4. Create a new profile.
5. Import from another browser.
Use separate profiles when you want clear boundaries between work, personal browsing, testing, or different companies.
During onboarding, select **Why do this?** for an optional explanation of what Strawberry imports.
Close it with **Got it**, then select **Continue** to start importing the selected browser profile.
Your original browser is unchanged.
## Your onboarding companion
A new setup starts with a random companion. It stays with you through sign-in and naming unless
you accept a different companion or edit its appearance. An interrupted setup restores its saved
companion. Shared access adds another companion without replacing your personal one.
When a received companion cannot load, use **Try again** or **Continue with me**. A temporary failure
does not discard the invitation. If the profile changed, use **Review again** before accepting it.
## Theme and UI
Open `strawberry://settings/theme`.
You can:
* Choose **Dark mode**, **Light mode**, or **System**.
* Set the profile color.
* Toggle **Show color as tab background**.
* Choose **Classic** for tabs across the top or **Modern** for tabs in a sidebar.
* Toggle **Auto Picture-in-Picture for YouTube** to control whether a playing YouTube video moves into a floating mini player when you switch tabs.
## Search engine
Open `strawberry://settings/search-engine`.
Select your preferred search engine and click **Set as default**.
## Default browser
Open `strawberry://settings/default-browser`.
Click **Make default** if you want links from other apps to open in Strawberry.
## Bookmarks and passwords
* Bookmarks: `strawberry://bookmarks`
* Passwords: `strawberry://settings/password`
Manage saved browser passwords on the **Passwords** page. Access to protected passwords may require your computer's authentication.
# Tabs and sidebar
Source: https://docs.strawberrybrowser.com/browser/tabs-and-sidebar
Use Strawberry tabs, chat sidebar, vertical tabs, activity sidebar, Universal Search, bookmarks, and Picture-in-Picture.
Strawberry supports normal browser tab workflows, plus AI-aware sidebars that help you move between pages, chats, and companion work.
## Tab layouts
Open `strawberry://settings/theme` to choose a tab layout:
* **Classic**: tabs across the top of the browser.
* **Modern**: tabs in a sidebar, with access to search for tabs and chats.
## Chat sidebar
Press `Cmd/Ctrl + E` to toggle the chat sidebar. Use it to start chats, revisit previous sessions, check running routines, and open companion work.
Routines can appear in the sidebar when they are scheduled, running, listening, or need your input.
## Universal Search
Press `Cmd + Shift + A` on macOS or `Ctrl + Shift + A` on Windows.
Universal Search helps you find:
* Open tabs
* Recent tabs
* Chats
* Sidebar history
Use chips to filter to tabs or chats. Click an active chip again to return to all results.
## Bookmarks
Open the Bookmark Manager at `strawberry://bookmarks`. Set bookmarks bar visibility in Appearance at
`strawberry://settings/theme`.
You can:
* Show the bookmarks bar always, only on the new tab page, or never.
* Search and manage bookmark folders.
* Right-click a tab to add or move it to a bookmark folder.
* Use the bookmark manager shortcut: `Cmd + Option + B` on macOS or `Ctrl + Shift + O` on Windows.
## Picture-in-Picture
When **Auto Picture-in-Picture for YouTube** is on, Strawberry moves a playing YouTube video into a floating mini player when you switch to another tab. Switching to a different window does not trigger it.
To turn it off, go to `strawberry://settings/theme` -> **Picture-in-Picture** and switch off **Auto Picture-in-Picture for YouTube**. The setting is on by default and syncs across your devices.
## Best practices
* Use **Modern** if you prefer browsing tabs in a sidebar.
* Use Universal Search instead of scanning long tab lists.
* Use profiles to separate website sign-ins and browsing data. Check connected app accounts separately, since built-in connections are shared across profiles.
# Welcome to Strawberry
Source: https://docs.strawberrybrowser.com/index
Start here to learn what Strawberry Browser is, how it works, and where to find the right docs.
Strawberry is a browser built for AI work. It keeps the browser you expect, including tabs, profiles, bookmarks, downloads, passwords, extensions, and history, then adds companions that can read pages, use connected apps, remember useful context, and run multi-step work with you.
Use these docs for two kinds of questions:
* **How do I use the app?** Find routes, settings, shortcuts, billing flows, permissions, and troubleshooting steps.
* **How do I get better results?** Learn how to prompt companions, create routines, use memory and skills, and give Strawberry enough context to do useful work.
## Where to start
* New to Strawberry: read [What Strawberry is](/introduction/what-is-strawberry), then [Quickstart](/introduction/quickstart).
* Moving from another browser: read [Import from other browsers](/browser/import-from-other-browsers) and [Strawberry compared with Chrome](/browser/chrome-comparison).
* Using AI features: read [Companions](/ai/companions), [Chat](/ai/chat), and [Agent runs](/ai/agent-runs).
* Managing usage: read [Credits and usage](/ai/credits-usage), [Pricing plans](/billing/pricing-plans), and [Personal billing](/billing/personal-billing).
* Building repeatable workflows: read [Routines](/knowledge/routines), [Skills](/knowledge/skills), and [Prompting best practices](/best-practices/prompting).
## Important Strawberry routes
You can paste Strawberry routes into the address bar:
* `strawberry://newtab` lets you pick a companion and start a new chat.
* `strawberry://settings` opens settings.
* `strawberry://settings/account` shows profile details, plans, billing, credit usage, invites, and account actions.
* `strawberry://settings/team` manages your team, billing, members, roles, and seat plans.
* `strawberry://library` opens files, projects, and companion files.
* `strawberry://use-cases` opens Official Skills and starter workflows.
* `strawberry://skills` opens your reusable skills.
* `strawberry://meetings` opens meeting summaries and transcripts.
* `strawberry://routines` opens routine management.
> [!TIP]
>
> If you are asking a companion about Strawberry itself, ask it to check `strawberry-docs` before
> answering. Strawberry provides built-in product help so companions can look up how to use the app.
> That help is maintained separately from this website, so wording and update timing can differ.
## Find a specific answer
Use search or the navigation to find a feature, setting, or troubleshooting guide. [Strawberry URLs](/reference/strawberry-urls) lists direct links you can open in the app.
# MCP and custom integrations
Source: https://docs.strawberrybrowser.com/integrations/mcp-custom-integrations
Add remote HTTP MCP servers, local command MCP servers, API-key integrations, and environment variables safely.
Custom MCP integrations let Strawberry connect to tools that are not built into the app.
Open `strawberry://settings/integrations`, then use **Add MCP**.
## MCP server types
### HTTP MCP servers
HTTP MCP servers run remotely or locally and communicate over HTTP, SSE, or Streamable HTTP.
You provide:
* Name
* Server URL
* Optional API key
* Optional OAuth sign-in when supported
Local HTTP servers, such as `http://127.0.0.1:8105/mcp`, support tool discovery and calls from your companion on the same device. Keep the server running while using its tools. If it requires an access token, enter it as the API key when adding the connection. Public remote servers require HTTPS.
### Command MCP servers
Command MCP servers run as local subprocesses that communicate over stdin and stdout.
You provide:
* Name
* Full command line
* Optional environment variables
Example command shape:
```bash theme={null}
npx -y @modelcontextprotocol/server-filesystem /path/to/folder
```
## Environment variables
Command MCPs can receive environment variables. Use them for API keys or configuration the server needs. Values are encrypted at rest.
## Security
Only add MCP servers you trust.
> [!WARNING]
>
> Command MCPs run as local processes with your system permissions. Strawberry does not verify
> third-party MCP servers for you.
## Best practices
* Prefer official vendor MCP servers when available.
* Read the server documentation before adding it.
* Scope local filesystem MCPs to the narrowest folder that solves the task.
* Avoid putting long-lived secrets into untrusted tools.
* Disable or remove custom MCPs when a project ends.
# Connected apps overview
Source: https://docs.strawberrybrowser.com/integrations/overview
Connect Google, Microsoft, Slack, Notion, CRM, ATS, MCP, and API-key tools so companions can work with real context.
Connected apps let Strawberry companions use your real work systems with your permission.
Open integrations at `strawberry://settings/integrations`.
## Connections across profiles
Built-in app connections, such as Gmail, Google Calendar, Drive, Outlook, Slack, Notion, and CRM apps, are shared across profiles signed into the same Strawberry account. Companions in those profiles can use the connected accounts according to permissions.
Changing browser profiles separates website sign-ins and browsing data. It does not isolate built-in app connections. Check which connected account a task will use when working across companies or clients.
Custom MCP connections configured locally belong to the profile where you add them. See [MCP and custom integrations](/integrations/mcp-custom-integrations).
## Disconnecting an account
Disconnecting a built-in app account removes that connection across your Strawberry profiles. Tasks and routines that rely on it may need you to reconnect it.
## Connect or disconnect an app
1. Open `strawberry://settings/integrations`.
2. Open the integration detail page.
3. Click **Connect** or **Add Account**.
4. Complete OAuth or enter the requested token.
5. Use **Disconnect** to remove an account connection.
API-key and token integrations use the same page, but prompt for provider credentials instead of opening OAuth.
## What companions can do
Each app exposes specific tools. For example, an email app might support reading messages and drafting replies, while a CRM might support reading records and writing updates.
The app detail page lists actions with configurable permissions. These controls do not cover every action or every read. Review the access requested when connecting the app as well.
## Best practices
* Connect only the apps needed for your workflows.
* Start with read-heavy workflows before enabling write-heavy actions.
* Review app permissions after adding a new routine.
* Disconnect apps you no longer use.
* Use companion-specific prompts to limit which apps a companion should prefer.
# Integration permissions
Source: https://docs.strawberrybrowser.com/integrations/permissions
Configure per-app tool permissions so companions ask, always allow, or cannot use specific connected app actions.
Integration permissions control what companions can do with connected apps.
Use them together with global AI permissions at `strawberry://settings/ai-permissions`.
## Configure tool permissions
1. Open `strawberry://settings/integrations`.
2. Open an integration's detail page.
3. Find **Permissions**, if the app offers configurable actions.
4. Set each listed action to one of:
* **Ask every time**
* **Always allow**
* **Disable action**
These settings cover the actions listed on the page. Some app reads and other actions do not have a separate permission control. To remove access to an account entirely, disconnect it from `strawberry://settings/integrations`.
## Choosing a permission level
Use **Ask every time** for actions that:
* Send messages
* Create, update, or delete records
* Spend money
* Change billing state
* Affect customers, candidates, or teammates
* Access sensitive data
Use **Always allow** for low-risk, frequent actions that are needed for normal work, after reviewing what the listed action can change or access.
Use **Disable action** when a companion should never use that capability.
## Permanent versus chat-specific permissions
Permanent permissions apply across sessions and are managed in integration settings.
Chat-specific permissions apply to that chat. They can still apply when you return to it; finishing a response or closing its tab does not clear them.
## Routine considerations
Routines can run while you are not actively watching. Review permissions carefully before giving a routine access to write actions.
For routines, it is often safer to let Strawberry read and draft, then notify you for approval before sending or mutating external systems.
## Audit checklist
Review permissions when:
* You connect a new app.
* You create a routine.
* You share a companion.
* A team member changes roles.
* Your workflow begins touching customer, payment, hiring, or production systems.
# Account basics
Source: https://docs.strawberrybrowser.com/introduction/accounts
Manage your email, sign out, redeem invite codes, and find help with account deletion or local data.
Account settings live at `strawberry://settings/account`.
Use this page for your account details, plan status, current usage, invitations, and sign-out.
## Update your email
1. Open `strawberry://settings/account`.
2. Open the menu beside your account details and choose **Edit email**.
3. Enter the new email address.
4. Request a verification code.
5. Enter the 6-digit code.
6. Confirm the update.
After a successful email update, Strawberry signs you out on every device. Sign in again with the updated email. If you use Google sign-in, you continue using the same linked Google account.
## Sign out
1. Open `strawberry://settings/account`.
2. Open the menu beside your account details.
3. Choose **Sign out**.
## Delete your account
To permanently delete your account and all associated data, contact us at
[support@strawberrybrowser.com](mailto:support@strawberrybrowser.com).
## Reset this computer
Local reset removes Strawberry data from this computer without deleting your account. It can remove browsing data and files that have not synced.
If **Reset Strawberry data on this computer** is available in **Danger zone** at `strawberry://settings/account`, review its confirmation before continuing. If it is not available, contact [support](mailto:support@strawberrybrowser.com) for help with a clean local setup.
## Redeem an invite code
1. Open `strawberry://settings/account`.
2. Find the invite or referral section.
3. Enter the code.
4. Confirm redemption.
Invite and referral bonuses may grant credits depending on the current program.
## Share your invite link
Open `strawberry://settings/account` and use the invite section to copy your invite link when available.
# Glossary
Source: https://docs.strawberrybrowser.com/introduction/glossary
Definitions for common Strawberry terms such as companions, routines, credits, memory, skills, plans, profiles, and work traces.
## Companion
A personal AI teammate in Strawberry. A companion can chat with you, use tools, remember context, hold files, run routines, and have companion-specific skills.
## Chat
A conversation with a companion. Chats can include attached files, selected tabs, queued follow-ups, work traces, generated files, and sub-agent activity.
## Agent run
A companion task that uses tools or takes multi-step actions, such as reading pages, searching, writing files, using connected apps, or spawning sub-agents.
## Sub-agent
A focused helper agent spawned by a main companion to work on a scoped task. Sub-agents can have their own `PLAN.md` and work trace.
## Routine
An automation that runs on a schedule or app event. Routines are managed per companion and on the full `strawberry://routines` page.
## Skill
Reusable instructions for a kind of work. Skills can be global to your profile or specific to one companion.
## Memory
Stable information Strawberry saves so companions can use it later. Memory can include preferences, company context, workflow notes, and other durable facts.
## Library
The `strawberry://library` page for artifacts, projects, companion files, and other files. Use Cases, Skills, Meetings, and Routines have separate pages.
## Credits
The usage unit for AI work in Strawberry. Browsing without companion help does not consume credits. Companion replies, agent runs, web research, app actions, and transcription-related AI work can consume credits.
## Paying account
The Personal or team account that pays first for new AI work. If you belong to a team, a team is your paying account. If you belong to multiple teams, choose one under **Paying account** in `strawberry://settings/account`.
Eligible Personal plan and extra credits can cover work after the team's available credits. The free Personal allowance is excluded. Balances keep their ownership; switching teams does not transfer credits.
## Top-up credits
Prepaid extra credits. Top-ups can be used when included credits are exhausted or temporarily unavailable because of a rate limit. They do not expire at month end.
## Profile
A browser profile with its own browsing data and many profile-specific settings, such as appearance. Files belong to the Strawberry account used by the profile. Built-in app connections are shared across profiles signed into the same Strawberry account.
## Team workspace
A shared synced folder created for team members. Open Library and select your team to browse it. Companions can use these files as shared context.
## Work trace
The visible record of what a companion or sub-agent did during a task, including searches, file operations, app tool calls, browser actions, questions, and progress.
# Keyboard shortcuts
Source: https://docs.strawberrybrowser.com/introduction/keyboard-shortcuts
Common Strawberry shortcuts for tabs, windows, chat, search, bookmarks, downloads, and settings.
Most browser shortcuts match familiar Chrome-style shortcuts. Use `Cmd` on macOS and `Ctrl` on Windows unless a shortcut says otherwise.
## Core shortcuts
* Settings: `Cmd/Ctrl + ,`
* New tab: `Cmd/Ctrl + T`
* New window: `Cmd/Ctrl + N`
* New incognito window: `Shift + Cmd/Ctrl + N`
* Reopen closed tab: `Cmd/Ctrl + Shift + T`
* Open address bar: `Cmd/Ctrl + L`
* Close tab: `Cmd/Ctrl + W`
* Close window: `Cmd/Ctrl + Shift + W`
* Find: `Cmd/Ctrl + F`
* Copy tab address: `Cmd/Ctrl + Shift + C`
* Add or remove bookmark: `Cmd/Ctrl + D`
* Print: `Cmd/Ctrl + Shift + P`
## Sidebar and tabs
* Toggle chat sidebar: `Cmd/Ctrl + E`
* Switch between Classic and Modern tab layouts: `Cmd/Ctrl + Shift + S`
* Toggle tab sidebar in Modern layout: `Cmd/Ctrl + S`
* Switch to the previous recent tab: `Ctrl + Tab`. In Modern layout, the recent-tab switcher also lists sidebar destinations you opened in this session, such as Chat History and Routines.
* Cycle backward in the recent-tab switcher: `Ctrl + Shift + Tab`
* Universal Search for tabs and chats: `Cmd + Shift + A` on macOS or `Ctrl + Shift + A` on Windows
## Bookmarks and downloads
* Bookmark manager: `Cmd + Option + B` on macOS or `Ctrl + Shift + O` on Windows
* Downloads: `Cmd + Shift + J` on macOS or `Ctrl + J` on Windows
## Companion switching
In chat input, `Cmd + .` on macOS or `Ctrl + .` on Windows cycles through companions. Use `Shift` with the shortcut to cycle backward.
## Tip
If a shortcut is not working, check whether focus is inside a web page, the browser toolbar, chat input, or an external window. Some shortcuts depend on the active surface.
# Quickstart
Source: https://docs.strawberrybrowser.com/introduction/quickstart
Set up Strawberry, open the main pages, start a chat, connect apps, and run your first useful workflow.
Use this quickstart to get from a fresh install to your first useful Strawberry workflow.
## 1. Install and sign in
Download Strawberry from `strawberrybrowser.com/download`, install it, and sign in. Strawberry is available for macOS and Windows.
After sign-in, open `strawberry://settings/account` to check your account email, current plan, credit usage, invite code options, and account actions.
## 2. Import browser data
Open `strawberry://settings/profiles`, then use **Import from another browser**. Strawberry supports importing from common browser profiles, including Chrome-family browsers, Safari, Firefox, and Arc depending on platform and local data availability.
Import what you need first:
* Bookmarks help you keep your browsing setup.
* History helps address bar suggestions and recall.
* Passwords reduce sign-in friction.
* Cookies and tabs can help you continue an existing browsing session when supported.
## 3. Start from the new tab page
Open `strawberry://newtab`.
You can:
* Pick a companion.
* Start a chat immediately.
* Paste or drop files into the chat input.
* Follow the Getting Started checklist when it is available.
For workflow ideas, open `strawberry://use-cases`. Read a workflow before choosing **Use**, which starts work immediately. If you want to add constraints first, name the skill in a new chat and include them in your first message.
## 4. Connect one or two apps
Open `strawberry://settings/integrations`.
Start with the apps that give Strawberry useful context:
* Gmail or Outlook for email workflows
* Google Calendar for meeting prep and scheduled meeting recording
* Google Drive, Docs, Sheets, or Notion for files and knowledge
* Slack for team updates
* HubSpot, Attio, Salesforce, Ashby, or other systems for domain-specific workflows
## 5. Try a focused prompt
Give Strawberry a concrete goal, the context it should use, and the output you want.
```text theme={null}
Help me prepare for my next sales call.
Use my calendar to find the meeting, check any recent emails with the company,
research their website and LinkedIn, and give me a concise briefing with
risks, likely pain points, and three questions to ask.
```
## 6. Review permissions and output
When a companion needs to use a connected app or take an action, Strawberry may ask for approval. Read the request, confirm what will happen, and approve only if it matches your intent.
Open the chat's content or work trace panels to review credits, sources, files, sub-agents, and progress.
## 7. Make it repeatable
If you repeat a task often, turn it into a routine or skill:
* Use a **routine** when the task should run on a schedule or app event.
* Use a **skill** when you want reusable instructions for a kind of task.
* Use **memory** when Strawberry should remember stable facts about you, your company, your preferences, or your workflow.
# Settings navigation
Source: https://docs.strawberrybrowser.com/introduction/settings-navigation
Open Strawberry settings and jump directly to account, billing, team, integrations, privacy, downloads, and other pages.
Open settings in any of these ways:
1. Press `Cmd + ,` on macOS or `Ctrl + ,` on Windows.
2. Click the profile or settings button in the top-right browser toolbar, then click **Settings**.
3. Type `strawberry://settings` in the address bar.
When opened without a subpath, Strawberry redirects to `strawberry://settings/account`.
## Account and billing
* Account overview: `strawberry://settings/account`
* Billing, plans, and receipts: `strawberry://settings/account#billing`
* Team management: `strawberry://settings/team`
* Paying account: `strawberry://settings/account` -> **Paying account**, available when you can choose between teams
## AI and connected apps
* Connected apps and integrations: `strawberry://settings/integrations`
* AI permission controls: `strawberry://settings/ai-permissions`
* Meeting transcription setup and tuning: `strawberry://settings/transcription`
* Extensions: `strawberry://settings/extensions`
## Browser preferences
* Profiles: `strawberry://settings/profiles`
* Theme, UI, and bookmarks bar visibility: `strawberry://settings/theme`
* Search engine: `strawberry://settings/search-engine`
* Default browser: `strawberry://settings/default-browser`
* Passwords: `strawberry://settings/password`
* Downloads: `strawberry://settings/downloads`
## Data
* Privacy controls: `strawberry://settings/privacy`
* Storage and cleanup: `strawberry://settings/storage`
* Memory: `strawberry://settings/memory`
## App updates
Use the application menu for update checks and issue reporting. Some support options may vary by release.
## Quick links outside settings
* New tab: `strawberry://newtab`
* Downloads page: `strawberry://downloads`
* Library: `strawberry://library`
* Bookmarks: `strawberry://bookmarks`
* Use Cases: `strawberry://use-cases`
* Skills: `strawberry://skills`
* Meetings: `strawberry://meetings`
* Routines: `strawberry://routines`
# What Strawberry is
Source: https://docs.strawberrybrowser.com/introduction/what-is-strawberry
Understand Strawberry Browser, companions, agent work, routines, memory, skills, and how they fit together.
Strawberry is a full browser with AI companions built into the browsing workflow. You can use it like a normal browser, but when you need help, a companion can read what is on screen, answer questions, operate web pages, use connected apps, create files, and continue multi-step work in the background.
The central idea is simple: your browser already contains the work context. Strawberry lets an AI use that context directly, instead of making you copy page text, screenshots, files, and instructions into a separate chatbot.
## Core concepts
### Browser
Strawberry includes browser basics such as tabs, windows, bookmarks, downloads, profiles, saved passwords, history, extensions, search engine settings, default browser settings, and import from other browsers.
### Companions
Companions are the AI teammates you chat with. Each companion can have its own instructions, memory, files, routines, skills, and visual identity. Built-in app connections are available across profiles signed into the same Strawberry account, subject to permissions. You can create different companions for different kinds of work, such as sales, recruiting, research, operations, or personal productivity.
### Chat
Chat is where you ask questions, delegate work, attach files, reference tabs, and review outputs. Strawberry supports queued follow-ups, so you can keep giving instructions while a companion is already responding.
### Agent runs
An agent run is a more active task. The companion can navigate pages, search, read files, write files, use tools, ask for feedback, and spawn sub-agents for scoped work. Strawberry shows work traces so you can see what happened.
### Routines
Routines are scheduled or trigger-based automations. A routine can run every day, every few hours, on a cron expression, or when an app event fires, such as a new email.
### Library
Library holds your files, projects, and companion files. Skills, Meetings, Use Cases, and Routines have their own pages.
## What Strawberry is good at
Strawberry is strongest when the task involves browser context, connected app context, or repeated work:
* Researching companies, people, markets, products, and competitors
* Extracting data from websites into spreadsheets or reports
* Drafting and personalizing messages from real context
* Preparing for meetings from calendar, email, web, and CRM data
* Summarizing Slack, email, documents, and transcripts
* Building routines that monitor tools and alert you only when something matters
## What still needs your judgment
Strawberry can act, but you stay in control. Permission settings determine which supported actions ask for approval. Saved permissions can allow actions without a new prompt. You should review important outputs, especially when a task involves money, legal commitments, hiring decisions, external messages, deletions, or customer-facing updates.
> [!WARNING]
>
> Treat companions as capable assistants, not final authorities. Review destructive actions,
> external messages, billing changes, and business-critical outputs before confirming them.
# Memory
Source: https://docs.strawberrybrowser.com/knowledge/memory
Understand Strawberry memory, shared memory, companion memory, editable memory files, and best practices for durable context.
Memory is durable context Strawberry can use later. It helps companions avoid asking the same questions repeatedly and makes future work more personal and specific.
## What memory can contain
Useful memory is stable and reusable:
* Your role, company, industry, and goals
* Product and customer context
* Writing style and tone preferences
* ICP and target account details
* Tooling and workflow preferences
* Recurring constraints, such as regions, formats, or approval rules
Avoid using memory for temporary tasks, one-off instructions, secrets, or information that will quickly become stale.
## Find and review memory
Open `strawberry://settings/memory` to review the memory controls available to you. The available controls can differ between accounts and app versions.
You can also ask a companion what it remembers and ask it to correct outdated facts. If your setup uses editable memory files, find them through **Companion files** or **All files** in `strawberry://library`.
Keep saved context concise. Ask your companion to use the Memory Best Practices skill when memory has become repetitive or outdated.
## Shared and companion memory
Strawberry supports information shared with every companion and companion-specific memory. Companion-specific memory is useful when a recruiting companion should remember different context than a sales companion.
## Editing memory
Ask your companion to save or update useful facts. If your setup exposes editable memory files, you can also edit those files in Library. Good updates are short, factual, and easy for a companion to apply.
```text theme={null}
When writing outbound sales messages, keep the tone concise, direct,
and lightly personal. Avoid hype. Lead with the prospect's likely problem.
```
## Memory and privacy
Only store information you are comfortable making available to the relevant companion scope. When sharing a companion, remember that the recipient can access that companion's synced folder, including memories.
## Best practices
* Store stable context, not every chat detail.
* Use headings so memory files are easy to scan.
* Remove outdated preferences.
* Keep sensitive details out of memory unless they are necessary and scoped correctly.
* Ask a companion to summarize new durable facts before saving them.
# Official Skills
Source: https://docs.strawberrybrowser.com/knowledge/official-skills
Find role-aware starting points for useful Strawberry workflows.
Official Skills are curated, role-aware instructions for useful Strawberry workflows.
Open **Use Cases** at `strawberry://use-cases` to browse Official Skills and starter workflows.
Public tutorials live in Strawberry's [Use Cases hub](https://strawberrybrowser.com/use-cases):
* [Getting Started skills](https://strawberrybrowser.com/playbooks) show how someone can grow from a useful first result into repeatable, connected, team-wide work.
* [Official Skills](https://strawberrybrowser.com/prompts) focus on one concrete outcome.
* [Blog](https://strawberrybrowser.com/blog) contains editorial analysis, product news, and ideas.
The public article and its Official Skill follow the same recognizable recipe or journey. The
article adds readable explanation, examples, and videos; the public GitHub link contains the
complete technical skill. If no handwritten article exists, the same page shows the canonical
skill instead of generating substitute copy.
Every Getting Started skill has a handwritten public guide. These guides preserve the useful
prose and practical examples from Strawberry's earlier human-written best-practice material while
linking to the focused Official Skills that contain the executable detail. They are reviewed
together so the public explanation and the in-product journey do not drift apart.
## How recommendations work
During onboarding, you can optionally describe your role in your own words, add lightweight workplace context on a separate page, and choose the work categories most relevant to you. Strawberry uses those choices to prioritize useful official skills. The same workflow can use role-appropriate wording, for example sourcing customers for a founder or sourcing leads for a sales role. Agency, consulting, and independent work are organization types rather than job roles, so they can tailor recommendations without replacing the work you actually do.
Recommendations can include:
* **Official Skills** for one concrete, valuable result.
* **Getting Started skills** that describe a readable journey through an area such as sales, recruiting, research, or venture capital.
Getting Started as a Founder in Strawberry helps someone choose among early customer acquisition,
fundraising, hiring, research, and operational work without trying to set everything up at once.
## Examples
Official Skills include workflows such as:
* Find new customers, leads, or candidates.
* Research companies and create beautiful slide decks.
* Prepare for calls and interviews.
* Turn meetings into notes and follow-ups.
* Organize an inbox and keep it at zero.
* Investigate app errors.
* Build an investment memo or map a startup ecosystem.
* Take repetitive admin, support, or bookkeeping work off your plate.
## How to use an Official Skill
1. Open `strawberry://use-cases`.
2. Search or choose a category to find a relevant workflow.
3. Read the workflow description.
4. Click **Use** to start a chat and begin the workflow.
**Use** starts work immediately. If you want to set constraints before work begins, start your own chat at `strawberry://newtab`, name the skill, and include those constraints in your first message.
The companion uses the skill as guidance and can ask for missing context as it works.
## Tips
* Treat official skills as starting points, not fixed scripts.
* Add the exact source, account, file, or system you want Strawberry to use.
* Tell the companion what output you want.
* Ask it to confirm before sending messages, mutating systems, or spending credits beyond a sample.
# Library
Source: https://docs.strawberrybrowser.com/knowledge/overview
Find your files, projects, companion files, and shared team work in Library.
Library brings together the files you and your companions work with, including generated reports, projects, and shared team files.
## Open Library
Click **Library** in the chat-history sidebar, or enter `strawberry://library` in the address bar. You need to be signed in.
Library opens to **Artifacts** in **My Workspace**. Use the workspace selector to switch between your files, team files, and files shared with you.
## Find what you need
* **Artifacts**: browse outputs from companion work.
* **Projects**: find project folders.
* **Companion files**: browse files belonging to your companions.
* **All files**: browse the folders and files in the selected workspace.
Use search to narrow the current view. When you select files shared with you, **Invitations** lets you review pending shares.
## Other places to find your work
Some features have their own pages:
* **Use Cases** at `strawberry://use-cases` helps you find Official Skills and starter workflows.
* **Skills** at `strawberry://skills` holds reusable instructions.
* **Meetings** at `strawberry://meetings` holds meeting summaries, transcripts, and recordings.
* **Routines** at `strawberry://routines` manages scheduled and app-triggered work.
* **Memory** at `strawberry://settings/memory` holds your memory settings.
For sharing and downloads, see [Reports and files](/knowledge/reports-and-files).
# Reports and files
Source: https://docs.strawberrybrowser.com/knowledge/reports-and-files
Find generated reports, shared files, companion files, workspace files, transcript files, and public file links.
Strawberry companions can create files and reports as part of their work. Files can live in a chat session, a companion folder, your workspace, or a team workspace.
## Reports
Open `strawberry://library` and choose **Artifacts**.
Reports are generated by companion tasks. Open a report to see the full output and continue the conversation that produced it.
## Files in companion settings
Open a companion's settings and go to **Files** to browse that companion's folder. Choose **Open in Library** to continue there.
To browse your other files or team files, open `strawberry://library` and choose the workspace you want.
You can drop local files into an open folder to copy them there. If a file with the same name already exists, Strawberry saves the dropped file with a unique numbered name.
## Workspace files
Your files belong to your Strawberry account. They can include memory, skills, meetings, reports, and other reference material. Profiles signed into the same account can access its files, even when folders retain another profile's name.
Team workspace files are shared with team members. See [Team shared files](/billing/team-shared-files).
## Public file links
You can share a synced file, folder, report, or generated HTML artifact:
1. Open the file or folder.
2. Choose **Share** or **Copy public link**.
3. Strawberry creates a public link and copies a `strawberrybrowser.com/files/...` URL.
Anyone with a public link can view the current synced file or folder. Later edits and files added to a shared folder can become visible through the same link; updates may take a short time to appear.
Revoke the link from the share dialog to stop future access through it. This does not remove copies someone has already downloaded. For a fixed version, make a separate copy and share that copy without changing it.
## Share access with people
In the share dialog, use **Invite people by email** to share access with specific people. If you are on a team, typing in the field suggests team members by name and email. Select a suggestion to fill the email, then click **Invite**. Strawberry accepts direct email shares between team members automatically, so the shared file appears for your teammate right away. Other recipients can accept or decline the invitation unless they previously chose to always accept your shares.
Use the permission menu next to each person to choose viewer or editor access, or remove access when they no longer need the file.
## Send or download reports
The report share dialog also includes action chips for connected sharing apps and downloads. Reports can be downloaded as Markdown or PDF. If Slack or Gmail is connected, use the Slack or Gmail chip to open a send dialog with the report attached.
## Best practices
* Put reusable reference files in your workspace or team workspace.
* Put companion-specific instructions and skills in that companion's folder.
* Publish public links only for files you are comfortable sharing with anyone who has the URL.
* Review future edits and new folder contents as carefully as the files you first share.
# Routines
Source: https://docs.strawberrybrowser.com/knowledge/routines
Create, manage, run, pause, and review Strawberry routines for scheduled and event-triggered work.
Routines are automations managed per companion and from the full Routines page at `strawberry://routines`.
The routines page has a flat list across companions, companion filters, search, detail screens, editing, and run history.
You can create routines conversationally. If a workflow should repeat, tell the companion:
```text theme={null}
Do this workflow every Tuesday morning.
```
The companion can help turn the workflow into a scheduled routine and ask for any missing trigger, account, approval, or notification details.
## Routine routes
* `/routines`: list view with a run history sparkline card
* `/routines/history`: aggregate run history across companions
* `/routines/:id`: routine detail and run history
* `/routines/:id/edit`: routine editor
* `/routines/new`: opens the routines list with the create-routine dialog
## Create a routine
1. Open `strawberry://routines`.
2. Click **New routine** to open the create-routine dialog.
3. Choose a trigger type:
* **Daily**
* **Interval**
* **Cron expression**
* App trigger, such as new email
4. If the trigger needs a connected account, select one.
5. Give the routine a name.
6. Write the instruction prompt.
7. Click **Create routine**. A routine needs at minimum a name and instructions. If anything required is missing, **Create routine** stays clickable and the dialog highlights the fields that need attention instead of being disabled.
## Create a routine from a chat
When a chat produces a workflow you want to repeat, ask Strawberry to schedule it:
```text theme={null}
Do this workflow every Tuesday morning.
Ask me any targeted questions you need to make the routine reliable.
```
Good routine-creation chats usually clarify:
* The schedule or event trigger
* Which companion should run the work
* Which connected account, folder, label, project, or source to use
* What counts as important enough to notify you
* What the routine may do automatically
* What must wait for your approval
## Get help creating a routine
Open `strawberry://routines` and choose **Create with companion** to work through an idea in chat. Describe the outcome you want, the schedule or event, and when you want to be notified.
You can also ask in any existing chat to turn a successful workflow into a routine.
## Manage routines
You can:
* Filter by companion.
* Search routines.
* Open a detail page.
* Edit a routine.
* Delete a routine.
* Pause and resume.
* Run now for scheduled routines.
* Replay last run for webhook routines when available.
* Review run history.
## How running routines appear
When a routine fires, Strawberry creates a real chat session. If the task finds nothing significant, it can delete the automatic chat. If it finds something, it can notify you and keep the session visible.
Cron routines show scheduled-work notices. Webhook routines show webhook notices with integration logos when available.
## Best practices
* Combine related actions into one routine prompt when they share the same trigger.
* Keep prompts explicit about what counts as important enough to notify you.
* Ask routines to delete quiet chats when nothing meaningful happened.
* Review run history to tune noisy routines.
# Skills
Source: https://docs.strawberrybrowser.com/knowledge/skills
Create, edit, organize, and use Strawberry skills as reusable instructions for repeated workflows.
Skills are reusable instructions. They help companions apply the same playbook each time a similar task comes up.
Use a skill when you find yourself writing the same prompt, checklist, rubric, or process repeatedly.
The easiest way to create a skill is from a chat that already went well. Tell the companion:
```text theme={null}
Create a skill for me from this workflow.
```
The companion can summarize the steps, inputs, approval gates, and output format into reusable instructions for future tasks.
## Global skills
Global skills are installed for your profile. Open them at `strawberry://skills`.
From a skill card, you can read or edit the skill instructions in the document viewer or start a chat that uses it.
## Companion-specific skills
When you add a skill from companion settings, Strawberry creates it in that companion's own skills folder.
Companion-specific skills:
* Belong to that companion.
* Appear before global skills in the slash menu.
* Follow the companion when shared with another user or team.
## What to put in a skill
A useful skill includes:
* When to use it
* What inputs to ask for
* What sources to inspect
* What steps to follow
* What output format to produce
* What requires user approval
* How to verify the work
## Turn good chats into skills
When a companion does something correctly, do not make yourself remember every detail. Ask it to capture the process.
Useful follow-ups:
```text theme={null}
Create a skill for me from what we just did.
Make sure it includes the questions you asked, the sources you checked,
the approval rules, and the final output format.
```
```text theme={null}
Update the skill so next time you ask for a sample size before running
the full workflow.
```
Review the draft before saving it. A good skill should still ask targeted questions when the task depends on missing context.
## Example skill skeleton
```text theme={null}
# Skill: Competitor teardown
Use when the user asks to analyze a competitor's website, pricing,
positioning, product, or go-to-market motion.
Process:
1. Ask which competitor and what decision the user is trying to make.
2. Inspect official website pages first.
3. Capture pricing, target customer, core claims, integrations, and proof.
4. Compare findings to what you know about the user's company.
5. Return a concise battlecard with source links and confidence notes.
Ask before sending messages, signing up for products, or using paid tools.
```
## Best practices
* Keep skills focused.
* Avoid stuffing unrelated workflows into one skill.
* Include examples of good output.
* Update skills after a companion makes a useful improvement.
* Ask a companion to create or update the skill while the successful workflow is still fresh.
* Use memory for facts and skills for process.
# Transcription and meeting recording
Source: https://docs.strawberrybrowser.com/knowledge/transcription
Record meetings, transcribe voice, configure microphones, add languages and preferred terms, and browse saved transcripts.
Strawberry can transcribe your voice in chat and record meetings. Configure it at `strawberry://settings/transcription`.
## Why record meetings
Meeting transcripts help companions:
* Draft follow-up emails
* Book meetings
* Update CRMs
* Create summaries
* Recall past decisions
* Use meeting context in future work
## Dictation or a saved meeting
Use the microphone in chat to dictate text. A chat recording can also become a saved meeting when Strawberry detects a conversation. Length alone does not determine whether a recording becomes a meeting.
When you want a recording saved as a meeting, open `strawberry://meetings` and choose **Start meeting**.
## Online meetings
Strawberry can record online meetings on Google Meet, Zoom, and Microsoft Teams.
Recording can start from:
* Auto-detected meeting URL toasts
* Scheduled meeting notifications from Google Calendar
* **Start meeting** on `strawberry://meetings`
## In-person meetings
Open `strawberry://meetings` and choose **Start meeting**. Strawberry captures microphone audio and transcribes the conversation.
## During a recording
A floating pill widget shows audio level bars and controls. Hover to reveal pause and stop. Drag the widget to reposition it.
## First-time setup
macOS:
1. Enable microphone access.
2. Enable screen and system audio access for remote participants.
3. Restart Strawberry after permission changes.
Windows:
1. Enable microphone access.
2. Strawberry does not require a separate system-audio permission prompt. If audio is missing, check your Windows audio and privacy settings.
## Settings
At `strawberry://settings/transcription`, configure:
* Microphone
* Spoken languages
* Preferred terms
* Scheduled meeting notifications
* Auto-detected meeting notifications
* Advanced noise thresholds
* Level tests
## Where transcripts appear
Open `strawberry://meetings` to browse meeting summaries and transcripts. The **Recordings** filter shows saved recordings that did not become meetings or still need transcription.
Meeting files are also available in your workspace through `strawberry://library`.
## Troubleshooting
See [Transcription troubleshooting](/troubleshooting/transcription) for audio, permissions, accuracy, and meeting toast issues.
# llms.txt and AI readers
Source: https://docs.strawberrybrowser.com/reference/llms-and-ai-readers
Find Strawberry help pages with an AI assistant.
The [Strawberry docs index](https://docs.strawberrybrowser.com/llms.txt) lists the help pages on this site with a short description of each. Give the link to an AI assistant when you want it to find the right guide before answering.
## Ask for a specific answer
For example:
```text theme={null}
Use https://docs.strawberrybrowser.com/llms.txt to find the current guide
for team billing. Explain where I can see usage and buy more credits.
Link the pages you used.
```
## Help inside Strawberry
When asking a Strawberry companion about the app, ask it to check `strawberry-docs`. Companions have built-in help that is maintained separately from this website. If two answers differ, check the current app controls and contact support when needed.
# Strawberry URLs
Source: https://docs.strawberrybrowser.com/reference/strawberry-urls
Reference for common strawberry:// routes for settings, account, billing, teams, Library, routines, downloads, and browser pages.
Paste these routes into the Strawberry address bar.
## Core routes
| Route | Purpose |
| - | - |
| `strawberry://newtab` | New tab page with chat input and companion selection |
| `strawberry://settings` | Settings, redirects to account by default |
| `strawberry://downloads` | Downloads history |
| `strawberry://library` | Files, projects, and companion files |
| `strawberry://bookmarks` | Bookmark Manager |
| `strawberry://routines` | Routines list |
## Settings
| Route | Purpose |
| - | - |
| `strawberry://settings/account` | Profile, billing, plans, credits, invites, and account actions |
| `strawberry://settings/account#billing` | Billing, plans, receipts, and subscription controls |
| `strawberry://settings/team` | Team details, billing, members, roles, and seats |
| `strawberry://settings/team#members` | Team members and pending invitations |
| `strawberry://settings/integrations` | Connected apps and tool permissions |
| `strawberry://settings/ai-permissions` | Global AI permission mode and permission summary |
| `strawberry://settings/transcription` | Meeting recording and transcription setup |
| `strawberry://settings/extensions` | Browser extensions |
| `strawberry://settings/profiles` | Profiles and import |
| `strawberry://settings/theme` | Theme, profile color, tab layout, and bookmarks bar visibility |
| `strawberry://settings/search-engine` | Search engine selection |
| `strawberry://settings/default-browser` | Default browser setting |
| `strawberry://settings/password` | Saved passwords |
| `strawberry://settings/downloads` | Download location and save behavior |
| `strawberry://settings/privacy` | Privacy and browsing data controls |
| `strawberry://settings/storage` | Storage usage and cleanup |
## Files and workflows
| Route | Purpose |
| - | - |
| `strawberry://library` | Artifacts, projects, companion files, and all files |
| `strawberry://use-cases` | Official Skills and starter workflows |
| `strawberry://skills` | Reusable skills |
| `strawberry://meetings` | Meeting summaries and transcripts |
| `strawberry://meetings?filter=recordings` | Saved recordings and transcription retries |
| `strawberry://settings/memory` | Memory settings |
## Routines
| Route | Purpose |
| - | - |
| `strawberry://routines` | Routine list |
| `strawberry://routines/history` | Aggregate run history |
| `strawberry://routines/new` | Open routines with the create-routine dialog |
| `strawberry://routines/:id` | Routine detail |
| `strawberry://routines/:id/edit` | Edit routine |
# Credit troubleshooting
Source: https://docs.strawberrybrowser.com/troubleshooting/credits
Understand unexpected credit drops, rate-limit windows, top-ups, paying accounts, and how to reduce usage.
If credits changed unexpectedly, first check whether a companion response, agent run, routine, transcription follow-up, or connected app task recently ran.
## Credits dropped without an obvious agent
Normal chat replies can use credits. A visible agent block is not required for AI usage.
Long prompts, attached files, large tab context, and advanced models can increase cost.
## A task stopped before finishing
Check the chat for a request for input, a credit message, or an error. If the companion returned a sample and you want the full batch, review the sample and ask it to continue. A small result alone does not tell you whether a plan limit was the cause.
## Rate-limit window is active
A rate-limit window is a short-term usage guardrail. It can appear even if monthly credits remain.
Open the chat content panel to see the active window and refill time.
## Top-ups not used yet
Available included credits normally pay before purchased top-ups. Top-ups can also pay when a rate limit temporarily holds back monthly credits. Purchased top-ups do not expire at month end. Check **Available now** and the credit breakdown at `strawberry://settings/account`.
## Check which account pays
Open `strawberry://settings/account` to see your paying account and credit breakdown. If you belong to several teams, use **Paying account** to choose one. On the web, use [Billing & usage](https://strawberrybrowser.com/account/billing).
The selected team pays first. Eligible Personal plan and extra credits may be used automatically afterward; the free Personal allowance is excluded. Viewing another team in team settings does not switch who pays, and switching teams does not transfer credits.
## Your team has no available credits
Check `strawberry://settings/account` for available credits and refill times. Team admins and owners can buy shared top-ups or review seat plans at `strawberry://settings/team`.
There is no automatic pay-as-you-go overage to enable. If no eligible team or Personal reserve credits are available, wait for a refill or ask an admin or owner for help.
## Reduce usage
* Ask for a plan before execution.
* Ask for a sample before a large batch.
* Limit rows, pages, sources, or candidates.
* Use files and connected apps instead of pasting huge text.
* Stop or steer off-track chats.
* Save stable context in memory.
* Save repeated process in skills.
# Storage and cleanup troubleshooting
Source: https://docs.strawberrybrowser.com/troubleshooting/storage-and-cleanup
Free up storage, manage large chats, understand public links, and choose the right cache or site data cleanup action.
Use `strawberry://settings/storage` for app storage and `strawberry://settings/privacy` for browser data cleanup.
## Check storage usage
1. Open `strawberry://settings/storage`.
2. View total storage used.
3. Open **More** for category breakdown.
Empty chats are not saved to disk until you send your first message.
## Free up space
Use storage settings to clean large local categories such as chat images or large chats when available.
For site-specific data, use privacy settings or site settings.
## Cache versus cookies and site data
* **Clear Cache** removes cached content and service workers. It keeps cookies and local site databases, but websites may need to reload or rebuild offline content.
* **Clear Cookies and Site Data** signs you out of websites and can remove preferences.
* Site **Clear cache** also removes that site's service workers, which can affect offline features.
* Site **Clear site data** removes that site's cookies, local storage, IndexedDB, WebSQL, service workers, and cache storage.
## Public links
Public file links show the current synced file or folder. Edits and files added to a shared folder can appear through the same link after a short delay. For a fixed version, share a separate copy and leave it unchanged.
To stop future access through the link, revoke it from the share dialog. Copies already downloaded are not removed.
## File preview issues
Spreadsheet files such as `.xlsx`, `.xls`, `.csv`, and `.tsv` render as tables in chat artifact previews. Unsupported binary files show an **Open externally** option.
HEIC and HEIF image attachments are converted to JPEG during chat image preparation before AI upload.
# Support logs and issue reports
Source: https://docs.strawberrybrowser.com/troubleshooting/support-logs
Send Strawberry issue reports with logs, describe reproduction steps, and know what information helps support.
Use **Strawberry** -> **Report Issue** from the application menu to send an issue report.
The message field is optional, but a useful report helps the team diagnose faster.
## What gets shared
Submitting an issue report sends app logs and a diagnostics bundle to Strawberry support. Depending on the problem, it can include recent logs, app and device details, open-page information, and performance, file-sync, or other troubleshooting details.
When available, **Include chat** and **Include a screenshot of this tab** are selected by default. Turn either off if you do not want to include it. Files you attach are sent too. Review those choices and attachments before submitting.
Logs help diagnose crashes, failed integrations, update problems, migration issues, transcription problems, and browser errors.
## What to include
Add:
* What you were trying to do
* What happened instead
* The route or page you were on
* Whether the issue repeats
* The relevant connected app
* The time the issue happened
* Any visible error message
## Billing or account issues
For billing issues, include:
* Account email
* Plan or team involved
* Whether it happened in personal billing or team billing
* Stripe portal behavior if relevant
* What action you took, such as upgrade, downgrade, cancel, top-up, add card, invite, or seat change
## Privacy note
Do not paste secrets, passwords, private customer data, or sensitive tokens into the issue message.
## Before reporting
If Strawberry is still running and the issue is not an unexpected exit, try:
1. Restart Strawberry.
2. Reproduce the issue once.
3. Report immediately after reproducing so logs contain the relevant event.
## If Strawberry will not open or keeps exiting
Download the [Strawberry Diagnostics Collector](https://www.strawberrybrowser.com/diagnostics)
for Windows or macOS. It runs separately and saves a local report without uploading anything.
On Windows, open the collector before reopening Strawberry after an unexpected exit. Click **Start**
and wait a few minutes. It saves existing crash reports first, then automatically observes a running
Strawberry or opens the installed copy to capture startup. You do not need to close Strawberry;
the collector finishes on its own and leaves it running. If Strawberry cannot start or exits
during collection, the report still includes the available evidence and any launch error.
Drag the finished report into your private support conversation, or click **Show in File Explorer**.
No setup or mode selection is needed. Technical details are available if support needs them.
Review the report before sharing it. Logs and crash dumps can contain private information, including
page contents or tokens held in memory. Include the incident's local time and what happened in your
message. Support can help with longer monitoring or additional crash and hang capture if needed.
# Transcription troubleshooting
Source: https://docs.strawberrybrowser.com/troubleshooting/transcription
Fix microphone, system audio, permissions, accuracy, server, meeting notification, and transcript location issues.
Use this page when transcription, dictation, or meeting recording does not behave as expected.
Open transcription settings at `strawberry://settings/transcription`.
## No audio detected
1. Check that the correct microphone is selected.
2. Click **Refresh** to re-scan devices.
3. Confirm microphone permission is granted.
4. Try the built-in microphone.
5. Restart Strawberry.
## macOS permissions not taking effect
After granting microphone or screen and system audio access, restart Strawberry from `strawberry://settings/transcription`.
macOS permission changes often do not apply to already-running apps.
## Remote meeting audio missing
On macOS, system audio capture requires screen and system audio permission. Enable it, then restart Strawberry.
On Windows, Strawberry does not require a separate system-audio permission prompt. Check Windows audio and privacy settings if audio is missing.
## Poor accuracy
Try:
* Add spoken languages instead of relying on auto-detect.
* Add preferred terms for names, brands, acronyms, and jargon.
* Switch from Bluetooth headset microphones to the built-in microphone.
* Use **Test levels** to verify input.
* Adjust noise thresholds in Advanced settings.
## Cannot reach transcription servers
Transcription requires internet access. Check network connectivity, VPN rules, and firewall restrictions.
## A saved recording is taking a while to transcribe
Large recordings can take several minutes to upload and process. Keep Strawberry open and connected, then check `strawberry://meetings` for the finished transcript.
## Meeting toast not appearing
Check:
* Scheduled meeting notifications are enabled.
* Auto-detected meeting notifications are enabled.
* Google Calendar is connected for scheduled reminders.
* The meeting URL belongs to Google Meet, Zoom, or Microsoft Teams.
## Where is my transcript?
Open `strawberry://meetings`.
Use the **Recordings** filter for saved recordings that still need transcription. Meeting files are also available through `strawberry://library`.