All spotlights

Product spotlight · October 2026

Follow autonomous jobs live and run prompts on a schedule

QuantCode now uses your existing permission rules, hooks and project memory, streams autonomous jobs to a live console, and runs prompts later or on a schedule.

Updated QuantCode For developers

What changed in October 2026

The October 2026 changelog has the full details.

  • Live console for autonomous jobs

    Each QuantCode Agent job in the dashboard now opens a console that streams the session while it runs. Each tool call shows as a titled card with its duration, and the console shows the job's running cost and links to any pull requests that the agent opens. Jobs started from Slack also post a status message for the session in the Slack thread.

  • Scheduled and repeating prompts

    You can ask QuantCode to run a prompt later or repeatedly. A schedule has a start time, an end time or a run limit, and an interval or a cron expression with a time zone. It runs in the session that created it, on that session's current model, while the project is open.

  • Claude Code settings, hooks and memory

    Repositories set up for Claude Code now work the same way in QuantCode. QuantCode applies the allow, ask and deny permission rules in .claude/settings.json, .claude/settings.local.json and your user settings, and it loads and can add to the project memory that Claude Code keeps. It runs SessionStart, UserPromptSubmit and Stop command hooks, but not in autonomous jobs or sub-agent sessions.

  • A model suited to each agent

    Autonomous jobs now run each agent on a model suited to its work, where your AI governance settings allow it, instead of one model for every agent. This lowers the cost of a typical job. Security and supply-chain review agents keep their configured model, and the job report breaks down spend by agent and model.

  • Automatic updates

    The macOS desktop app checks for updates 10 seconds after it starts and every 4 hours, then asks you to restart to install a new version. Homebrew installs of the CLI with automatic updates on now install any newer release, not only patch releases. Other installs show a notice when a new version is available.

  • Smaller requests

    Each request now lists your local skills once instead of twice. This removes about 4,600 tokens from every request when 45 skills are installed. The system prompt stays the same across sessions in a repository, so cached prompts can be reused.

Who it is for

  • Repository maintainers

    Keep the permission rules, hooks and project memory that your repositories already have, and use them in QuantCode.

  • Teams running jobs

    Follow an autonomous job while it runs, answer its approval requests, and see its running cost and pull requests.

  • Build and deploy checks

    Ask QuantCode to check a build or a deployment later or repeatedly, in the same session, while the project is open.

How it works

You ask for a schedule in plain words, in the session where you want it to run. For example:

check the build in two minutes
from 1am tomorrow, check the deployment every minute for an hour

The desktop app and the terminal interface list each schedule with its next run, and you can pause, resume, complete or cancel it.

The live console lets you act on an autonomous job while it runs. You can send the agent a message, interrupt or pause it, or cancel the job. When a job must ask before an action, an Approval needed card shows the request. You can approve it once, always allow it for the session, or deny it. A finished session replays in full and is marked as ended.

Two actions now ask you first. A hook that comes with a project asks once before it first runs. By default, QuantCode also asks before it opens a shell in a running cloud container.

When the connection drops during a cloud tool call, such as web search, QuantCode no longer sends the request again. It stops and asks you to check the result in the dashboard.

Get started

  1. Update QuantCode

    Restart the desktop app when asked. Other installs: quantcode upgrade gives steps.

  2. Check permission rules

    Review the allow, ask and deny rules in .claude/settings.json.

  3. Schedule a prompt

    Ask QuantCode in plain words, for example "check the build in two minutes".

  4. Manage your schedules

    Use the Schedules button in the desktop app, or the list in the terminal.

  5. Open a job console

    Open a QuantCode Agent job in the dashboard to follow its session live.

Related: Explore QuantCode · October 2026 changelog

Ready to try it on Quant?

Use QuantCode on your own project, or read more about it first.