FAQ

Yes. Kibo offers all core features—projects, tasks, views, storage, and AI—for individual users. Collaboration features (assignments, approvals, roles) activate effortlessly as your team grows.

Kibo is built for speed and simplicity. Many tools on the market force users to spend hours micro-managing dozens of statuses, fields, and complex configurations for every single task. Kibo removes this administrative burden: it gives you the flexibility you need, deep document indexing, and native MCP integration to operate directly from the tools you use every day (like your code editor).

Your data security is built on workspace isolation and strict Role-Based Access Control (RBAC). Access to information and documents is strictly bounded by the permissions you set, at both the organization and document levels.

Each paid seat adds its monthly allowance to a shared organization pool that all members draw from. Each person also has a daily cap set by the plan: an admin can raise or lower it for individual people, for example to give a project manager more headroom.

The side panel shows, in real time, your credits for today, the organization's monthly credits, and your credit pack balance. When credits run out, AI requests stop and scheduled automations are skipped, with a notification.

If your organization has bought a credit pack, you keep working: once the monthly allowance is used up, Kibo automatically switches to the pack balance for all members. The pack also lets you go past the plan's daily cap, but not a cap an admin has set for you.

No. Credits bought in packs never expire: they stay with the organization until they are used, with nothing lost at the end of the month.

Kibo provides an MCP server that clients such as Claude, Cursor, or VS Code can connect to. You connect with an API key scoped to specific permissions or, from Claude, by authorizing access to your account (OAuth). From there you manage tasks and query projects without leaving your usual workspace.

MCP access is available on paid plans.

No. Through MCP, your client reads and edits tasks, comments, and dependencies: Kibo does not call any AI model, so no credits are used. The processing happens in your client, on its own resources.

Kibo's AI is not just a chat but an agent that acts on your workspace. Give it quick commands on tasks, such as "Move open tasks to next Monday" or "Close all of today's tasks", or start from a document: attach a PRD and ask it to create phases and tasks linked by their dependencies. The agent carries out requests directly and asks for your confirmation only for destructive operations, such as deletions.

Kibo indexes uploaded files into a semantic knowledge base. When you ask a question, the system identifies key context within your documents and answers from it, linking back to the original source so you can check it.