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 profile-level connected apps
- 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:
- General details
- Files
- Apps
- Skills
- Routines
- Sharing
The Files tab opens the filesystem roots the companion can use, including the companion folder, your workspace, and team workspace when available.
Companion-specific skills
When you create a skill from companion settings, Strawberry saves it in that companion’s own Files -> [companion name] -> 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.
Chat history is not shared. When someone opens a shared companion, they start their own local chat with it.
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, permissions, or app needs.
- 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.
