Skip to content

Releases

v0.3.2

Choose a tag to compare

@NamerekWASD NamerekWASD released this 17 Nov 23:00

A patch of 0.3: a permission question that no longer vanishes, and the README badge during a fix of the main branch or a release carry.

Changed

  • Chain sessions run on Copilot CLI 1.0.113, the version this release was checked against; Claude Code 2.1.326, codex-cli 0.169.0 and OpenCode 1.19.6 stay.

Fixed

  • A permission question of a Claude session through the SDK no longer disappears when the CLI stops waiting for your answer. The CLI's built-in check of dangerous deletions waits two minutes and then refuses the call itself; before, the question simply vanished and there was nowhere to answer. The chat now marks the call "approval expired, not run" and adds a closing line, and the tracker gets a comment saying that the question expired.
  • The README badge of a fix of the main branch or a release carry:
    • The milestone card stays on the badge while the fix or carry runs. It shows the milestone of the chain's next task, or of the task closed last if no task is next.
    • The run gets a title of its own. A fix names the project's main branch, such as "Fixing the red main"; a carry names the release and the branch it goes into, such as "Carrying release v0.3 into dev".
    • On a task with no title, the agent line stays on the line with the task's key. Before, it sat out of line under an empty title.
  • In the chat's question card, the layout no longer jumps between two columns and one when the pointer moves onto an option without a preview: the preview column stays and says "No preview for this option". Deny of a permission now previews the same call as Allow.
  • /stats prices gpt-6.2-astra and gpt-6.2-sol at their own prices, taken from OpenAI's model pages. A prompt over 272k tokens gets the long-prompt price.

v0.3.1

Choose a tag to compare

@NamerekWASD NamerekWASD released this 17 Nov 15:15

A patch of 0.3: the CI and limit fixes that cost a chain time, and a clearer carry panel.

Added

  • What a waiting carry brings. The panel of a carry waiting for its turn shows the number of commits, the conflicted files with the conflict lines of each, and Skip.
  • Update all in the package catalog, to the right of Check all.

Fixed

  • One CI poll that gets no answer no longer leaves the pushed commit unchecked. Before, a single timed-out poll during a run dropped the commit, so a red main was never fixed. The push is now watched for up to an hour, and the CI's later result decides it: red means a rerun and then a fix session, green means it passed. Meanwhile the CI panel says the CI did not answer.
  • A Claude chain on a subscription no longer treats a session's cache as warm for an hour when the session writes the five-minute cache.
  • When a limit resets early, a task no longer stays held by "paid usage possible, not confirmed" until the announced reset with usage at 0%.
  • More limits are read correctly:
    • Claude's limit windows come from the CLI's usage report, so reading an Ultra account without a five-hour limit no longer depends on how the CLI words its lines.
    • A ChatGPT seat in a workspace (Team, Business, Edu) gets its spending cap and monthly credits read.
    • Copilot no longer shows "unlimited" for a Business seat whose allowance is used up.
  • Copilot: a turn that fails on "Failed to load models" shows the error instead of waiting for an answer.
  • OpenCode: a permission request refused by the task's rules, such as reading .env, no longer ends the turn silently and leaves the session waiting with no question.
  • The launch card shown when a session continues after a limit no longer says that the old session stops and a new one starts with a handoff, since the same session continues.
  • A private repository on a free GitHub plan no longer shows "Could not verify protection" after every launch, since its branch cannot be protected.
  • A pause on a refused pull request description no longer tells you to press Resume. The pull request opens by itself from the session's next mark.
  • The GitLab profile form no longer requires a server address for GitLab.com, where the hint says to leave it empty.
  • "What sessions get" reads .claude/settings.json from the project's branch, not from the main checkout's disk.
  • The changelog window:
    • For a released milestone, it shows the released section of the file instead of an old draft under [Unreleased].
    • On an account whose limit is spent, it shows a clear notice instead of the CLI's raw JSON answer.
  • A carry waiting for its turn no longer shows the session of an earlier carry with the same name.
  • A row's Install or Update button in the package catalog no longer stays stuck after the action.
  • On a phone, a long question in the chat window no longer covers the answer options, and the question switcher no longer wraps around the text.
  • The demo:
    • The session window opened from the task's sessions finds its transcript, and the card of a finished task shows what the session did.
    • The answer to DEMO-3's question appears above the TASK DONE line and is still there when the chat is opened again.
    • Without git, "The demo is over" no longer says the branches were merged into the main one.

