Miniflux
Use flowbot reader for capability miniflux.
CLI root is reader — do not invent flowbot miniflux 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: No reader refresh or star/unstar CLI; feed fetch is server-side. Mark read/unread with reader update-entries.
JSON fields: Feed and entry ids are integers in -o json (id).
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:miniflux:read/service:miniflux:write
Workflows
Subscribe to a new feed
When a user shares a blog or feed URL they want to follow:
flowbot reader create -u <feed_url>flowbot reader list- Pick the new feed id from list output (server fetches entries asynchronously).
flowbot reader feed-entries <feed_id> -n 5- Report the latest entries to the user; retry feed-entries shortly if still empty.
Catch up on unread entries
When a user wants to see what's new across all feeds:
flowbot reader entries -s unread -n 20- Present the entries in a readable format.
- If the user wants to mark as read, run: flowbot reader update-entries -i -s read
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:miniflux:read / service:miniflux: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 reader, not the capability id as the CLI verb |