Conversations

A Conversation is a live chat with a coding agent, working in one of your workspaces. Where a ticket runs on its own and comes back when it’s done, a Conversation keeps you in the loop for every message, you ask, it responds, you steer, in real time.

When to use it

Reach for a Conversation when you want to work with an agent rather than hand something off:

• a quick question about the code that isn’t worth a ticket,
• exploring an idea or sketching an approach before you commit it to tickets,
• pairing through a fiddly change where you want to react to each step.

For work you’d rather set going and walk away from, use a ticket instead, see Feeding it work.

Starting one

Pick a workspace, choose which agent and model to talk to, and start typing. The agent works in that workspace’s repo with the same tools it has on a ticket: it can read the code, make changes, and run commands, and you see each step as it happens.

Staying in control

The agent asks before it does something that touches your machine, editing a file, running a command, so nothing happens without your say-so. If you find yourself approving the same kind of action over and over, you can let it stop asking for that kind, in that workspace, and take it back whenever you want.

A Conversation stays open while you’re using it and ends when you close it or leave it idle too long. Once ended, you can still pick the thread back up. Send another message and it resumes right where it left off, with its history and context intact. The first message back can cost a little more while the session warms up again, so Harmonic flags the cold resume before you send.