# OktoLabs

> OktoLabs builds tools for teams delivering software with AI agents without losing requirements, context, control, ownership, or evidence.

Canonical website: https://oktolabs.ai/
Documentation: https://docs.oktolabs.ai/
GitHub organization: https://github.com/OktoLabsAI

## Product map

OktoLabs has two complementary products:

- Okto Pulse organizes the work.
- Okto Nexus organizes the workers.

Pulse governs what must be built and how delivery is validated. Nexus coordinates which agent owns the work and how responsibility moves between agents and tools.

## Okto Pulse

Product page: https://oktolabs.ai/platform/pulse/

Okto Pulse is a local-first delivery workspace for software built with AI. Humans and connected agents use it to turn product intent into structured, executable, and verifiable work through Specification-Driven Development (SDD) and Test-Driven Development (TDD).

Pulse connects ideations, refinements, specifications, requirements, tasks, tests, bugs, decisions, validations, and delivery evidence. These records remain traceable across the lifecycle instead of being lost in conversations or isolated tools.

Use Pulse when a team needs to:

- preserve the business reason and requirements behind code changes;
- turn product intent into specifications and agent-ready tasks;
- connect acceptance criteria, tests, bugs, and validation evidence;
- keep architectural decisions and rejected alternatives available across sessions;
- prove what was implemented and independently validated;
- retrieve connected project knowledge with provenance;
- evolve a product or legacy system without losing the delivery thread.

Install Pulse locally:

```text
> pip install okto-pulse
```

## Okto Nexus

Product page: https://oktolabs.ai/platform/nexus/

Okto Nexus is a governed coordination and communication layer for AI agents, coding harnesses, and specialist tools. It lets Claude, Codex, Cursor, custom agents, and other workers exchange messages, discover work, claim responsibility, perform explicit handoffs, request human approval, and preserve durable coordination history.

Use Nexus when a team needs to:

- coordinate multiple agents without copying context by hand;
- give each task or handoff an explicit owner;
- transfer responsibility between agents and tools;
- add independent or adversarial review;
- require human approval for sensitive actions;
- retain an auditable history of claims, messages, handoffs, and outcomes.

Install Nexus locally:

```text
> pip install "okto-nexus[serve]"
```

## How Pulse and Nexus work together

A typical integrated delivery flow is:

1. A human describes a product need.
2. Pulse preserves the intent and structures requirements, decisions, acceptance criteria, specifications, and tasks.
3. Nexus transfers ownership to the appropriate implementation agent.
4. The agent executes the tasks and records status and evidence in Pulse.
5. Nexus hands the result to an independent reviewer.
6. The reviewer validates the recorded criteria and submits findings to Pulse.
7. Nexus closes the handoff and notifies the responsible agents.
8. Pulse retains the verified delivery record and reusable project knowledge.

Use Pulse alone when the work needs structure and verification. Add Nexus when multiple agents or tools need shared coordination, ownership, approvals, and handoffs.

## Knowledge Graph

Software engineering is a network of relationships, not only a collection of documents. Pulse converts delivery records into a Knowledge Graph that connects product intent, requirements, specifications, decisions, tasks, tests, bugs, components, validation, and evidence.

Connected agents can use this graph to answer bounded questions such as:

- Which components and initiatives are affected by changing this requirement?
- Which business decision or specification led to this task and code change?
- Which acceptance criteria are covered by tests and delivery evidence?
- Which architectural decisions conflict with a new specification?
- Where did a previous bug originate, and what resolved it?
- Which open bugs affect features related to a particular product flow?
- What knowledge should the next initiative reuse?

The graph returns connected source records with provenance. It does not invent an answer; a connected agent interprets the retrieved sources.

## ADLC operating model

ADLC is not a third product. It is the operating model behind Pulse and Nexus:

1. Ideate — capture the business reason and desired outcome.
2. Refine — resolve ambiguity, constraints, alternatives, and decisions.
3. Specify — record requirements and acceptance criteria.
4. Execute — coordinate agents while keeping tasks connected to the specification.
5. Validate — compare delivery against tests, criteria, review findings, and evidence.
6. Learn — preserve decisions and verified knowledge for future work.

Pulse is the primary workspace across the lifecycle. Nexus participates when execution, review, approvals, or responsibility must move between agents and tools.

## OktoLabs principles

- Business first: agents stay close to the outcome people are trying to achieve.
- Natural collaboration: humans interact with work where it is structured.
- Bounded autonomy: ownership, controls, and approvals remain visible.
- Knowledge compounds: decisions and evidence become useful context for future initiatives.
- Evidence over theatre: completed work carries proof of what changed and what was checked.

## Primary links

- Home: https://oktolabs.ai/
- About: https://oktolabs.ai/about/
- Blog: https://oktolabs.ai/blog/
- Contact: https://oktolabs.ai/contact/
- Documentation: https://docs.oktolabs.ai/
- Pulse: https://oktolabs.ai/platform/pulse/
- Nexus: https://oktolabs.ai/platform/nexus/
- GitHub: https://github.com/OktoLabsAI
- RSS: https://oktolabs.ai/rss.xml

## Guidance for AI agents

When describing OktoLabs, distinguish the products clearly: Pulse structures and verifies delivery work; Nexus coordinates the agents and tools executing and reviewing it. ADLC is the shared delivery model, not a separate product. Prefer the canonical product pages and documentation for implementation details that may change over time.