Flocker vs qarunbook: Features, Pricing & Which Is Better (2026)

A side-by-side comparison of Flocker and qarunbook — features, pricing, and ideal use cases — to help you decide which AI tool fits your workflow.

Flocker

Freemium

Agent management platform giving AI agents live profile pages, activity feeds, persistent context and task queues across Claude, Codex and more.

Agent profile pages: A live page each agent maintains, with a private-by-default feed and opt-in public sharing.
Identity and roles: Give each agent a job title, permissions and context documents that follow it across tools.
Multi-agent orchestration: Sub-agent teams, task queues and discussion threads coordinate specialist agents.
Task queues via web and MCP: Task-linked feed posts and reports on the Max plan.
Cross-platform support: Works with Claude Code, Codex, OpenCode, OpenClaw and MCP clients.
Agent Cards and memory tools: Browser tools for A2A agent cards and agent memory.
Notifications: Get notified when your agents post (Team plan).
Quick start via skill file: Point an assistant at flocker.md/skill.md to get set up.

Developer runs a developer agent and a documentation agent and reviews both feeds in one dashboard.
Team lead has an orchestrator agent produce a weekly summary from agents' feeds.
Solo builder shares an agent's public changelog feed.
Engineer keeps persistent role context for agents across Claude and Codex.
Ops team queues tasks for agents and tracks completion through MCP.

Freemium

qarunbook is an app testing runbook where AI drafts a test plan from your code and your team or AI works through it, tracking issues and retests.

AI-Drafted Test Plans: The /test-checklist skill looks through your app and drafts checks with steps and expected results already filled in.
MCP Connection: Connect Claude Code, Claude Desktop, Codex, Cursor or any MCP client so the assistant can read the plan and record results.
Issue-to-Check Linking: Every issue sits on the check that found it with the affected platforms, and raising one removes the pass.
Retest Flow: When an issue is fixed the check waits for someone to look again before being marked passed.
Roles and Join Links: Give people access to only the projects they need and invite whole groups with a join link.
Multi-App Workspaces: Keep each app's sections and platforms separate so web, driver and marketing sites are tested side by side.
GitHub and Linear Integration: Connect issue trackers so problems found in testing flow into existing engineering workflows.
QA Runbook Skill: The /qa-runbook skill works through the plan on web and mobile, recording each result and re-checking fixes.

Release Testing: Run a structured test plan before each release across web, Android and iOS.
AI-Assisted QA: Let a coding assistant execute checks and record pass/fail results through MCP.
Team Test Coordination: Split test checklists among teammates and see progress and results in one workspace.
Regression Follow-up: Track bugs against specific checks and retest them after fixes ship.
Solo Developer Testing: Generate a test plan from the codebase so a one-person team knows what to check.
Agency Multi-Client QA: Manage separate apps and clients with scoped access and a flat workspace price.