Beav Docs
Beav documentation
Start with the desktop app and browser extension, then learn web access, capture, knowledge, content creation, media processing, and external Agent connections.
Beav is a local-first AI workspace for creator content and assets. It keeps web pages, comments, images, videos, local files, and finished drafts in one workspace, so every source stays searchable, citable, and reusable.
Start here
Using Beav for the first time? Finish these steps in order:
- Install the Beav desktop app.
- Install the Chrome / Edge browser extension.
- Save your first web page.
- Turn captured sources into topics and drafts.
Common entry points
| Goal | Guide |
|---|---|
| Use Beav from a browser, a phone, or a server | Web access |
| Install from the command line and use Beav in your local browser | Install Beav CLI |
| Save web pages, Xiaohongshu, YouTube, images, or selected text | Capture pages and platform content |
| Let Beav drive real, already signed-in browser pages | Browser control |
| Generate covers, images, videos, or audio | Images, video, and audio |
| Call third-party APIs or automate a repeatable workflow | Environment variables and scripts |
| Let Codex, Hermes, or OpenClaw use Beav | Connect an external Agent |
| Fix install, connection, or long-task problems | Troubleshooting |
How Beav organizes creation
The browser extension and local imports bring sources into the workspace. The knowledge base, media library, and subject library keep what is worth reusing over time; topic planning, Task Briefs, and drafts turn it into concrete work; image, video, and audio results flow back into the media library.
An external Agent that connects to Beav should follow the same path: read the real sources and the current task first, then create a brief, a draft, or a media task, and finally save the results back into Beav — instead of leaving behind a block of chat text nobody can reuse.
Data and permissions
By default Beav keeps workspace data on your machine. Browser capture, media generation, and third-party model calls reach the relevant page or service only for actions you start. Paid generation, browser control, deletion, publishing, and external exports from an external Agent require approval; see Capabilities and approvals for the full rules.
Mini Apps
Mini Apps are local apps installed inside Beav. They keep their own interface state and, once the user grants permission, can call Beav's capture, knowledge base, asset library, media processing, AI, and automation capabilities.
Read the Mini App development guide for the package structure, the window.redbox SDK, every capability name, the security boundary, and the release checklist.