Skip to content
AiQu Docs

v3.45.0

AiQu can be driven by an AI agent, through personal API keys and a hosted MCP server with browser sign-in. The rest is mostly scheduling and billing fixes.

New

Section titled “New”
  • A hosted MCP server for AI agents, at mcp. followed by your AiQu domain. Claude Code, Cursor, VS Code, Codex and opencode connect with one line, for example claude mcp add --transport http aiqu https://mcp.aiqu.ai/mcp. The agent opens a browser, you approve it with your existing AiQu sign-in, and no key is copied into a file. An agent can list queues and what is free on them, book, extend and cancel jobs, read logs, open ports and run commands in a running job, with the same access you have in the terminal.
  • Personal API keys, for CI and anything else without a browser. Revoking a key under API keys also disconnects any agent that was approved through the browser.
  • Connect an agent under Account settings shows ready-to-paste setup for each tool. Where browser sign-in is turned off, it shows the API key route instead.
  • Account menu and Account settings. The account block at the bottom of the sidebar opens a menu with settings, API keys, notifications, dark mode, the classic interface, bug reports and sign-out. Profile, password and defaults have pages of their own.
  • Terminal button on the job row. A job with several services now offers the terminal on the job itself, with a menu to pick the service.
  • Statistics for administrators: GPU hours per project and period, and utilisation over time. A restarted job counts with all its runs, not just the latest.

Fixed

Section titled “Fixed”
  • A job could be extended into the next booking on the same node, so two jobs held the same GPUs at once. Extending now checks the node and the wallet first, and extending one service extends the whole job.
  • A job created in the new interface that did not fit right away was queued without a start time. It now gets the first free slot.
  • The scheduler could double-book a node for a booking with a start time.
  • A failed interactive job could not be cancelled and held its node until its booked time ran out. When one service in a job fails, the others are no longer cancelled, so the configuration can be fixed and the job restarted in place.
  • A job out of tokens could keep running while you were told it had been stopped. Transfers between wallets are also always saved now.
  • Private ports on Docker nodes could hang until they timed out, including on upgraded installations with no port access list configured.
  • Ports for system services survive invalid specifications, leftover proxies and dead nodes, and one unresponsive node no longer stops ports from opening on the others.
  • Mounting the same storage folder twice in a job silently replaced the first mount, or kept the job from starting. It is now refused with a clear message.
  • A browser signed in to one AiQu environment could loop at sign-in on another under the same domain. Sign-in cookies for private ports are now set with Secure and SameSite.
  • Password errors showed as [object Object] in the new interface.
  • The www. address gave an error instead of leading to the start page.
  • The notification and bug report panels opened underneath the terminal panel.
  • The job API returned the start time as a date in 1970. The stored value was always correct.

Changed

Section titled “Changed”
  • The product video is self-hosted on the start page and in the documentation, instead of embedded from a third party.