v0.3.0

Choose a tag to compare

@NamerekWASD NamerekWASD released this 16 Nov 02:10

0.3 needs neither a tracker account nor git to start: a built-in tracker, projects without git, a demo on the first start and a project wizard that clones or creates the repository. Sessions get Even Keel's own tasks server for every tracker, Forgejo issues join the trackers, Claude Code runs on Amazon Bedrock, Google Vertex AI and Microsoft Foundry, and OpenCode on an OpenRouter key. The page gains an event log, a chat window per task and a README badge of the chain.

Added

  • A built-in tracker. Tasks are kept in Even Keel's own database, with no account or token; it is the first choice of the tracker in the setup and the project wizard. A task's card edits it in place: title, description (a Preview and a Markdown editor), status, labels, milestone, links, parent and subtasks, deletion. An edit is saved when you leave the field and kept as a browser draft until it lands; an edit that crossed another opens a window with the difference. Screenshots and files pasted or dropped into a description become attachments the session gets. The card's journal keeps the agents' reports with their model, the sessions' questions, your answers and your notes. A ghost row at the end of each chain group and on top of the backlog adds a task.
  • Moving a built-in project to a real tracker. Move to another tracker in the project's Tracker settings says what the tracker cannot hold, copies the open tasks with their statuses, parents, links, attachments and journal, and goes on after a refusal or a restart. Switch then moves the project there in the same chain order; the old tasks are marked with the key they moved to, and /stats counts their sessions under the new keys.
  • Projects without git. A project can be a plain folder: its tasks share it, write their files there and close when the session ends its answer with the TASK DONE mark. Sessions are refused git there, each task gets its own handoff note, and a session still idle in the folder is stopped before the next task starts. The setup's Git step first asks Use git?, and the answer is the default of new projects. Turn on git on the Repository tab makes the folder a repository with the work so far in its first commit; a folder that became a repository by itself gets a band offering it.
  • A demo on the first start. With no project yet, Watch the demo takes a small project on the built-in tracker through three tasks in about two minutes: one waits for another, one asks you a question in the chat. The agent is a script, so no account is used and nothing is spent. It runs with or without git, as the setup's Git step answered and git is there, and stays out of the statistics; the project wizard's Remove the demo removes it once your project is added.
  • The project wizard clones or creates the repository. One field, Folder or repository address, takes an address to clone (the remote is asked at once and its branches are offered), a checkout already on the machine, a folder without git to make a repository of, a path that is not there yet, or a bare name for a new folder in Even Keel's projects folder. Add project opens a window with each step's progress: the clone with its percent and Git LFS files, the first commit, the project, Claude Code's trust and the packages, with Retry and with Cancel, which removes only what Even Keel made. A refused sign-in, an unknown SSH host key or a cut network is one line saying what to do; a missing name and e-mail for commits gets Set them, which asks for both over the page.
  • Even Keel's own tasks server (tasks@even-keel) for every tracker: Huly, GitHub, Linear, Jira, GitLab, Forgejo, the built-in one and a project's feeds. Its five tools read and write tasks with links, parents, labels, milestones, estimates, components and attachments; nothing can be deleted through them. task_read downloads a task's files into .temp/task-files, task_update changes several tasks in one call, and a create cut off by a crash is found again by its marker instead of filed twice. A project you add gets the package on; the page warns when the tracker's own MCP server is on beside it. A session you start by hand gets the same tools through the tasks plugin.
  • Forgejo, Gitea and Codeberg issues as a tracker, with the forgejo plugin and its forgejo:task skill: labels, milestones and blocking links come from the repository. On an organization's repository a token without read:organization still reads the tasks, and the project page says what sessions lose and which scope to add; a token without the issue scope is named as such, not as revoked.
  • Claude Code on Amazon Bedrock, Google Vertex AI and Microsoft Foundry. Add account → Cloud takes the cloud's credentials (a profile, a key, or the environment of the user Even Keel runs as); the account runs through the Agent SDK and shows its spend and region.
  • OpenCode on an OpenRouter key, with any of OpenRouter's models in a task's run. The account row shows the key's real spend, what is left of the key's own limit and the account's balance; /stats counts a session's real spend, with the estimate by price in a tip.
  • More limits are read: OpenCode Go's subscription limits and Copilot's AI credits on their account rows, and a model's own week (Fable on Max, Ultra and Team) beside the account's. When that week is spent, the next task on its model waits for it to open while a task on another model goes on.
  • The event log, Log in the header: launches, stops, settings changes, questions, limits, a red main, carry conflicts, a paused chain, package problems and moves between trackers, kept for 3000 entries and filtered by level, category and project. A new event shows as a toast for 12 seconds in sight, with a bar of the time left and a pause under the pointer, and the header counts the unread ones.
  • A chat window per task. It has the task's head, a status line with the context ring and the model and effort of the last answer, a slash button and a panel with the description, attachments and comments; it outlives a handoff and Done and keeps a draft per task. Accept as answer closes a task with its session's last message. A reply to a session whose cache went cold first asks whether to start a new session with it, send it anyway or cancel. A session whose turn has ended while its background command runs says so instead of "working".
  • A README badge of a project's chain: an SVG of what runs, what is done and the milestone's progress, pushed to a Cloudflare Worker you deploy from the even-keel-badge package. The project's README badge dialog sets it up with a preview and a still PNG for sites that take no SVG. Task titles pass a filter of private data and can be translated into English through your LiteLLM endpoint, and sessions give the badge a short status line.
  • The CI panel by push: a row per workflow with its median time, history by push, each run's event and who pushed, a busy runner, and what the chain waits for. A red main gets one automatic rerun of its failed jobs before a fix session (ci.rerunFailed, on by default), and a run failed only because no runner took its jobs leaves the commit unchecked, not red.
  • Milestone order by hand in a project's tracker window. Without one, milestones go by the tracker's own position, then date, then version, and Jira's versions by release date, as on its Releases page.
  • An automatic copy of the state database, daily and before every schema step. Each copy is checked by a trial restore and includes the attachments; the newest 14 are kept (Settings → Backups, backup.dir, backup.keep).
  • Hotkeys: Ctrl+Enter runs the chain, a double click opens a card, and the Hotkeys window in the gear menu changes them.
  • Codex and OpenCode get an auto-compaction window of their own, set in the Agent card.
  • The backlog panel searches its tasks, shows them 50 at a time with each task's run beside its key, and orders them newest first, oldest first or by priority. The project feed has a parents view, and a task's card lists a parent's subtasks on any tracker and the replies of a comment's thread.
  • Notices take Got it and Don't show again; Settings → Notices turns back on what was turned off.
  • A Claude setting changed right in an account folder's settings.json is kept: a band asks whether to make it shared, keep it for that account only or discard it.
  • The ⋯ menu of an account row offers Replace key for a working key too.
  • even-keel install, even-keel update and the first install from npx print the page's address once the page answers, taken from EVEN_KEEL_HOST/EVEN_KEEL_PORT of the environment and the data folder's .env. If the page has not answered after 30 s, they say where the log is instead. The first install from npx then opens the page in the browser. On Linux it does that only on a desktop with a display, never over SSH.

