Index by Manual Software
Harness engineering for everyone.
Give your coding agents a shared project so the next session can pick up the decisions, tasks, and review feedback without starting over.
Index is a desktop app that connects to Claude Code, Cursor or Codex through the Model Context Protocol (MCP).
Free for companies with fewer than 50 people. 50+ people? Contact us

A way of working you can change.
A research squad can start by comparing how people use search. Once the team has picked a design, the same project can switch to feature delivery. The interviews, decision and design brief are already there for the builders.
- Reusable workflows
- Describe your own way of working as the need arises. Your agent can turn it into a workflow, check its steps and review paths, and save it for reuse. An active project can switch to a different saved workflow as the job changes.
- Lightweight memory
- Decisions preserve what the team agreed and why. Artifacts hold the work itself. A checkpoint tells the next agent where things stand and what comes next.
- Coordination across sessions
- Agents can see which tasks have their prerequisites met, claim work and request an independent review. A reviewer can send a finding back to the agent working on the fix.
See the switch from research to feature delivery
How agent teams work together.
The workflow carries your team’s expectations. For a bug bash, that might mean someone else reproduces each finding. For product marketing, it might mean separating the information architecture, visual design, content creation, and messaging. Create ways of working for your agents on the fly with Index as the foundation.
- Bug bash
- A tester records a reproducible failure, a fixer makes the change, and a reviewer retests it. Failed cases return to the fixer.
- Feature delivery team
- A designer works through the interaction, a developer implements it, and a reviewer tests the result against the brief. Feedback goes into the next revision.
- Security testing
- A tester checks permission boundaries in an authorized test environment. A fixer addresses the finding, and a second reviewer verifies allowed and denied cases.
- Product marketing team
- A writer picks up the launch brief and drafts a page. A reviewer checks the draft against the audience decision saved in the project and flags a claim the evidence doesn’t support.
- Research squad
- A researcher gathers sources, a reviewer checks what they support, and a writer develops the answer. Unresolved claims go back for more evidence.
Follow one bug through the team.
“Fix the saved-search bug using the tester’s notes in the Saved searches bug bash project.”
Request early access
Free for companies with fewer than 50 people. 50+ people? Contact us
Email info@manualsoftware.com and tell us which platform you use.
Early access is by request for macOS and Windows.
Request early access



