LATESTv0.25.2Oct 2, 2026
DownloadSessions move on before they fill up, and a request can start from a GitHub or GitLab issue
- · A smart-routing session no longer grows until the engine refuses it. Each session card shows how full its context window is, and once a session passes half of it, the next request on that topic starts a fresh session that is handed the last result and the files it touched. Codex windows are smaller than Claude's, so Codex sessions move on sooner.
- · A session that overflows anyway, with Claude's "Prompt is too long", continues on a fresh session inside the same run. Before, the run was retried on the same full session, refused again, and the project was left stuck with the request unserved. A request too big even for a fresh session stops after one more try and says to split it or attach fewer or smaller images.
- · The run card says why a run started a fresh session, and in the desktop app the running session's context reading updates every few seconds. The token total on the session card counts every re-read of the conversation, so it stays separate from how full the session is.
- · In the desktop app, a request can start from an open issue. The request composer and a team workspace's new request form list the repository's 30 most recently updated open GitHub or GitLab issues, read through your signed-in gh or glab. Picking one adds its number, title, link and text to the draft. Nothing is sent and the issue is not changed. Pull requests and confidential GitLab issues are left out.