Changed

  • What a task runs on is set on its card, not by a tracker label. A task's run — provider, model and effort — is kept by Even Keel: the card's Runs on picks it, and a session can set it through the tasks server's run field of tasks_create and task_update. The effort is new: Claude Code's low to max, Codex's minimal to xhigh, OpenCode's variant and Copilot's reasoning effort; empty passes none. Labels <Provider> | <model> are no longer read. The update moves the run label of each open task into its run once, in the projects that had run labels on; the labels stay in the tracker. The setting modelLabels is removed.
  • OpenCode keeps a model for each provider it signs in to. Switching OpenCode's account to one on another sign-in (ChatGPT, an Anthropic key, OpenRouter, Copilot, Go, the free models) and back no longer loses the model you set: the model field shows the one of the account's sign-in and says which it is, in th...
Read more

v0.2.4

Choose a tag to compare

@NamerekWASD NamerekWASD released this 11 Nov 00:37

Fixed

  • A project without a counted CI no longer takes main for green when the session merged without running its check. Main counts as green only when the check hook reports it passed on the merged tree (checkpoint plugin 0.14.1). A merge without that report, made by a session without the checkpoint package for one, is checked in the next task's folder before that task starts.

v0.2.3

Choose a tag to compare

@NamerekWASD NamerekWASD released this 07 Nov 09:20

