Skip to content

Document agent participants.#1012

Merged
mkbehr merged 2 commits intoPAIR-code:mainfrom
mkbehr:agent-participant-docs
Feb 27, 2026
Merged

Document agent participants.#1012
mkbehr merged 2 commits intoPAIR-code:mainfrom
mkbehr:agent-participant-docs

Conversation

@mkbehr
Copy link
Collaborator

@mkbehr mkbehr commented Feb 13, 2026

Description

Add a documentation page describing agent participants.


Verification

n/a


Related issues

n/a


@mkbehr mkbehr requested a review from vivtsai February 13, 2026 22:03

## Preparing an Experiment for Agent Participants

You can add agent participants to any experiment, as long as you have a Google
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Google API key?

Copy link
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yeah, the UI only supports Gemini for these right now. Updated the doc to clarify.

Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I had initially meant it as "it's called the Gemini API not the Google API" -- but I didn't know the particpant one was limited! Split them out to a shared component here: #1033

personalities or instructions to different agents. These settings will apply for
that agent across all experiment stages.

## Supported Stages
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

AssetAllocation, StockInfo also supported. A link to where the stage-specific prompt context is built would be nice so that people can see exactly what the agent will see.

Copy link
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Added those two.

Piecing together the prompt from the code takes some jumping around, but I added a link to our other documentation on the implementation. I do think a better way to see what the agent will see is to run a test experiment and check the logs, so you can see exactly what gets sent to the agent.

Copy link
Collaborator

@rasmi rasmi left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

A few suggestions!

Copy link
Collaborator

@rasmi rasmi left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

A few suggestions!

Copy link
Collaborator

@rasmi rasmi left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

A few clarifications!

@mkbehr mkbehr merged commit f281aa7 into PAIR-code:main Feb 27, 2026
5 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants