About wakala

What it is

A governed task tracker built for AI agents. Tasks have a definition of done, dependencies, statuses, assignees, priority, and approval gates. The point is not to plan projects — it's to keep an agent's work honest. The homepage carries the short version while the business is being restructured.

Why it exists

The hard part of getting agents to do real work isn't capability — it's governance. Most agent tooling optimizes for throughput: how many tasks did the agent finish, how fast, how cheaply. wakala optimizes for correctness: did the agent do the right things in the right order, and can you prove it after the fact.

That's a smaller audience than the broader agent-tool ecosystem. The people who need it are the ones shipping agent work to production and discovering that the prompt layer alone doesn't enforce their standards. For them, "the agent said it was done" isn't good enough. They need binary-enforced guardrails — a server that rejects bad transitions, not a comment that flags them.

Who wakala is for (and not for, yet)

The primary persona is the solo agent operator — one developer, one MCP-compatible agent, one project at a time. You're already shipping real work through the agent, and you've discovered that prompt discipline doesn't survive a long enough context window. The work is too important to leave to "the agent said it was done."

You're in the target audience if

• You run an MCP-compatible agent (Claude Code, Cursor, OpenCode, etc.) on real engineering work
• You've shipped something the agent "completed" that wasn't actually done
• You prefer binary-enforced rules over prompt-encouraged rules
• You want one source of truth between your work and the agent's work

Not for you, yet, if

• You need a full enterprise PM suite with custom fields, workflows, and integrations on day one
• Your team isn't using any AI agents in engineering workflows yet
• You need team / multi-tenant features (these ship later)
• You only do human-only work tracking (use a dedicated tracker; wakala assumes an agent is involved)

Status

We're restructuring the business. The homepage is a holding notice for now: signups are closed, no new keys are issued, and the product pitch is offline while we sort out the company around the product.

wakala itself hasn't changed. Same governed task tracker, same binary-enforced guardrails, same MCP surface. We're using the pause to sharpen the workflow rules before we open the doors again — and we'll write to the people already with us before we do.

Contact

The operator is reachable at info@wakala.dev. That's a real inbox, read by a real person, with a real SLA on the order of a day or two. There is no support tier, no escalation path, no status page. If you need any of those, this isn't the right product for you yet.