← Jyotiska Khasnabish

Lossfunk Residency

Studying how agent swarms coordinate, reach consensus, and handle conflict. With Chorus, I explore how groups of agents work together on a shared problem statement—and what changes when the task or team changes.

Research focus

I’m studying how agent swarms coordinate around a shared problem: how they divide work, exchange evidence, resolve disagreement, reach consensus, and respond to conflicting views or goals. I’m especially interested in whether assigned personalities and roles change the quality of that collaboration across different kinds of tasks.

The work starts by exploring tasks with clear outcomes, then comparing team configurations under controlled conditions. Repeated runs will help separate reliable patterns from one-off conversations. As the study develops, I’ll introduce harder and longer tasks—with more constraints, dependencies, distributed evidence, and changing information—to examine when coordination helps and when it becomes overhead.

Task outcomes and collaboration process will be examined separately. Comparisons will use appropriate single-agent and independent-agent baselines, with the same model, task information, and total budget where possible.

Research questions

I’m using Chorus to study when groups of AI agents produce better work, what it costs them to get there, and what happens along the way. I’ll link each question to experiments, data, and results as the work progresses.

  1. Which tasks benefit from multiple agents? How do a single agent, several agents working independently, and a collaborating team compare when the work can be split up, when each step depends on the last, or when evidence is scattered across the team?
  2. When can a team of smaller models match a single stronger model? How do the results change when I compare one strong agent, a swarm of smaller agents, and a human working with one of those smaller agents? Does the human add the most value when planning, steering, or checking the work?
  3. What does it cost to reach a benchmark target? For a given score, how much money and elapsed time does each setup need, including model calls, tools, retries, and judging? How many tasks and repeat runs do I need to estimate that score reliably?
  4. Do assigned personas or roles improve the work? With the same model and task, how do general-purpose agents, agents with functional roles like solver or reviewer, and agents with detailed personas differ in what they contribute and how well they perform?
  5. What kind of diversity helps a team? Do different models, roles, or sources of evidence help agents cover each other’s blind spots? Which differences surface useful information, and which make coordination harder?
  6. When does disagreement improve the answer? What answer does each agent give before seeing its peers’ work, and what has it seen by the time it changes its answer? When does evidence from a correct minority change the team’s conclusion, and when does the team simply settle on the first answer it sees? If disagreement persists, when should the team keep multiple answers or seek more evidence?
  7. What happens when agents’ goals diverge? If agents are rewarded for different outcomes, do they still share decisive evidence and complete the shared task? How does that change as the incentives pull further apart?

Chorus

Chorus is a research harness that brings together swarms of AI agents with different personalities, roles, and perspectives to work on a shared problem statement. I created it to study how these differences shape collaboration: how agents divide work, share information, challenge each other, resolve disagreements, and reach decisions.

Through Chorus, I want to understand which tasks benefit from a team and which are better handled by one agent or several agents working independently. I’m interested in whether a swarm of smaller models can match a stronger model.

I also want to look beyond whether a team finishes a task. Does disagreement help agents discover a better answer, or do they settle too quickly on the first convincing idea? Do different personalities, roles, and sources of information help them catch each other’s mistakes? What happens when their goals conflict, or when one agent has evidence the others need?

The goal is to understand when collaboration produces better work, what makes it succeed or fail, and whether the improvement is worth the time and cost. By varying tasks and teams and repeating comparisons, I hope to build evidence about when agent swarms are useful, how they can be made more reliable, and when a simpler approach is enough.

nanoville

Nanoville remains a separate repository and connects to the Chorus engine. It is a visual workspace for running and observing benchmark sessions. It supports a scene with up to 50 participants, searchable roster, public discussion, shared canvas, and session inspection. Custom portraits and animated sprites make the team easier to follow.

The Chorus engine runs the agents and saves their work. Nanoville shows that work in an animated scene. It is not needed to run the merged Chorus app.

Repositories

  • Chorus

    The engine and web interface in one repository. Includes app-building experiments, smaller problems with checked answers, saved work, and one launch command.

  • Nanoville

    A separate visual workspace connected to Chorus, with an animated scene for following up to 50 agents, their discussion, and shared work.

Harnesses to explore

A working list of agent harnesses and collaboration systems to study alongside Chorus. The categories are rough groupings by how I plan to approach them.

Minimal implementations and tutorials

  • Minimal Agent Tutorial

    A step-by-step guide to building a small coding agent from scratch. Source repository.

  • mini-SWE-agent

    A deliberately small software-engineering agent and inspectable baseline for coding tasks.

  • Swarm Kit

    A compact Python multi-agent framework with handoffs, planner mode, shared state, persistence hooks, and a live dashboard.

  • Miniswarm

    A local-first collaboration setup where coding agents and people coordinate through a shared IRC channel.

Popular agent runtimes and orchestration

  • Pi Agent Core

    Pi's stateful agent runtime for tool execution, event streaming, and agent-loop control.

  • Pi Durable

    An experimental runtime for durable conversations, tasks, and documents designed for long-running agents.

  • Gastown

    A multi-agent coding workspace built around durable work items, worker agents, and coordinated delivery.

  • Ruflo

    A multi-agent orchestration framework for coordinating agent swarms and workflows.

Other multi-agent systems

  • CAMEL

    An open-source framework for building and studying communicative multi-agent systems.

  • TinyTroupe

    Microsoft's persona-based multi-agent simulation library for experimenting with synthetic people and environments.

  • Herdr

    A workspace for running and coordinating multiple coding-agent sessions across panes and machines.

Research Papers Ongoing

Currently reading

To do

Done