AIndex
Download free

Adoption · For: dev

Features stay hidden when they only exist as low-level commands or undocumented MCP actions.

The registry is the source of truth for feature pages, dashboard links, CLI discovery, MCP status and setup success screens.

Download freeAll workflows
$ aindex features --json && aindex status --json

feature_id
command
mcp_action
maturity
vscode_action

Command

VS Code, CLI and MCP Surfaces

The same structured JSON powers CLI, MCP tools and IDE sidebars.

CLI

aindex features --json && aindex status --json

MCP

status detail=features

Example output
  • feature_id
  • command
  • mcp_action
  • maturity
  • vscode_action

What the Brain does automatically

The Brain fires this workflow for you.

Every feature appears where agents are actually used: setup, CLI, MCP status, dashboard and IDE.

On demand

Run when you need it

This workflow is not auto-triggered by the Brain yet; run it explicitly with the command above or its MCP action.

Not measuredProof
Not measuredNo public benchmark covers this workflow yet — the proof is the live command output above, not a positioning claim.
Source—
AvailableRuntime feature status · 0 evidence item(s). Metadata-only; no raw source included.

Required tier

Where this becomes commercially available.

The same structured JSON powers CLI, MCP tools and the IDE sidebar so features stop hiding in low-level commands.

Free · €0

Foundation

Visible as a product workflow and pilot proof target; do not treat as fully shipped enterprise automation yet.

Buyer grade

Foundation

Names the parity workflow and proof path without claiming full Sourcegraph-class depth.

Visible in
  • Setup success
  • CLI features
  • MCP status
  • VS Code sidebar
  • Docs
  • Command palette

This workflow stays discoverable across setup, CLI, MCP status, docs, dashboard and pricing — never a hidden command.

Feature visibility checklist

Buyer-visible names covered by VS Code, CLI and MCP Surfaces.

This keeps grouped product names discoverable without claiming a separate maturity level from the underlying workflow.

Feature DiscoveryFoundation

VS Code, CLI and MCP Surfaces

No workflow ships as a hidden command or undocumented MCP action.

Surface
Feature registry, setup success, dashboard, docs, pricing
Buyer-safe status
Foundation · Foundation
Runtime
preview only
VSCodeFoundation

VS Code, CLI and MCP Surfaces

IDE actions mirror the same registry used by CLI, MCP and web.

Surface
VS Code sidebar and command palette
Buyer-safe status
Foundation · Foundation
Runtime
preview only
CLIFoundation

VS Code, CLI and MCP Surfaces

Commands expose the same feature names, statuses and JSON contracts.

Surface
aindex features, status, context, pack and workflow commands
Buyer-safe status
Foundation · Foundation
Runtime
preview only
MCPFoundation

VS Code, CLI and MCP Surfaces

Five tools route advanced actions without schema bloat.

Surface
context, search, navigate, status and remember
Buyer-safe status
Foundation · Foundation
Runtime
preview only

Adoption

No feature ships invisibly.

One registry

Download freeSee pilot proof