Example rule:
When the user asks for X, follow this agentic protocol to better understand how to provide a meaningful answer:
1) read file @file_1.md
2) read file @file_2.md
3) read file @file_3.md
4) read file @file_4.md
5) read file @file_5.md
After you followed all 5 steps, continue with generating a meaningful answer based on what you learned.
Example input to Composer in Agent mode:
how can I do X?
Example output:
- Let me analyze the requirements and read through the necessary documentation
- read file @file_1.md
- read file @file_2.md
- read file @file_3.md
- Based on the documentation and requirements, here is how you can do X:
- ...
As you can see, the agent correctly understood it has to read the provided files, but it read only the first three, omitting the last two.
- Is there a way we can get more control over the agent (including adjusting props like temperature and output tokens limit)?
- Or be able to implement our own agents? Usually a ReAct agent would’ve followed all the instructions from the rules. Suggests that your agent is limited by:
- output tokens config (currently cannot be changed by the user),
- or by some internal prompts,
- or by the actual agent implementation.
- As part of your internal tests, have you implemented “evals” to test the agent in different scenarios ? In this case, the eval would’ve failed as it didn’t correctly follow the instructions.
Using Cursor Business + claude-3.5-sonnet.