harness-multitool

0022 — Moving a Claude Code conversation onto the harness

Decision

A conversation can move onto the harness and go on there, with its whole context.

The context can only go on where it lives, in Claude Code, and the harness never holds a Claude subscription's tokens (CON-56, CON-57). So the conversation is not converted for another model. It goes on through the delegate, and the harness gets a copy for the screen.

What goes with it

A delegate is isolated by default. A conversation that moves needs what it has been working with, so a provider row can opt in:

[session.providers.claude-code]
kind = "claude-code"
environment = "user"   # the user's own settings, hooks, servers and environment
permissions = "skip"   # no permission prompts, as the user may run Claude Code themselves

permissions = "skip" is only ever the user's own setting. Without it, tools that need approval are denied until the harness answers prompts itself.

Limits

This page's source