This is an issue to find out if there is still life in this repo

[klausnitsche]

Activity here has dropped to zero.
Some issues have been fixed but the fixes were never released.
These issues have prevented me from using KinBot for one and a half weeks now. My instance is completely broken.
I am happy to support Kinbot's development further, but I also have to know if it's worth the time.

[MarlBurroW]

Hi @klausnitsche — thanks for reaching out, and sorry to hear your instance is down. That's a terrible experience and you deserve an answer.

Yes, KinBot is alive. Here's what's been happening:

Recent activity

The repo has been very active over the past 10 days:

• v0.35.0 released on April 8 (token usage transparency, task panel fixes, abort handling)
• Fixes pushed April 9–11: tool cap provider-awareness (Tool dropping affects Anthropic provider and drops critical tools incl. MCP #354), sanitize persisted tool calls to fix permanently broken sessions (Session permanently broken after tool dropping: "Invalid prompt: ModelMessage[] schema" #355), typecheck fixes
• Multiple issues triaged and labeled daily

The release gap you're hitting

You're right — fixes merged after April 8 (especially #354 and #355) haven't been tagged as a release yet. If your instance is broken due to the Invalid prompt: The messages do not match the ModelMessage[] schema error or the write_file has no execute function error, those fixes are in main but not in a Docker image tag.

Immediate workaround: You can pull the ghcr.io/marlburrow/kinbot:main tag (or ghcr.io/marlburrow/kinbot:latest if it tracks main) to get the unreleased fixes right now.

Looking at your open issues

• write_file tool broken in v0.35.0: 'Tool write_file has no execute function' #351 (write_file broken) — likely fixed by the tool cap changes in Tool dropping affects Anthropic provider and drops critical tools incl. MCP #354. Can you confirm if pulling the latest image resolves it?
• http_request blocks private LAN/Tailnet access in self-hosted setups – breaks autonomy use cases #352 (private IP blocking for http_request) — this is a valid enhancement request, not yet implemented. The SSRF protection is intentional, but making it configurable for self-hosted setups is on the radar.
• Compaction leads to loss of current context in some cases #315 (compaction context loss) — tagged needs-discussion, still being investigated.

What's next

A new release with the post-v0.35.0 fixes should be coming soon. In the meantime, the main branch is stable and deployable.

Your investment in KinBot is appreciated — you've filed some of the most detailed and actionable issues in the repo. We're here. 🤝

[klausnitsche]

Trying to pull the main branch ("latest" is in the same state as v0.35.0 so it is of no use):

Pulling image: ghcr.io/marlburrow/kinbot:main
Error response from daemon: manifest unknown

Boom.