Skip to content

feat(provider): IBM bob provider support added#243

Closed
SunithaGudisagarIBM1 wants to merge 1 commit into
getagentseal:mainfrom
SunithaGudisagarIBM1:ibm-bob-provider-supported
Closed

feat(provider): IBM bob provider support added#243
SunithaGudisagarIBM1 wants to merge 1 commit into
getagentseal:mainfrom
SunithaGudisagarIBM1:ibm-bob-provider-supported

Conversation

@SunithaGudisagarIBM1
Copy link
Copy Markdown

@SunithaGudisagarIBM1 SunithaGudisagarIBM1 commented May 6, 2026

@SunithaGudisagarIBM1
Copy link
Copy Markdown
Author

@iamtoruk can you take a look at this PR

@iamtoruk iamtoruk self-requested a review May 11, 2026 16:58
@SunithaGudisagarIBM1
Copy link
Copy Markdown
Author

SunithaGudisagarIBM1 commented May 12, 2026

Hi @ozymandiashh,
I have already implemented the issue #248 in this PR,
Can you please take this PR as i came with the issue and the implementation as well.
@iamtoruk @ozymandiashh I am interested to contribute to this open-source project, please consider this PR for merging.
Thank you

@AgentSeal AgentSeal added the needs-validation PR requires validation against real-world usage before review label May 12, 2026
@AgentSeal
Copy link
Copy Markdown
Collaborator

Thanks for working on this, and for opening the original issue requesting Bob support.

We've been reviewing both this PR and #303 against a real IBM Bob install. A few issues that make this one hard to merge as-is:

  • Merge conflicts with current main (provider registry, README, and other files have changed significantly since this branch was created).
  • Model fallback lands on cline-auto which is misleading for Bob users -- Bob deliberately hides its model name, so the fallback should be Bob-specific (e.g. ibm-bob-auto), not the generic Cline label.
  • Test fixtures fabricate model tags (claude-sonnet-4-6 in api_conversation_history.json) that don't exist in real Bob installs. The real-world case is always no model tag, and that path isn't tested.

PR #303 addresses these points and is closer to merge-ready, so we're going to move forward with that one after validating it against real data.

Appreciate you opening the issue and the implementation effort -- the discovery paths and shared parser reuse in your PR were solid.

@AgentSeal AgentSeal closed this May 12, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

needs-validation PR requires validation against real-world usage before review

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants