Claude

What it does

• Picks up a ticket — a bug, a story, a small feature — with any extra instructions you add.
• Works in the repository mapped to the ticket’s product, on its own branch.
• When it’s done, Worklynq opens a pull request for your team to review. Claude never merges its own work.

Before you start

• Connect GitHub first. Claude uses Worklynq’s GitHub connection to work in your code, with Contents and Pull requests write permission on the repositories it should touch.
• An Anthropic API key. Create one in the Claude Console under API keys. Usage is billed to that Claude Console account by Anthropic, pay as you go — separate from a Claude Pro subscription.
• You need to be your workspace’s System Admin.

Connect Claude

1. Open the Admin console → Connectors → Developer Connections and choose Claude.
2. Paste your Anthropic API key.
3. Choose the Claude model to use.
4. Map each product to its repository and base branch — this is where Claude works for that product’s tickets.
5. Optionally set limits for each session (see Limits and control).
6. Save. Claude shows as Connected.

Hand a ticket to Claude

There are three ways to start Claude on a ticket:

• From a ticket: choose Hand this ticket to Claude and add any instructions.
• When you create a ticket: tick Hand this ticket to Claude after it’s created.
• Automatically: in a ticket type’s workflow, add the action Hand ticket to Claude to a stage. Every ticket that reaches that stage goes to Claude. The instructions can include the ticket’s title and description.

Write tickets the way you would for a new teammate: what’s wrong or wanted, where to look, and how to know it’s done.

What you see on the ticket

Each ticket gets a Claude section showing the session’s status, Claude’s summary, the files it changed, its activity, the pull request, and how much it used. From there you can stop a running session or run Claude again (which starts a fresh session).

Your System Admin can turn the Claude section on or off for each ticket type in Admin console → Work Configuration → Ticket types. When it’s off, that type’s tickets can’t be handed to Claude, including by automations.

Limits and control

• Maximum run time and stop if idle: Worklynq stops a session that runs too long or goes quiet.
• Maximum cost per session: Anthropic stops the session when it reaches the budget.
• Leave a limit blank for no limit. Limits are set in Developer Connections → Claude.
• Claude’s changes always come back as a pull request. Your team decides what to review, merge, and deploy.

Troubleshooting

“No repository is mapped to this ticket’s product”

Add the product’s repository and base branch in Developer Connections → Claude.

“Claude needs Worklynq’s GitHub connection”

Connect GitHub first.

Claude finished but made no changes

Read what Claude reported on the ticket — it explains why. Often the ticket needs more detail.

The session failed while opening the pull request

Usually GitHub permissions (Contents and Pull requests need write access) or branch protection on the base branch.

The key is rejected when connecting

The key is wrong, revoked, or from a different Anthropic workspace. Create a new key and try again.