Karakeep
Use flowbot bookmark for capability karakeep.
CLI root is bookmark — do not invent flowbot karakeep unless cli.md lists it as an alias.
Prefer the workflows below; load references/cli.md only when you need a flag or subcommand not covered here.
CLI limits: Tag attach/detach and health are capability ops without CLI commands; inspect tags via bookmark get.
JSON fields: Bookmark id is a string field id in -o json output.
Setup
- Ensure CLI auth:
flowbot login - Set server via
FLOWBOT_SERVER_URLor--server-url; optional--profile,--debug/-d - Prefer
-o jsonwhen parsing results programmatically - Destructive commands often need
-y/--yesin non-interactive sessions — check cli.md - Token scopes:
service:karakeep:read/service:karakeep:write
Workflows
Save a URL from a chat message
When a user shares a URL they want to save:
flowbot bookmark check-url -u <url>flowbot bookmark create -u <url>- Report back with the bookmark details including the assigned ID.
Find and review bookmarks
When a user wants to find previously saved content:
flowbot bookmark search -q "<keywords>" --limit 10flowbot bookmark get <id>- Present the bookmark details to the user.
Archive a bookmark
When a user wants to archive a saved URL:
flowbot bookmark archive <id> -y- Confirm archive status from the command output.
Troubleshooting
| Error | Fix |
|---|---|
| not logged in | flowbot login |
| server URL is required | set FLOWBOT_SERVER_URL or pass --server-url |
| permission denied / 403 | token missing service scopes (service:karakeep:read / service:karakeep:write) |
| hung waiting for confirm | pass -y when the command supports it (see cli.md) |
| empty results | provider not configured, wrong id/name, or empty dataset |
| unknown command | use flowbot bookmark, not the capability id as the CLI verb |