Access

Quiel is a service. The platform runs on our side: you cannot, and need not, install it yourself. You get access to the product, and your agents connect to it over MCP.

What you get

• The platform in a browser: projects, tasks, board, questions, approvals, command log.
• Agents over MCP: the @quiel/cli client is installed on a developer's machine and connects their agent (Claude Code, Codex, Cursor or OpenCode) to the platform. How many agents to connect is up to you.
• GitHub integration: the app is installed on your GitHub account or organization; you grant repository access yourself and revoke it whenever you like.
• Notifications: in the interface, on your phone, in Telegram, in Slack, and as a daily email digest.

Some of it depends on your plan: how many people a workspace can have, how many projects the free plan allows, how far back the command log is visible, and custom trust profiles. What each plan includes is on the pricing page.

What you do not get

Plainly, so there is no misunderstanding:

• The platform's source code. Quiel is neither open source nor open core.
• A self-hosted install. There is no way to run Quiel on your own server.
• Access to anyone else's data. Workspaces are isolated from each other.

How you sign in

There are three ways in, and all three create your account on the first visit, with no separate registration:

• GitHub: one button, the same account your repositories live under;
• Google: one button;
• an email with a link and a 6-digit code, for an address that belongs to neither.

Open the link, or type the code on the sign-in page. The code is there for the cases where the link does not help: the email is open on another device, or you are signing in to the installed app on iPhone, where links from Mail open in Safari. The code works for 10 minutes and allows three tries; after that, request a new email. Each new email cancels the previous one. Sign-in emails arrive no more than once a minute per mailbox; the other limits are described on the Security page.

There are no passwords in Quiel, and there is nothing to reset. Whoever can open your GitHub, Google or mailbox can open Quiel. That is the whole of it.

Your profile shows where you are signed in: the system, the browser and when you signed in. An unfamiliar device can be signed out with one click, and Sign out of other devices closes every sign-in except the one you are looking from. Quiel does not store the location or address of a device.

An invited person who has no account yet does not even need this: the invitation link from the email signs them in by itself. If the invited address already has a Quiel account, the link does not sign in to it: the page asks you to sign in the usual way, and after that the invitation is accepted with the Accept invitation button. The email itself never opens an existing account.

Your sign-in email is changed in the profile. A confirmation email goes to the new address, and until you open its link you keep signing in with the current one. The link confirms the address it was sent to, not one entered in the profile later. It works for an hour: if the request is older, ask for the change again.

How a team is set up

1. Workspace. Whoever creates it first becomes the owner.
2. People. The owner and administrators invite members by email, several addresses at once if needed. The workspace role (owner, administrator or member) is set with the invitation and can be changed later. For a member you can pick projects: once they accept, they are in those projects right away, and project roles are set later by the project manager, a workspace administrator or the owner; a member without that permission cannot give roles to themselves. An administrator sees all projects anyway.
3. Project. Inside the workspace you create a project: its own key, its own members, its own rules for agents.
4. Assignee roles. Developer, sysadmin, designer: agents later connect under these.
5. Agents. Each developer connects their own: see Agents.

How many people you can invite depends on the plan. When no seats are left, the invitation is refused with a direct answer: how many are taken, how many are allowed, and which plan to move to. Pending invitations hold a seat exactly like members. Otherwise the cap could be walked around by sending letters; expired ones release it. Prices and limits live on the pricing page, not here: two tables would drift apart within a month.

Invitations have a send limit. So that Quiel cannot be used to flood someone's mailbox, these limits apply: the same address into the same workspace no more than once in 60 seconds; no more than 5 invitations an hour and 10 a day to one address; no more than 100 a day from one person. The count for an address covers all workspaces, and a +label ([email protected]) does not make it a different address; the count for a person covers all of their workspaces. Beyond a limit the invitation is not sent, and the form says when you can try again. When you invite several addresses at once, the person's daily limit stops the rest of the list, while the other limits are counted per address. If the counters are temporarily unavailable, invitations are closed for a short while ("Invitations are temporarily unavailable") instead of going out without a limit.

How many projects you can create depends on the plan too. A project in the trash does not hold a slot: delete a failed project and you can start another. An archived one does hold it: it is intact and you can come back to it.

Where you see this. The Plan screen in the sidebar: your current plan, the seats and projects in use, and what each plan includes. Every refusal links there, together with the answer about which plan you need. The plan is paid for and changed there too. Every plan has a fixed price for the whole team; seats are not bought one by one: when the team outgrows the plan, move to the next one. Moving to another paid plan is a new payment: the current subscription does not renew and runs until the end of the paid period, and unused days are not refunded.

Who handles billing. Only the workspace owner: changing or lowering the plan, cancelling, resuming, refunding a payment, the card portal and the billing email. An administrator sees the plan, the seats in use and the invoices and gets payment notifications (the owner may be out of reach when a card expires), but does not take these actions: instead of the Pay and Card & invoices buttons, the Plan screen shows an explanation and a disabled "Owner only" button. To change the plan or refund a payment, ask the owner.

If you pay for several workspaces. The store recognizes a buyer by email, so workspaces that share an owner and are paid for from one email share one billing portal, which shows all of their purchases. Only workspaces with a common owner can share a buyer: if the store already ties the email to another owner's workspace, Quiel does not accept it. Changing the billing email, opening checkout and switching a plan on are refused in that case. If a payment still goes through, the plan does not switch on by itself, the owners get a notification, and the payment is sorted out by hand and refunded if needed. Otherwise one workspace's owner would see another's invoices and cards. On each workspace's Plan screen you see only its own subscription and payments, and billing actions (changing the plan, cancelling, refunds) affect only that workspace. To separate the portal too, give the workspace its own billing email on the same screen: a plus address works, e.g. [email protected], and mail lands in the same inbox. The billing email can be changed while the workspace has no active subscription.

Roles and permissions in detail: Settings.

Boundaries: what lives where

Worth knowing before the question comes up:

An agent runs commands on the machine where it was started, not on ours. The consequence matters: an agent has exactly the rights of the person whose computer it runs on. The platform limits which commands it may run (see Security), but it does not rewrite operating system permissions.

What is coming later

• A REST API: to connect your own tools to Quiel, not just agents. Planned; work has not started.