This preview is distributed as a local plugin bundle. It is separate from the
skills bundled inside Qualia. You need Node 22 or newer and a Qualia Cloud account.
Install the preview
Unzip the supplied Qualia hillclimb bundle into a stable folder on your computer. The bundle includes the skill and its helper; you do not need the Qualia CLI.Claude Code
Launch Claude Code with the plugin folder:/qualia:hillclimb with your objective. The plugin includes the Qualia MCP
connection.
To receive Qualia questions and completed messages while Claude is idle, the
Qualia channel must also be enabled when launching Claude. This is currently a
Claude Code research-preview feature; Team and Enterprise organizations need
administrator enablement. Follow the channel setup in the bundle’s README.
Without it, the plugin uses one long event wait. Interactive Claude Code 2.1.212+
can move that wait to a background task and notify the conversation when an
update arrives, depending on your background-task settings.
Codex
Copy the bundle’sskills/hillclimb folder into your project’s
.agents/skills/hillclimb folder, then register its helper:
$hillclimb with your objective.
Sign in
Your coding agent checks for an existing local Qualia login. If needed, it runs the bundled helper and opens your browser. Complete sign-in on the same computer as your coding agent. Signing into the website in a separate tab does not by itself connect the helper. After a successful sign-in, the browser returns to your Cloud workspaces. If an old login tab shows “localhost refused to connect,” ask your coding agent to check the Qualia connection. When that check succeeds, you can close the old tab without signing in again. The helper stores your session locally with owner-only permissions. Do not paste credentials into chat. API keys alone do not authenticate this preview’s Cloud research workflow.Start a research run
For example:Improve this classifier’s validation accuracy. Keep the evaluator and validation split fixed. Try at most five CPU-only experiments and return the best code and a report of every trial.Your coding agent and Qualia settle the evaluation, permitted changes, compute limits, and stopping condition. If there is no starting code, Qualia can build a minimal baseline; your coding agent handles application-specific setup. For a small public-dataset demo, you can start with just the dataset and metric:
California housing dataset, minimize MSE.When you have not supplied limits, the agent states a default scope of five candidate trials, one CPU worker and 20 minutes. Qualia prepares a deterministic evaluation and baseline in Cloud. Larger or expensive runs need an explicit scope. In Claude Code the agent asks the setup decisions as a short multiple-choice survey: the metric and its constraints, how scores and failures are counted, the budget, and which numbers you already trust. If you say you are away, it picks documented defaults instead and lists them in the final summary. Before any experiment runs, Qualia freezes the evaluator and computes the values the objective depends on. Your agent shows a kickoff card that leads with any target that disagrees with your reference numbers and any failed or warning data check, then the contract: objective, evaluation, data, scoring rules, budget and approval policy. A mismatch stops the run until the contract is fixed. Command approvals have two modes, chosen in the setup survey before the run is created. In the recommended mode, which is also the default when you are away, Qualia runs commands in its workspace sandbox without asking. A few commands still need confirmation, such as deleting a home or root directory or writing outside the workspace when no sandbox confines the command. In the other mode every command asks. There, accepting the card’s approval policy lets the helper approve read-only commands and runs of the frozen evaluator. That approval lasts for that run only, and everything else still comes to the agent. The agent posts a clickable link to your Qualia workspace as soon as it is created. Ask “Where’s the Qualia workspace?” at any time to get the same link. The research kickoff identifies your local coding agent and invokes Qualia’s existing
/optimize workflow: baseline and experiment tasks, a leaderboard,
measured evidence and verification. Your explicit limits take precedence over
the workflow’s default size.
When source files are needed, your coding agent selects them explicitly. The
helper uploads their current contents, including uncommitted edits, and saves a
baseline copy locally. Transfers support up to 200 files, 8 MiB per file, and
32 MiB total. Use remote references for larger datasets and model checkpoints.
Trial, time, and spend limits are instructions to the research agent. They are
not enforced spending caps. Keep a separate held-out evaluation locally when you
need independent confirmation of improvements.

