Skip to content

4 min read

Setting up AI assist

Your provider, your key, your models, your budget.

Nothing happens until you connect it

AI assist is off until an administrator connects a provider. There is no shared Vorkhurry key and no default-on behaviour — a workspace that never opens the AI settings never sends anything to a model.

Configuration is a policy, not a toggle

Connect OpenAI, Anthropic or Google Gemini with your organization's own API key. The key is encrypted at rest and never returned — reading it back gives you a masked suffix.

Then choose which models are enabled, a default model, per-feature overrides, and a monthly budget. Every call writes a usage row, so spend is a number you can look at rather than a surprise on an invoice.

Output is a suggestion

An assist produces a suggestion in one of three states — generated, then accepted or rejected, then applied. Applying it to an issue is a separate action a person takes.

The assists are: on an issue, draft a description, suggest acceptance criteria, break into subtasks, summarise the thread, suggest a priority; on a project, draft a delivery plan, propose milestones, identify risks; on a sprint, advise on scope, summarise progress, surface blockers.

All guides

Start with your team, not with a sales call

Create a workspace, invite the people you work with, and bring your existing issues in from Jira, Linear or a CSV.