Bots & conversations

A bot is a saved teammate: a name, avatar, provider, model settings, instructions, and working folder. Give it a clear responsibility, such as editing an article or investigating a bug, so its role is easy to recognize when you return.

Add a teammate

Inside a branch, use the + beside the team’s name. Choose a provider and describe the bot’s role. Newton can create a workspace inside the branch or use an existing folder you choose. Check the folder before confirming: it is where the bot will work.

The current desktop offers Claude Code, Codex, Gemini, and experimental Hermes. Each needs its own supported installation and authentication. Provider availability, model choices, and usage limits depend on your setup. Newton does not include model access.

Conversation or CLI?

• Conversation presents messages, replies, and supported activity in a readable chat. Use the composer to continue the conversation and attach useful context.
• CLI opens the provider’s interactive terminal. Use it when a provider needs its own command, sign-in, or terminal interaction.
• The sidebar chat shortcut opens a quick conversation while keeping your current workspace close at hand.
• Routines, Connections, and Skills are available alongside the bot’s conversation. They describe scheduled work, tool access, and reusable instructions.

Conversation history is assembled from supported provider messages. Earlier or unsupported history may not appear there; a saved chat view is not a complete transcript of every terminal interaction.

Change the profile

Use Show profile beside the bot’s name to inspect its identity and configuration. Keep instructions specific about the result you need, the files involved, and how success should be checked. Provider permissions still apply to the work.

Keep or resume earlier work

Open Session logs from the top view row to browse saved conversations by bot. Select a session to read it. Where resumption is supported, Newton uses the original bot and provider; the original workspace and provider session must still be available.

Use Greenhouse when you need to see multiple live terminals together, or Kanban when work needs an explicit result and review.