Fixed

  • The GitLab plugin's gitlab:task skill loads again: its description is quoted, so the skill's frontmatter parses and chain sessions on GitLab projects get the skill (plugin 0.1.3).
  • Right after a service restart a Claude chain no longer pauses on agents --json --all timed out. The session listing the chain waits on goes ahead of the account's other short calls and is tried again for up to five minutes.
  • A cleanup after Done whose session stop timed out the same way tries the stop again and then removes the task's worktree folder, instead of warning that the session and the folder were left behind.

v0.2.2

Choose a tag to compare

@NamerekWASD NamerekWASD released this 06 Nov 14:08

Added

  • A done task's time is written to GitLab and Jira as it is to Huly. Sometimes Jira refuses the worklog for a reason that is not about a field, for example when the project does not take time. That is now read as a refusal by the project.

Changed

  • Claude folder trust is written by Even Keel before every background session, with the project's consent in the wizard, instead of a switch and a command to run by hand. If the write or the CLI still refuses, the pause shows one command to run, for the right CLI, account folder and user. On Windows under a service account it shows a runas line with a ready script.
  • Checked CLI versions: Claude Code 2.1.319, codex-cli 0.167.0, OpenCode 1.19.5 and Copilot CLI 1.0.106.
  • Pull request mode is no longer marked experimental.
  • Setting up the Claude plugin marketplace by hand has moved to Accounts.

Fixed

  • Claude trust is written under the path the CLI checks. That is a forward-slash key on Windows and the real path of a symlinked folder or a Windows junction, so such folders no longer pause on "Workspace not trusted". The write keeps the account's .claude.json permissions (600 stays 600).
  • Copilot: sign-in is checked in the session's own account folder, an unknown sign-in is shown as unknown, and a terminal login's token is kept apart from the accounts' own. Protection also catches a Copilot force push to the main branch written as a refspec.
  • A fix session that finds nothing to fix ends with NO CHANGES.
  • A chat reply sent to a session no longer repeats the session's instructions.
  • Windows: environment variables such as %USERPROFILE% in a project's folder are expanded.
  • Windows: uninstalling and installing over a running tray host no longer fails while the quitting host still holds its exe.
  • Session account pills show the account of the session's own agent.
  • New rows in settings tables are kept when switching tabs.
  • Tips close when the page scrolls or the window is resized.
  • The answer card's caret points at the question's first line.
  • Download size estimates of the checked CLI copies are up to date.

v0.2.1

Choose a tag to compare

@NamerekWASD NamerekWASD released this 04 Nov 13:37

