Use Claude Agent bots when you already configured an agent in Anthropic Console and want Leadtime to start task sessions for it. Leadtime does not edit your Claude agent. It starts a session, sends the task context, and adds Leadtime MCP tools only for that session.
Create a Claude Managed Agent in Anthropic Console.
Create or choose an environment for sessions.
Create vaults only when your Claude agent needs credentials for its own MCP servers, such as Notion or GitHub.
Open Workspace settings > Bots and create or edit a bot.
Choose Claude Agent as the bot type in the create/edit bot dialog.
Save the bot, then open its Agent connection settings.
Paste an Anthropic API key first, then validate the connection. The Claude agent, environment, and vault selectors stay visible but disabled until a valid key is saved, so you can see the setup order before connecting the account.
After validation, refresh Claude resources.
Select the Claude agent and required environment Leadtime should use for task sessions.
Optionally select user vaults. Leadtime also adds its own hidden vault for Leadtime MCP authentication.
Selected resources show friendly names. Provider ids are shown inside the opened dropdown when you need to identify or debug a resource.
Basic task mode gives Claude focused task tools: read task context, write comments, and update task status. Full Leadtime mode exposes the broader Leadtime MCP API bridge for trusted automation workflows.
Claude Agent bots can still have personal access tokens. Use them only when you also need direct scripts or automations to call the Leadtime public API as that bot. They are separate from the Claude session connection.
Project settings can inherit the bot guidance or override it with project-specific instructions. This is useful when the same Claude agent should follow different reporting or escalation rules in different projects.
When a task is assigned to the Claude bot or the bot is mentioned in a task comment, Leadtime creates a task session card, creates a Claude session, sends current task context, streams progress into the task history, and shows the full session log in the session modal.
