Repository navigation
Releases: FelixMUrphy/TaskHub
Release list
TaskHub 3.1.0
- New connector: AWS. EC2 instances, SageMaker training jobs and AWS Batch jobs as tasks, this month's cost and forecast, AWS Budgets, each behind its own switch. Off until you turn it on, and read-only. Built from AWS's documentation and tested against a simulator, not yet on a real account. Cost Explorer is billed by AWS ($0.01 per request; about $1.80 a month). That switch goes on only in Settings, not through the local API.
- Settings open beside the panel, with icon tabs. While the panel is pinned they close only with their own button.
- Plan limits for Claude Code, off until you turn them on: how much of the 5-hour and weekly limits is used, in the panel, yellow with a warning from 75%, red with a warning from 90%. Your own status line keeps working unchanged. Also by script:
TaskHubHost.exe --integrations claude-limits=on(Codex: with TaskHub closed). - Plan limits for Codex too, off until you turn them on: TaskHub asks Codex every 10 minutes while it is running, with no model requests. Each row says how much is used. In the panel each agent's limits sit under its own name, and the bars take the Windows accent colour.
- The About page says in a few words what TaskHub does.
- Fixed: a button in a Telegram message sent before TaskHub restarted could run a button of a different task. Such a button now says it has expired.
- A path naming another machine in an agent's message is no longer looked up, so TaskHub makes no connection there and doesn't stall. A reset time no limit window can have counts as no reset time.
- On battery the panel and settings appear and go at once, without the slide, which could leave text running over the panel or onto the next monitor.
- Vast.ai: the balance shows again, and with it the low-balance warnings and the balance guard. Vast.ai had started redirecting the address TaskHub asked.
- A task's percentage now shares a row with its status, and the task counter is short (1 / 3), so the header no longer wraps.
- GitHub Actions: the bar follows the same time estimate as the ETA instead of standing still during a long step. A run past its usual duration says so.
- Notifications from Claude Code and Codex are offered in the panel when an agent is found and you haven't chosen yet. Nothing changes in the agent's settings until you press Connect. A switch left off in setup for an agent that isn't on the PC no longer counts as a no.
- No more two notifications for one thing: "response ready" is left out when the agent has just sent its own notification or finished a task from the same project. With the hooks on, TaskHub's MCP server also asks the agent not to notify just to say it is done.
- Safer Claude Code notifications: TaskHub's hook is now a command rather than a local web address, and no token stays in Claude Code's settings. With TaskHub closed, another program listening on its port could read the agent's last message and steer it. Existing entries are replaced on start; this needs a recent Claude Code.
- Codex notifications now work when TaskHub is installed in a folder with a space in its path on a drive without short names.
- A clearer local log: date and level on every line and what a problem report needs at the top. Notification text and task names are no longer written unless you set
"log_level": "debug"inconfig.json, and anything that looks like a token or key is removed. At that level the command-line tool writes its own failures tocli.log. Back at the default level, TaskHub deletes on start what a beta build or that level left behind. Script errors in the panel now go to the log. - GitHub Actions: a repository the token can't reach now gets one clear line in your language that says what to check, instead of two English and mixed messages.
Install
- TaskHub-3.1.0-setup.exe — per-user, no admin rights; run it and press Install. Silent:
TaskHub-3.1.0-setup.exe --install --quiet.
SHA-256 of the setup exe: 07026184a5832688005a193642e630f68b25cf258a3316c2777facc4f0063628
Full Changelog: v3.0.0...v3.1.0
TaskHub 3.0.0
- TaskHub now runs on .NET 10 (long-term support until November 2028); .NET 8 support ends on 10 November 2026.
The runtime is still inside the app, nothing to install. - Not tested on Windows 10 for this release: the .NET 10 supported-OS list names only LTSC / IoT builds of Windows 10, not 22H2. If TaskHub 3.0.0 misbehaves on your Windows 10, please open an issue.
Install
- TaskHub-3.0.0-setup.exe — per-user, no admin rights; run it and press Install. Silent:
TaskHub-3.0.0-setup.exe --install --quiet.
SHA-256 of the setup exe: 79c4ad231605cd2543ac0f8ccda74b8ee6c97450c4302817f5a07258f9e691ae
Full Changelog: v2.9.7...v3.0.0
TaskHub 2.9.7
- The pinned panel keeps its edge of the screen: maximized windows make room for it and get the space back when you
unpin or hide it. A new switch on the settings page (off by default) also moves or narrows the other windows on that
screen, and puts them back on unpin. - Fixed: after adding a repository on the GitHub settings page as a link (
https://github.com/owner/repo), the text
stayed in the field although the repository was added. - API.md: an Errors section (error body and status codes), long-poll limits, how commands are delivered (once, on
read) and acked, which progress field wins, the token rule (every request except/api/health) and whereconfig.jsonis; what
registering an existingidkeeps, what counts againststale, the default controlkind, connector and guard
fields in one request.
Install
- TaskHub-2.9.7-setup.exe — per-user, no admin rights; run it and press Install. Silent:
TaskHub-2.9.7-setup.exe --install --quiet.
SHA-256 of the setup exe: 1ffdd2bac03decff29b47dc14203f6d91d5759afba4a60b6cbbb35ab05c0511a
Full Changelog: v2.9.6...v2.9.7
TaskHub 2.9.6
- GitHub Actions is set up right on the settings page (Connectors → GitHub Actions): access, repositories with their
state, interval, notifications and pull requests, instead of a separate window. taskhub mcp: a waitingtask_waitno longer holds the agent's other TaskHub calls (they waited up to 50 s); a call the
agent cancels stops; the server ends together with the program that started it, so no orphanedtaskhub mcp
processes are left behind.- Fixed: the spend guard (Runpod / Vast.ai) could hold its automatic stop for up to 10 minutes (or a day) when the key
was saved while a check of its rights was still running; the check now runs again after the save.
Install
- TaskHub-2.9.6-setup.exe — per-user, no admin rights; run it and press Install. Silent:
TaskHub-2.9.6-setup.exe --install --quiet.
SHA-256 of the setup exe: bee4fe464e66da3b82cfa434004affc7fb87e8019bc2fe56905b4abbd5ae28d5
Full Changelog: v2.9.5...v2.9.6
TaskHub 2.9.5
- Fixed: Update to X on the settings page could stay at an older version for up to a day after a newer one came out
(the hub keeps running while the panel is hidden). The open settings page re-checks quietly when the last check is
older than 15 minutes (only with automatic checks on), and Update to X always opens the newest release.
Install
- TaskHub-2.9.5-setup.exe — per-user, no admin rights; run it and press Install. Silent:
TaskHub-2.9.5-setup.exe --install --quiet.
SHA-256 of the setup exe: af9888981da317fab09d8a5b2d85708f6207ab8d8390ae55859a20c3677ef94d
Full Changelog: v2.9.4...v2.9.5
TaskHub 2.9.4
- GitHub: pull requests, read-only (off by default): PRs waiting for your review and open Dependabot PRs of the
watched repositories become tasks with a link and a notification; they end quietly when merged, closed or reviewed.
Nothing is merged, approved or commented on. - Telegram is set up right on the settings page (token, the t.me link with its QR code, the switches, Send test,
New link, Disconnect) instead of a separate old-style window. - Transparency sliders say when Windows draws no blur: energy saver on, or Transparency effects off in Windows settings
(with a link to that setting); the hint comes and goes without a restart. - Fixed: uninstalling the GitHub edition from Settings → Apps said "installed from the Microsoft Store" and removed nothing.
- Fixed: Check for updates said nothing when TaskHub was up to date; the answer now shows on the settings page.
Install
- TaskHub-2.9.4-setup.exe — per-user, no admin rights; run it and press Install. Silent:
TaskHub-2.9.4-setup.exe --install --quiet.
SHA-256 of the setup exe: 300a79c67c50201ff8e68faf04e31ec981a1cfb9595b3c70cca9a521d43afc4c
Full Changelog: v2.9.3...v2.9.4
TaskHub 2.9.3
- Runpod / Vast.ai: auto-stop on GPU idle (off by default): Stop when the GPU is idle for, min. A machine idle that
long gets the balance guard's announcement with Stop now / Snooze; GPU busy again cancels it; stop only, never
delete; Never auto-stop machines are left alone. Works with the balance guard off. At the deadline the machine must
have a recent idle reading (unknown load: not stopped). taskhub run, Blender preset fixes: Ctrl+C after some frames were saved is cancelled again, not failed; the printed
resume command keeps a quoted path that ends with\intact and no longer changes the arguments after--(those
belong to Python scripts). Video output (FFmpeg, "Append frame N") counts frames and Stop after this frame works for
it; stereo views saved as separate files count as one frame; the memory-leak note Blender prints at exit no longer
fails a good render; Stop after this frame now ends Blender when the next frame begins (pressed during the last
frame: the render just finishes, done).
Install
- TaskHub-2.9.3-setup.exe — per-user, no admin rights; run it and press Install. Silent:
TaskHub-2.9.3-setup.exe --install --quiet.
SHA-256 of the setup exe: 90ef61c60bf163e4fb564312d2e499966cf4ed3b5cb9f7ef24268c7a706701c5
Full Changelog: v2.9.2...v2.9.3
TaskHub 2.9.2
- MCP: new tool
task_wait— blocks up to 50 s until a task finishes, so an agent waits for a job instead of polling
with sleep. - The MCP server is also published as an MCP bundle (
taskhub-mcp-win-x64.mcpb, a release asset) and listed in the
MCP Registry asio.github.FelixMUrphy/taskhub; it needs the TaskHub app installed. taskhub run -- blender -b …reads Blender's render output: frame and samples, overall progress when the frame range
is known, seconds-per-frame and memory charts, the last saved file. A render error fails the task (Blender itself
exits with 0). Stop after this frame ends the render cleanly; after a stop or a crash the task and the console say
how to resume (-sset to the next frame).--preset blender/--preset nonechoose it by hand.
Install
- TaskHub-2.9.2-setup.exe — per-user, no admin rights; run it and press Install. Silent:
TaskHub-2.9.2-setup.exe --install --quiet.
SHA-256 of the setup exe: 417095f400ffaafc6bd6f4f9229dffd69bfb3b9eda2f43bcaccf367e61ee55f0
Full Changelog: v2.9.1...v2.9.2
TaskHub 2.9.1
Full Changelog: v2.9.0...v2.9.1
TaskHub 2.9.0
Full Changelog: v2.8.0...v2.9.0