SubAgent
The era of one AI burning the midnight oil on 100,000 rows of feedback is over. WeJot now puts a whole AI research team to work at the same time.
SubAgent brings SubAgent collaborative analysis to data analysis in WeJot. Instead of a single agent muscling through massive datasets alone, the main agent now works like a research team: it splits the work across several “subagents” who run in parallel, then consolidates their findings into one answer.
Why subagents exist
In practice we found that many complex tasks just don’t fit a single agent:
- Tens of thousands of user comments, large bodies of open-ended responses, oceans of reviews and social chatter.
- The more data one agent ingests, the more its context bloats — attention drifts, and the model can simply fail.
- A single viewpoint also misses edge signals — the same feedback may need sentiment, pain points, tags, and trend reading all at once.
SubAgent lets the system operate like a real team: someone analyzes, someone classifies, someone summarizes, and a lead aggregates at the end.
Where you’ll see it
-
The
/quick-action menu in the chat inputType
/in the input box. The Skill popover lists SubAgent as a built-in entry at the top. Once selected, a “Subagents” tag appears in the input to indicate the current turn will delegate parallelizable subtasks to subagents.
-
The “Subagents at work” group in the chat stream
When the main agent dispatches subagents, a Batch Analysis block appears in the chat. Each batch corresponds to one subagent:
- Every subagent has its own number, avatar, and nickname (e.g. “Subagent 01 · Searcher”).
- While running, a spinner shows what it’s doing right now (“Running text analysis”, “Data read complete — moving on”).
- When done, the subagent gets a checkmark and its subtask list auto-collapses, handing off to the main agent for synthesis.
- Hover the avatar to open a subagent info card showing the current subtask checklist with per-step status (Pending / In progress / Done).

How it works
SubAgent is a multi-agent collaborative execution pattern:
- The main agent decomposes the task — slices a large analysis into parallelizable subtasks and picks the right subagent role for each.
- Parallel delegation — every subagent handles its slice in its own isolated context, preventing the context bloat and attention drift you’d hit if one agent did it all.
- Visible progress — each subagent’s tool calls and stage updates stream into the chat in real time.
- Unified synthesis — once subagents finish, the main agent fuses the results and outputs conclusions, charts, even a full report.
Take 100,000 rows of VOC feedback as an example: one subagent handles sentiment analysis, one extracts pain points, one assigns tags, one spots outliers, one summarizes trend shifts — and the main agent stitches their work together to surface trends, pain points, and latent needs from the raw text.
You decide who does what
SubAgent is not a fixed pipeline. You can tell the main agent how to divide the work, for example:
- “Analyze from a product manager’s perspective.”
- “Focus only on churn reasons.”
- “Concentrate on high-value users’ needs.”
- “Find unmet needs that competitors miss.”
The main agent will split the task, define the right roles, and dispatch them to subagents running in parallel.
Thoughtful details
- Stable subagent identity — within the same project, subagents with the same name share the same avatar; refreshing or returning to the session keeps avatars and numbers unchanged.
- Projects stay independent — each survey has its own shuffled avatar sequence, re-randomized on first appearance, so subagents in the same project never duplicate avatars.
- Stable streaming — every batch renders by a stable ID, so subagents don’t flicker or swap identity mid-stream.
- Auto-collapse on completion — once all subagents finish, their subtask lists collapse, keeping the chat tidy.
Who it’s for
If you’re working on:
- User research / VOC analysis — open-ended responses, interview transcripts, user feedback at scale.
- Market / competitor research — many dimensions or many competitors scanned in parallel.
- Data analysis — the same dataset that needs to be split across several viewpoints simultaneously.
- Opinion monitoring — large volumes of cross-platform comments, sentiment, and topic clustering.
Hand the work to SubAgent and let a whole AI research team work in parallel — far more efficient than one model pulling an all-nighter over 100,000 rows.
How it relates to other capabilities
- Pairs with Brainstorming: use Brainstorming first to lock the research intent, then let SubAgent execute the analysis in parallel.
- Pairs with Skills Management: subagents still call the enabled official / custom Skills (Text Analysis, Data Analysis, Document Generation, etc.) while running — you control the boundary of what they can do via Skills Management.
Try it in the WeJot web appWeJot doesn’t just let AI handle your data — it makes multiple AIs work like a real research team: dividing labor, collaborating, cross-checking, and finishing the analysis together.