Use Claude Agents when you want Leadtime to start Anthropic-hosted task sessions for an agent. Leadtime can manage the Claude agent for you, or you can connect resources you already maintain in Anthropic Console. In agenth setups, Leadtime sends task context, attaches the Leadtime MCP tools, and can mount GitHub repositories or external MCP tools when the agent runs.
Create or choose an agent in Workspace settings > Agents, then set its type to Claude Agent.
Have an Anthropic API key with access to Claude Managed Agents. You can save it once and reuse it for multiple Claude agents.
Use Manage agent in Leadtime for the normal setup. Use Connect existing agent only when you already manage the Claude agent, environment, or vaults in Anthropic Console.
If the agent should work on code, connect GitHub and choose the repositories Leadtime should mount for sessions.
If the agent should use external tools such as hosted MCP servers, collect the MCP server URL and decide whether it needs no auth, a bearer token, or OAuth login.
In Agent connection, choose a saved Anthropic API key or add a new one. Leadtime stores the key as a reusable workspace provider key, shows only a masked value, and lets other Claude agents use the same saved key.
Use Add API key when no key is saved yet or when you want to store another Anthropic account.
Use the dropdown to switch the agent to another saved key, or delete keys you no longer need.
Click Validate connection after selecting or adding a key. Claude setup controls are disabled until the connection is valid.
The key is used only by Leadtime to create, repair, list, and start Claude Managed Agent resources.
Choose Manage agent in Leadtime when you want Leadtime to create and maintain the Claude resources for this agent. Saving the settings creates or repairs one Claude agent, one cloud environment, and one MCP credential vault for the agent.
Write Agent instructions in the rich editor. Leadtime stores the editor content and syncs it to Claude as HTML-safe instructions.
Choose the Claude model from the model picker. The list comes from the selected Anthropic API key, and Sonnet is the default for most agents.
Add custom MCP servers when the agent needs external hosted tools.
Use Custom guidance for extra run-time guidance that should be appended to Leadtime task guidance.
Use Ask agent when you want Leadtime's internal agent to help configure or improve the agent.
Skills give a Leadtime-managed Claude agent reusable instructions and workflows. Attach Anthropic built-in skills and workspace custom skills that you define once and reuse on any Leadtime-managed agent. Leadtime syncs your selection to Anthropic when you save the agent.
Open the Skills section in agent settings, above Custom MCP servers. Use the skill picker to choose built-in and workspace skills.
Click Create skill to add a workspace custom skill with a skill ID, display title, short description, and Markdown skill instructions (when to use, API patterns, examples, guardrails).
Click Manage skills to edit or delete workspace skills. Saved changes apply everywhere that skill is selected on Leadtime-managed agents.
Skills apply only when Manage agent in Leadtime is selected. For Connect existing agent, manage skills in Anthropic Console.
Choose Connect existing agent when your team already maintains Claude Managed Agent resources in Anthropic Console. Leadtime does not edit that Claude configuration; it selects the resources and starts sessions with them.
Refresh Claude resources, then choose the Claude agent and cloud environment.
Select any user vaults the existing agent should receive.
Leadtime still attaches its own hidden vault at run time for Leadtime task tools and any GitHub credentials configured in Leadtime.
Use this path for advanced setups where you want Claude Console to remain the source of truth.
Custom MCP servers add hosted tools to the Claude agent, for example a documentation system, CRM, search service, or another internal tool exposed as MCP. Leadtime stores credentials in the agent's Claude vault and attaches them when the agent runs; secrets are not written into prompts.
Click Add MCP, enter a display name and MCP server URL, then choose the authentication mode.
Use No token for public MCP servers that do not require credentials.
Use Bearer token when you already have an API key or access token. You can paste it in the modal and replace it later.
Use OAuth when the provider supports delegated login. After saving the MCP server, click Log in in the MCP list. Use Reconnect or Disconnect later to refresh or remove the credential.
Advanced OAuth setups can also store an access token or OAuth client credentials manually.
Use GitHub repositories when the Claude agent should inspect code, create branches, commit changes, or open pull requests. The GitHub connection belongs to the agent, so different agents can use different GitHub accounts or repository sets.
Click Connect GitHub, authorize the Leadtime GitHub App, and choose the repositories this agent may use by default.
Use Reconnect GitHub to refresh the GitHub authorization or repository list, and Disconnect to remove the agent connection.
In Project settings > Agents, override the repository list when a project should mount a different subset of repositories.
When a task session starts, Leadtime mounts the selected repositories as Claude resources and supplies GitHub access for the run.
You do not paste GitHub tokens into Claude. Leadtime provides the needed repository credential and GitHub MCP credential programmatically.
Tool mode controls which Leadtime MCP tools Claude receives during task sessions.
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.
Allow direct API access only for trusted agents that need script-based public API calls inside a session.
Optional agent personal access tokens are separate from Claude sessions. Use them for scripts, jobs, or integrations that need to call Leadtime as this agent outside Claude.
Project settings can inherit the agent defaults or override them for a specific project. Use project overrides when the same Claude agent should use different repositories, custom guidance, or agent rules in different projects.
When a task is assigned to the Claude agent or the agent is mentioned in a task comment, Leadtime creates a task session card, starts a Claude session, sends the current task context, attaches the configured skills, MCP tools, and repository resources, streams progress into the task history, and shows the session log in the session modal.