Fixed

  • Windows: git or an agent CLI installed while Even Keel runs is found after Restart in the tray, instead of only after a reboot: the tray host and the Windows service start Even Keel with the system and user PATH read anew.
  • The setup's Git step offers the install command of the package manager the machine has (winget, brew, apt and the like) and always the download link from git-scm.com, the link alone where none is found, instead of a winget command on a Windows without winget. On Windows it says what makes Even Keel see a git installed since, by how it was started: Restart in the tray, a restart of the Windows service, or a start from a new terminal.
  • Windows: the README and the guide say to run npx even-keel and even-keel from cmd, or as npx.cmd/even-keel.cmd in PowerShell, whose default policy blocks npm's .ps1 shims; the trust warning in the project wizard and the project's settings says to run its command in cmd.
  • The guide says to run npx even-keel from any folder but a clone of Even Keel, where npx looks for the package in the clone itself.
  • A very long line in an OpenCode account log no longer stalls Even Keel for seconds while it reads the log for errors.
  • The keyboard focus ring of a notification's link is drawn whole, a few pixels above its buttons, instead of a clipped line under them.
  • An install from npm with a Huly profile no longer crashes on every start while the Huly client is not installed yet (Huly in .env at the first start, or a client folder removed): the service comes up and installs the client.

v0.2.0

Choose a tag to compare

@NamerekWASD NamerekWASD released this 03 Nov 15:33

0.2 brings two more agents (OpenCode and GitHub Copilot) and two more trackers (GitLab and Jira), an install with npx even-keel that updates from the page, a first-start setup wizard, and Protection and Standards to limit what sessions may do.

Added

  • OpenCode and GitHub Copilot CLI (preview) as chain agents, beside Claude Code and Codex. OpenCode signs in with ChatGPT, an API key or its free models; Copilot with the machine's sign-in or a token per account, and its card shows the monthly allowance. Handoffs, chat messages mid-turn, the merge check and the tracker plugins' hooks reach both.
  • Claude sessions through the Agent SDK: "Execution" in Settings → Providers and models picks Auto, CLI --bg or Agent SDK. An SDK session survives a service restart with its question still open.
  • GitLab and Jira Cloud. GitLab Issues, GitLab CI and merge requests in PR mode, on GitLab.com and self-managed servers; Jira with fix versions as milestones and Blocks links as the order. Both come with a plugin. A tracker's MCP server can be connected through OAuth with one button, and sessions never see the access.
  • Task feeds: a project's chain can take tasks from several trackers or accounts. Labelled GitHub issues can be taken into your tracker as tasks; the issue gets a one-line summary when the task is done and reaches the session as information, not instructions.
  • Release branches: several projects share one tracker project split by milestone, and a release project's fixes are carried into the main branch, with an agent to resolve a conflict.
  • Install with npx even-keel as a service (on Windows at your sign-in with a tray icon, no administrator), and Update on the page with the release notes and Revert. If the new version does not come up, the old one comes back.
  • A first-start setup wizard: language, agent and account, tracker, statistics, update checks and the first project.
  • Protection (Settings → Sessions): deny rules for destructive actions for every agent, a switch per tracker that blocks deleting its records, and a warning about an unprotected main branch on GitHub and Forgejo.
  • Standards: a document tied to the files it guards reaches a session when it first touches them; the merge can wait for screenshots and answers to its check.
  • An Even Keel-wide Prompt and Model prompts matched by provider | model patterns. My skills turns your own skills into a package for every agent, and a project's CLAUDE.md/AGENTS.md and skills reach every agent.
  • Sessions: a waiting Claude session's cache is kept warm; handoffs by context size can be turned off in favour of the agent's own compaction; /handoff in the chat; a Claude permission dialog comes to the page as a question; an overloaded model is retried with growing waits.
  • Limits and accounts: extra usage and paid credits on account rows, and a chain session is stopped when paid usage is detected; an API key's spending cap holds the task until its date; Replace key for API accounts and Copilot tokens.
  • Checked CLI versions for every agent, and Check new CLI versions on this machine tries each new release with a short live session.
  • The /status page, a ? legend tab on the project page, a mark for uncommitted or unmerged work, and task labels editable from Even Keel.
  • Statistics count Codex turns and active time and follow-up tasks made on top of closed ones; the tally:session-audit skill proposes changes to your rules from them.

