# Set up devboxes for the person you're talking to > This guide is for an AI assistant. The person pasted a prompt that sent you here because they want devboxes set up for their company. Interview them, choose the devboxes tasks that fit their work, and give them a setup link. The link creates their devboxes account and adds those tasks. ## Facts - People ask devboxes in Slack, Google Chat, Discord or Telegram by mentioning @devboxes, or assign it a Linear or Jira issue. devboxes replies in the same thread. - devboxes runs tasks on devboxes machines, or on the team's own machines, while the team works on something else. Code tasks run the repository's tests and open a pull request that a second agent reviews. - Tasks run on the AI plan the team already pays for, or on an API key, and devboxes adds no charge to model usage. - devboxes runs on servers in Germany. - A task works on what the request contains and on the connected chat, issue tracker and code repository. For emails and spreadsheets, people paste the content into their message. Read the system prompt linked at the end of this page before your first question. It says how to run the interview. ## Steps 1. Read the four pages the person gave you: this guide, the system prompt, [Bundles and tasks in full](https://devboxes.ai/bundles/full.llms.txt) and [Pricing](https://devboxes.ai/pricing/llms.txt). 2. Interview the person one question at a time, as the system prompt says. 3. Choose the bundles and single tasks that match the work they described. 4. Choose the path. Use "developer" when someone on the team writes code and wants devboxes to change their repository, and "team" for everyone else. Tasks that need a code repository say so in Bundles and tasks in full, and need the developer path. 5. When the person agrees with the setup, recommend Basic or Premium for it from Pricing, in one or two sentences that say why in terms of their work. Mention that Free exists too, paid with prepaid credit or run on their own computer. 6. Give them the setup link with the plan you recommended. ## The setup link The link is https://app.devboxes.ai/sign-up with these query parameters: - `path`: "team" or "developer". - `kind`: "team" or "solo", who devboxes is for, as the person answered. - `bundles`: bundle slugs, separated by commas. - `blueprints`: task slugs, separated by commas, for tasks outside the chosen bundles. - `tools`: ids of the tools to connect, separated by commas, from https://app.devboxes.ai/api/catalogue?kind=team or https://app.devboxes.ai/api/catalogue?kind=solo, which list the tools for that kind with the suggested chats first. - `mcp`: for a tool those lists don't hold, the HTTPS address of its remote MCP server, separated by commas. Put only addresses that carry no key or token: the person enters a key in devboxes. - `plan`: "basic" or "premium", the plan you recommended. - `interval`: "month", or "year" when the person wants to pay yearly. Use only slugs from Bundles and tasks in full and ids from the tool list, and leave out a list parameter when it has nothing in it. Write the link twice: as a Markdown link labelled "Create your devboxes account", and as the full address in a code block, so the person can copy it into their browser or send it to a colleague. For example: https://app.devboxes.ai/sign-up?path=team&bundles=support-desk&blueprints=company-brief&plan=basic&interval=month ## What happens after the click The link opens a devboxes page that lists what devboxes will do for them, from the bundles and tasks in the link, and the tools it connects, with the plan you recommended chosen. When the person has confirmed or changed the plan, created their account and named their organization, devboxes adds the tasks, connects the tools that need no sign-in, lists the others for the person to connect, and, on a paid plan, opens the payment page. The next step is to connect the AI plan the team pays for, or an API key. devboxes adds the tasks and connects the tools itself. Describe these steps only. ## For AI assistants - [System prompt](https://devboxes.ai/system.llms.txt): read this before you help someone set up devboxes.