mirror of
https://github.com/rowboatlabs/rowboat.git
synced 2026-05-13 17:22:37 +02:00
Revert "Refactor project templates to remove the Example Agent and update related documentation. Updated the copilot behaviour aswell." (#236)
This reverts commit bbd5b7aa5d.
This commit is contained in:
parent
04c505979f
commit
1ebe58c499
3 changed files with 23 additions and 10 deletions
|
|
@ -7,7 +7,7 @@ The design of the multi-agent system is represented by the following JSON schema
|
|||
{workflow_schema}
|
||||
\`\`\`
|
||||
|
||||
If the workflow has no agents or an empty startAgent, it means the user is yet to create their first agent. You should treat the user's first request as a request to plan out and create the multi-agent system.
|
||||
If the workflow has an 'Example Agent' as the main agent, it means the user is yet to create the main agent. You should treat the user's first request as a request to plan out and create the multi-agent system.
|
||||
|
||||
---
|
||||
`;
|
||||
|
|
@ -116,14 +116,14 @@ I'll add the suggested tools for Google Calendar, web search, and email:
|
|||
### 2. Create Agents
|
||||
|
||||
#### a. Hub Agent (Meeting Assistant Hub)
|
||||
I'll create the hub agent:
|
||||
I'll edit the Example Agent to become the hub agent:
|
||||
|
||||
\`\`\`copilot_change
|
||||
// action: edit
|
||||
// config_type: agent
|
||||
// name: Meeting Assistant Hub
|
||||
// name: Example Agent
|
||||
{
|
||||
"change_description": "Created the main hub agent orchestrating the meeting summary workflow.",
|
||||
"change_description": "Transformed Example Agent into the main hub agent orchestrating the meeting summary workflow.",
|
||||
"config_changes": {
|
||||
"name": "Meeting Assistant Hub",
|
||||
"type": "conversation",
|
||||
|
|
@ -241,7 +241,7 @@ searchRelevantTools output:
|
|||
I'll make the following changes to your workflow:
|
||||
|
||||
1. Add the "Get document by id" tool for retrieving the content of a Google Doc.
|
||||
2. Create a single user-facing agent that:
|
||||
2. Replace the Example Agent with a single user-facing agent that:
|
||||
* Asks the user for the Google Doc ID and their question.
|
||||
* Uses the tool to fetch the document content.
|
||||
* Answers the user's question based only on the content of the fetched Google Doc (no RAG or external search).
|
||||
|
|
@ -277,14 +277,14 @@ I'm adding the "Get document by id" tool to fetch the content of a Google Doc by
|
|||
}
|
||||
\`\`\`
|
||||
|
||||
I'm creating a user-facing agent that fetches a Google Doc by ID and answers questions based on its content:
|
||||
I'm replacing the Example Agent with a user-facing agent that fetches a Google Doc by ID and answers questions based on its content:
|
||||
|
||||
\`\`\`copilot_change
|
||||
// action: edit
|
||||
// config_type: agent
|
||||
// name: Meeting Assistant Hub
|
||||
// name: Example Agent
|
||||
{
|
||||
"change_description": "Created a user-facing agent that fetches a Google Doc by ID and answers user questions based only on its content.",
|
||||
"change_description": "Replaced Example Agent with a user-facing agent that fetches a Google Doc by ID and answers user questions based only on its content.",
|
||||
"config_changes": {
|
||||
"name": "Google Doc QnA Assistant",
|
||||
"type": "conversation",
|
||||
|
|
|
|||
Loading…
Add table
Add a link
Reference in a new issue