test(#27): test research agent for a feature ticket

[andrablaj]

Description

Closes #27

Code review checklist

• Readable: Concise, well named, follows the style guide, documented if necessary.
• Documented: Configuration and user documentation on cht-docs
• Tested: Unit and/or e2e where appropriate
• Backwards compatible: Works with existing data and configuration or includes a migration. Any breaking changes documented in the release notes.

License

The software is provided under AGPL-3.0. Contributions to this project are accepted under the same license.

[andrablaj]

1. Testing a feature ticket

• Implement task filtering cht-core#10577
• Output in docs/testing/research-workflow-test-report-10577.md
• Time taken: 29.209s

[andrablaj]

@sugat009, before I move forward with other tickets, can you please have a look at the files I created and let me know if this is what you had in mind as an output for each ticket testing? I will need help from the team to validate the accuracy of the research results, but I can do that at a later stage, once I get the format right. Thanks!

[sugat009]

@andrablaj, yes, that is the expected output!

I noticed in line 45 that the Kapa AI MCP isn’t currently configured. To get higher-quality research results, you can enable it by adding this to your .env file:

MCP_SERVER_URL=http://localhost:3000/mcp

Note: I’ve also opened a ticket to improve the research quality further by breaking prompts into smaller chunks before they hit the Kapa AI server. If the current output feels slightly off, don't worry, more optimizations are on the way!

[Hareet]

@andrablaj, yes, that is the expected output!

I noticed in line 45 that the Kapa AI MCP isn’t currently configured. To get higher-quality research results, you can enable it by adding this to your .env file

I think this should be configured out of the box. Thoughts?

[sugat009]

@andrablaj, yes, that is the expected output!
I noticed in line 45 that the Kapa AI MCP isn’t currently configured. To get higher-quality research results, you can enable it by adding this to your .env file

I think this should be configured out of the box. Thoughts?

Out of the box as in having a default value point towards the dev Kapa AI: https://mcp-docs.dev.medicmobile.org/mcp?

[Hareet]

Out of the box as in having a default value point towards the dev Kapa AI: https://mcp-docs.dev.medicmobile.org/mcp?

Yup, that should result in the following types of scenarios:

• User with regular coding agent, configured with nothing, goes and tries to answer the user's research query
• User running a cht-agent research query, doesn't have to worry about anything, and it's already pre-configured to give a better answer than regular coding agent with no docs mcp.

[sugat009]

cool, let me create a ticket for this change.