Huddle

Overview

Huddle is a21e’s conversational interface. It supports two modes:

Single mode — fast, one-model execution through the intent pipeline
Multi mode — multi-model deliberation where models plan, critique each other, and reach consensus

Creating a session

Via the web interface

Navigate to a21e.com/huddle
Type your request in the composer
Select Single or Multi mode (or leave on Auto to let a21e decide)
Submit

Via the API

curl -X POST https://api.a21e.com/v1/huddle \
  -H "Authorization: Bearer YOUR_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "input": "What caching strategy should we use for our API?",
    "mode": "multi",
    "model_tier": "premium"
  }'

Single vs. Multi mode

	Single	Multi
Speed	Fast (seconds)	Slower (30s-2min)
Models	One model selected by tier	2-4 models deliberate
Best for	Direct tasks, code generation	Architecture decisions, trade-off analysis
Output	Direct response	Consensus report with dissenting views

Follow-up messages

Send follow-up messages to continue the conversation:

curl -X POST https://api.a21e.com/v1/huddle/sessions/{session_id}/messages \
  -H "Authorization: Bearer YOUR_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "content": "What about Redis vs Memcached specifically?",
    "mode": "single"
  }'

You can switch modes between messages — ask a quick follow-up in single mode after a multi-model deliberation.

Repository context

When your workspace has a connected GitHub repository, Huddle automatically:

Scans your codebase — identifies relevant files based on your question
Inspects files — reads configuration, source code, and tests
Grounds responses — references your actual code with linkified file paths

For codebase-specific questions (“audit my auth implementation”, “do I have test coverage for the API?”), a21e escalates to deeper inspection with more files analyzed.

Streaming

Pass ?stream=true for server-sent events:

curl -N "https://api.a21e.com/v1/huddle?stream=true" \
  -H "Authorization: Bearer YOUR_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"input": "Review my error handling patterns", "mode": "single"}'

Events include stage (pipeline progress), token (response chunks), metadata, and done.

Getting Started

Guides

Account

Legal

Overview

Creating a session

Via the web interface

Via the API

Single vs. Multi mode

Follow-up messages

Repository context

Streaming

​Overview

​Creating a session

​Via the web interface

​Via the API

​Single vs. Multi mode

​Follow-up messages

​Repository context

​Streaming

Overview

Creating a session

Via the web interface

Via the API

Single vs. Multi mode

Follow-up messages

Repository context

Streaming