Cannot bump claude sdk to 2.1.251 to support Fable

Closed

#6,855 opened on Sep 15, 2026 3 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty: 4/5
Estimated time: 3-5 days
Newbie friendliness: 45/100

Issue type: Bug
Clarity: Mostly clear
Activity status: Active
Tech stack: python
Domain: build-system, devtools

Research direction

Start with the uv lock resolution and the conflicting claude-agent-sdk constraints for hackbot-agent-bug-fix and hackbot-agent-test-repair. Trace how the runtime API and workspace dependencies are defined, then determine whether separate agent lock files are needed. Done means the workspace resolves successfully while allowing the test-repair agent to use SDK 2.1.251 or newer without capping other agents.

Written by the indexing model from the issue text.

Description

hackbot

hackbot_runtime.errors.AgentError: analysis stage failed: API Error: 400 Claude Code 2.1.191 does not support this model; version 2.1.251 or newer is required. Run 'claude update', or update the Claude desktop app, then try again.

uv lock
  × No solution found when resolving dependencies for split (markers: python_full_version >= '3.14' and sys_platform == 'win32'):
  ╰─▶ Because hackbot-agent-bug-fix depends on claude-agent-sdk>=0.1.30,<=0.2.110 and hackbot-agent-test-repair depends on claude-agent-sdk>=2.1.251, we can conclude that hackbot-agent-test-repair and
      hackbot-agent-bug-fix[dev] are incompatible.
      And because your workspace requires hackbot-agent-bug-fix[dev] and hackbot-agent-test-repair, we can conclude that your workspace's requirements are unsatisfiable.

      hint: While the active Python version is 3.13, the resolution failed for other Python versions supported by your project. Consider limiting your project's supported Python versions using
      `requires-python`.

@suhaibmujahid would it make sense for each agent to have its own lock file? There might be some issues with using the runtime API in this case. Capping the SDK for everyone is definintely not a solution. We should aim at always using the latest harness.

Dominant language: Python
Stars: 570
Forks: 351
Avg merge: 2d 3h
Merged PRs (30d): 69

Contributor guide

Open the contributing 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.

Similar issues

Exercise the latest Claude Code release in CI instead of a pinned version Open

Difficulty 2/5 1-3 hours Newbie friendliness 74/100

ogx-ai/ogx#6659 · Opened Sep 25, 2026
A cancelled SSE stream deletes the whole session's message queue, so the next stream 404s (503 behind a proxy) Open

Difficulty 2/5 1-3 hours Newbie friendliness 84/100

gradio-app/gradio#13895 · Opened Sep 25, 2026
Installation issue: spdk +pmdk (missing pmdk dependency) Open

build-error

Difficulty 2/5 1-3 hours Newbie friendliness 76/100

spack/spack-packages#6713 · Opened Sep 25, 2026
Use issue templates Open

Difficulty 2/5 1-3 hours Newbie friendliness 72/100

ActivityWatch/activitywatch#1464 · 1 reaction · Opened Sep 25, 2026
[Bug]: The ckg tool drops the return type of every decorated Python method in class search results Open

Difficulty 2/5 1-3 hours Newbie friendliness 78/100

bytedance/trae-agent#483 · Opened Sep 25, 2026

More Python issues