Okto Pulse
OktoLabs ↗ PyPI $ Get started
OktoLabs · Product no. 01 v0.1.2 · 2026

Spec-driven project management for AI agents.

A local-first kanban board with native MCP support. Okto Pulse is where humans and AI agents plan, refine, and ship together — on the same board, with distinct roles and zero collisions.

$ pip install okto-pulse
Install in one command
  • 150+ MCP tools
  • 5 Agent roles
  • 1 Command setup
  • Ø Cloud required
00  ·  PHILOSOPHY

Built for the Agentic Development Life Cycle.

ADLC is what the SDLC becomes once AI agents are first-class participants, not helpers on the side. Humans set intent, agents execute against spec, validators gate the result — and every artefact is traceable end to end. Okto Pulse is the first spec-driven platform built from the ground up for this cycle.

01

Intent is specified

Humans (and agents in upstream roles) define problem, scope, acceptance criteria. No code without spec.

02

Agents execute

Executor agents pick tasks linked to specs. MCP exposes the board so any agent can act — with its role permissions enforced.

03

Gates validate

Validator agents (or humans) gate the output against the original spec. Nothing ships without passing its gate.

04

Everything is traceable

Task → sprint → spec → refinement → ideation. Every artefact linked, every decision auditable.

01  ·  PIPELINE

From idea to shipped task
in five disciplined stages.

Okto Pulse enforces a deliberate flow. Each stage has its own artefacts, its own review gate, and its own agent permissions — so nothing jumps from whim to production without passing through refinement and spec.

  1. 01

    Ideation

    Raw ideas, problem statements, proposed approaches. Evaluated before promotion.

  2. 02

    Refinement

    Scope, decisions, constraints. Context compiled from the ideation and Q&A.

  3. 03

    Spec

    Requirements, acceptance criteria, test scenarios, business rules, contracts.

  4. 04

    Sprint

    A spec sliced into a shippable iteration. Objective, tasks, validation gate.

  5. 05

    Task

    A kanban card linked to its spec. Moves through the board until validated.

02  ·  CAPABILITIES

Everything a team — 
human or otherwise — needs to ship.

Opinionated where opinion matters, flexible where it doesn't. Okto Pulse ships with the primitives you'd build anyway — pipeline gates, role-based permissions, MCP tools, analytics — so you can focus on the work.

F·01

Spec-driven pipeline

Every task is traceable back to a spec. Specs derive from refinements. Refinements from ideations. No orphan work.

F·02

Role-based multi-agent

Five built-in agent presets — Executor, Validator, QA, Spec, Full Control — with surgical permission grids.

F·03

Native MCP server

150+ tools over Model Context Protocol. Plug Claude, Cursor, Windsurf, or any MCP-aware agent directly into your board.

F·04

Local-first by design

SQLite under the hood. Your data is a file on your machine. Cloud sync is optional, never required.

F·05

Kanban + flow, unified

Tasks in a board, specs in a list, sprints in a queue. Everything cross-links so context is never more than one click away.

F·06

Single-command install

pip install okto-pulse. One port for the app, one for MCP. No Docker, no accounts, no friction.

03  ·  DIFFERENTIATION

Five agents. One board.
Zero collisions.

Okto Pulse ships with five built-in permission presets that give each agent on a board a distinct area of responsibility. They work in parallel without stepping on each other — and they are built-in, not something you configure yourself.

01

Executor

built-in

Implements normal cards. Moves tickets not_started → validation. Cannot submit validations or promote to done.

Cards
Write
Specs
Read-only
Sprints
Read-only
Gate
No
02

Spec

built-in

Defines the pipeline upstream. Owns ideation, refinement, and spec content. Composes sprint plans and opens the specification.

Ideations
Write
Specs
Write
Cards
Read-only
Gate
No
03

Validator

gate holder

Exclusive gate holder. Submits spec, task, and sprint validations and evaluations. Touches cards only to attach validation results.

Validations
Exclusive
Evaluations
Exclusive
Cards
Validate only
Gate
Yes
04

QA

built-in

Owns test scenarios and the test-card lifecycle. Writes regressions, runs them, and reports. Does not submit validation gates itself.

Scenarios
Write
Test cards
Write
Specs
Read-only
Gate
No
05

Full Control

built-in

Unrestricted access. Intended for a trusted orchestrator agent or for the human owner who bootstraps the board before delegating.

Everything
Unrestricted
Cards
Write
Specs
Write
Gate
Yes
06

Custom

bring your own

Clone any built-in preset as a starting point — or compose your own permission grid across boards, specs, sprints, cards, validations, and analytics.

Surface
8 resources
Verbs
read · write · gate
04  ·  THE BOARD

Every stage has its own view.

The pipeline lives in the same application as the kanban board. You switch tabs, not tools.

01 / 05

Ideations

Raw ideas with problem statements, proposed approaches, and evaluation state.

Ideations tab with five draft items
03 / 05

Specs

Versioned specifications in Draft, Review, Approved, Validated, or Done.

Specs tab with three done specifications
04 / 05

Sprints

A spec broken into shippable iterations. Each sprint owns a set of cards and a validation gate.

Sprints tab with two draft sprints
05  ·  INSIGHT

Analytics that tell you
what the board is actually doing.

Every artefact in the pipeline is instrumented. Okto Pulse surfaces a conversion funnel, weekly velocity, validation gate throughput, sprint evaluations, and drift against the original spec — on the same screen, for every board.

Okto Pulse analytics dashboard showing KPI tiles, validation gates, conversion funnel, velocity chart, and per-board breakdown
Okto Pulse analytics coverage screen showing completeness versus drift, coverage by spec, agent ranking, and searchable spec table
Coverage by spec Completeness, drift, tests, rules, contracts, and agent contribution in one view.
Okto Pulse analytics detail screen for a spec with acceptance criteria coverage, functional requirements, test scenario status, and task metrics
Spec drill-down Trace a single spec through acceptance criteria, requirements, tests, tasks, and cycle time.
A · 01

Conversion funnel

Ideations → Refinements → Specs → Tasks → Done. Track what you started versus what you shipped, with overall completion percentage.

A · 02

Validation gates

Four tracked gates — spec, task, spec evaluation, sprint evaluation — each with its own submission count and pass/fail trend.

A · 03

Velocity & drift

Weekly throughput split by implementation, tests, and bugs. Average drift surfaces when specs start to deviate from their original shape.

A · 04

Export & drill-down

Every KPI card is clickable. Drill into a spec or sprint for a deeper view, or export the raw numbers as CSV for your own tooling.

06  ·  KNOWLEDGE

Evolves with you,
one initiative at a time.

As projects move through the ADLC, Okto Pulse consolidates ideations, refinements, specs, tasks, and bugs into a living knowledge graph. Every shipped decision becomes reusable context for future dashboards, discovery, and the next round of ideation.

Okto Pulse knowledge graph view showing connected decisions, requirements, constraints, bugs, test scenarios, and learnings
Project memory becomes operational knowledge. The graph connects delivery evidence back to the ideas that started it, so the next initiative begins with sharper context instead of an empty board.
K · 01

Capture the work

Ideations, refinements, specs, tasks, and bugs become typed nodes with provenance.

K · 02

Connect the evidence

Decisions, requirements, constraints, tests, and implementation signals stay linked.

K · 03

Grow the dashboard

Analytics gains a reusable knowledge base for discovery, drift, and future planning.

K · 04

Start smarter

New initiatives inherit what the project already learned, reducing repeated context work.

07  ·  PROTOCOL

Plug any MCP-aware agent
directly into your board.

Okto Pulse ships its own MCP server. Point Claude Code, Cursor, Windsurf, or a custom orchestrator at it, and the agent gets the full board API — 150+ tools spanning ideations, refinements, specs, sprints, cards, validations, analytics, and agents themselves.

.mcp.json 
{
  "mcpServers": {
    "okto-pulse": {
      "url": "http://127.0.0.1:8101/mcp?api_key=dash_xxx"
    }
  }
}
08  ·  GETTING STARTED

Four commands to a running board.

  1. 01

    Install from PyPI

    $ pip install okto-pulse
  2. 02

    Initialise local data

    $ okto-pulse init
  3. 03

    Run the board and MCP server

    $ okto-pulse --api-port 8100 --mcp-port 8101 serve
  4. 04

    Point your agent at .mcp.json

    Okto Pulse generates the config on first init. Drop it next to your agent and the board is wired up.

Free to use · Source-available under Elastic License 2.0

Install from PyPI Source on GitHub