Changed

  • Chain sessions run on Claude Code 2.1.317, codex-cli 0.166.0, OpenCode 1.19.5 and Copilot CLI 1.0.105, the versions this release was checked against.
  • The page follows one design system: settings in sections and rows with one way of inheriting values, reworked account, CI, status and stats pages, and loaders instead of text.
  • Accounts appear only after Add account, grouped by provider. CLI copies are downloaded only when needed and with your consent, with progress in a banner.
  • Chain rules are set per status and per label for Even Keel, a project and a task label; a project's milestones moved to its Tracker tab.
  • A red main gives one notification per commit, only the CIs that count hold the chain, and projects of one remote share one red main.
  • New session on a silent turn becomes available after five quiet minutes, with confirmation.
  • Codex limits are read from ChatGPT every five minutes, and a plan change no longer shows as an expired token.
  • The later handoff thresholds count from the compaction point.
  • The npm package's dependencies went from 117 MB to about 34 MB; Huly's client is installed into the data folder once you add a Huly profile.

Removed

  • The shared Default tracker setting: every project has its own tracker, and older installs are migrated.

Fixed

  • Claude Ultra accounts without a five-hour limit and Team seats without an all-models week get their limits read.
  • The chain no longer hangs on a postponed task after its blocker closes, and no longer puts the working session aside on a red main right after a start. A deleted Huly project no longer breaks the others of its profile.
  • A process that reused a Claude session's pid is no longer taken for that session, nor stopped with it.
  • Codex on Windows no longer pauses the chain with EPERM when writing a session file. Codex limits are no longer lost or wiped by themselves. Codex 0.164 recognizes an OpenAI key again, and a key without money shows as "no credit".
  • Chat messages are no longer lost after a resume, on a Stop or on a mailbox hook timeout. The chat can answer a Codex session stopped by an API error, and shows AskUserQuestion cards and files sent with SendUserFile.
  • A Claude session that calls a tracker's MCP tool before loading its schema is told to load it and repeat the call, instead of leaving the field out.
  • Start after a profile change retries a pull request that could not be opened.
  • The add-project wizard sees folder trust given in an account folder, expands ~ and refuses a missing or relative folder, and shows a tracker error under the right field.
  • Changing the default profile no longer moves a running project to another profile. A plugin-only update no longer reinstalls the package's server.
  • Two processes no longer open the state or statistics database at once. Cleanup after Done handles long paths in git worktree remove.
  • Statistics no longer count some Codex responses twice.
  • Smaller page fixes: the backlog no longer freezes the page, dragging a blocker's card no longer jumps, a chain order error shows once, and long names no longer break the layout.

Security

  • Tracker keys set in the env of an account's settings.json no longer reach chain sessions.

v0.1.4

Choose a tag to compare

@NamerekWASD NamerekWASD released this 27 Oct 17:58

Fixed

  • A chain on Codex no longer stands still for a day after a usage limit. Codex gives the reset rounded down to the minute, so a new session started right at that time was refused again, and the time it named, already past, was taken for the next day. Now a reset given without a date that has just passed counts as today. After any limit the chain waits one more minute past the reset before it starts the next session. If the next session is refused again with a reset more than a minute in the past, the chain retries 10 minutes later.

v0.1.3

Choose a tag to compare

@NamerekWASD NamerekWASD released this 26 Oct 15:36

Fixed

  • Stopping a Codex session no longer kills an unrelated program. When a turn has ended and the operating system has given its process number to a newer process, "Stop", "New session" and the cleanup after Done leave that process running; before, they ended it together with its child processes.