Avoid structural dependency on LLM APIs
@shivashanmugam is already working on this.
Since Oct 14, 2025.
Assessment
This issue has not been assessed yet.
Description
The current implementation of src/microbots/llm/openai_api.py is heavily depending on the response structure of the LLM. It expects the LLM's response to be always in llm_output_format. This adds an additional overhead for the custom-bots which need to extend the current system-prompt including the specific llm_output_format.
We should converge with OpenAI API's original structure. The LLM function-call should be in dedicated LLM's function-call key instead of forcing the LLM to provide it's NL output in JSON everytime.
- Dominant language
- Python
- Stars
- 38
- Forks
- 21
- Avg merge
- 4d 3h
- Merged PRs (30d)
- 2
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from microsoft/microbots
-
Difficulty 3/5 1-2 days Newbie friendliness 30/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 55/100
-
enhancement
Difficulty 3/5 1-2 days Newbie friendliness 20/100
-
enhancement
All issues in microsoft/microbots
Similar issues
-
agent-ready documentation needs-triage
Difficulty 1/5 1-3 hours Newbie friendliness 88/100
-
documentation
Difficulty 1/5 Under an hour Newbie friendliness 91/100
-
workflow-status page template still says reusable workflows are "triggered only by workflow_call:" Open
Difficulty 1/5 Under an hour Newbie friendliness 92/100
-
instance instance add
Difficulty 1/5 Under an hour Newbie friendliness 72/100
searxng/searx-instances#939 · 1 comment ·
-
area-deployment area-integrations triage:bot-seen
Difficulty 2/5 Half a day Newbie friendliness 86/100