Repository navigation
Releases: vrajpal-jhala/langgraph-harness
Releases · vrajpal-jhala/langgraph-harness
Release list
v0.4.3
Fixes
- Chat's GitLab tools always reported that no GitLab account was linked — turning on GitLab tools in a chat failed with "GitLab tools enabled but no linked GitLab token", even for users signed in with GitLab. Chat now retrieves the linked GitLab token correctly, so the tools work again.
v0.4.2
Fixes
- The backend refused to start unless both Gemini and Groq API keys were set — when Gemini and Groq support was added, their keys were left out of the optional list in the startup check, so it demanded them even when you only use one LLM provider. They're now optional, like the other provider keys.
v0.4.1
Fixes
- A repository search for several alternatives at once found nothing — the review agent's repo search treated
|,+,?and parentheses as plain characters, so a pattern likefoo|barsilently returned no matches. Searches now understand these as regular-expression syntax; searches explicitly marked as literal text are unaffected. - Icons in the run timeline could get squashed — the icon beside a tool call or retry row shrank when the row's text was long. It now keeps its size.
v0.4.0
Features
- The run timeline now shows how long each "Thinking" step took — previously there was no way to tell how much time the model spent reasoning before acting, for either the main agent or a per-file review sub-agent. Each reasoning step now shows a live-ticking counter while it's still thinking, and its final duration once it's done.
- Two new free LLM providers for MR review — reviews can now run on Google's Gemini or Groq's free-tier models, in addition to OpenRouter, Ollama, and sglang. This option is for MR review only; Chat doesn't support these providers yet.
Fixes
- Fetching a web page during a review always failed with an unhelpful error — a configuration issue in Lightpanda, the headless browser langgraph-harness uses to fetch pages, made every fetch fail immediately without a real explanation. Fetching now works, and any future failure will show what actually went wrong.
- A model stuck repeating itself while reasoning never triggered the safeguard that stops runaway runs — that safeguard only checked the model's visible answer, so a model looping purely inside its own reasoning (before writing anything visible) could run unbounded instead of being caught, whether in the main agent or a review sub-agent. It now checks the model's reasoning too.
- An empty box could appear under a "Thinking" step with nothing in it — a turn that produced only blank lines around a tool call still rendered its (invisible) content as a box, most noticeably on a review sub-agent's own turns. Blank turns no longer render anything.
- The context-usage number next to a step could show a confusing negative value — it was computed from a number that also swings with how much the model reasoned on that particular step, rather than from how much the conversation itself actually grew. It's now based on the latter, so the number reliably increases as a review progresses.
- The loading indicator kept spinning in a finished sub-agent's view — it tracked whether the review as a whole was still running rather than whether that specific sub-agent had finished, so its transcript looked like it was still working long after it had returned its findings.