Skip to documentation
Documentation
Documentation
OverviewInstallationQuickstartYour first dayYou were sent a linkWorking with a customerConfigurationTroubleshootingFAQGlossary

Usage

Terminal interfaceCLIStatuslineDashboardAnalytics

Collaborate

DocumentsLessonsSession sharingPicking up tomorrow and handing work overFrom your phoneSession linksSession messagingAsksAsks privacy fact sheetFeedbackEmail from crewkitBlueprintsAgent identitiesMCP server

Configure

AgentsSkillsSkill and agent security scanningRulesCommandsInheritancePlaybooksExperimentsHooksCapture modesSensitive sessionsData residencyTeamSettings mapIntegrations

Workspaces

WorkspacesSet up a workspaceFix a ticket end to endShip a feature with approvalHand off work and set agent settings

API Reference

API OverviewAuthenticationSessions APIResources APIOrganizations APIProjects APIPlaybooks APIExperiments API
Need a hand?Find an answer in troubleshooting.
Loading docs…
CREWKIT / DOCUMENTATION

You were sent a link

For someone with no crewkit account who opened a crewkit link, what the page is, what you can do there, who reads what you send, and how to erase it.

Someone on a team that uses crewkit sent you a link. You do not need an account to open it. crewkit is where a software team keeps the context of its work with AI agents. The team that sent the link is the organization named on the page.

Each link leads to one of three pages. Find yours:

  • A set of questions to answer: its address is on asks.crewkit.io.
  • A conversation to read: the address has /shared/ in it.
  • A feedback panel in an app you are testing: a button inside someone else's app, before its release.

A set of questions to answer

What this page is

The team calls a set of questions an Ask (see the glossary). You are its Respondent: the person who answers it through its link (glossary). The page names the organization that asks and says that crewkit hosts the page. It shows a notice, in English and French, about what happens to your answers. The questions come in English, French or both; when both, you answer in the one you choose.

What you can do

  • Answer. You send your answers and a name you type. If the link was made for you, the page shows the name the team put on it: your answers are recorded under that name, and you cannot change it.
  • Choose how to answer, if you are already signed in to crewkit in that browser and the link was not made for you. With my crewkit account records your answers under your account's display name; the team does not see your email address or your organization. With a name I type records them under a name you type, with no tie to your account. Either way, the team sees that name and when you answered. No other sign-in step is asked of you.
  • Report this page, while the Ask is open, if it looks wrong or abusive. Your report goes to crewkit's staff, who can take the page down. The organization's admins are told the page was reported, not by whom. The report is not deleted with your Response.
  • Use your private link. After you answer, you keep a private link to your Response, which is your set of answers (glossary). With it you can:
    • read and change your answers while the Ask is open. Each change is a new version, and the earlier one is kept. The name you gave stays as it was;
    • add screenshots with Add screenshots while the Ask is open: up to 5 images, 10 MB each;
    • download your Response as a JSON file, with every version of it, also after the Ask closes;

Your first day

Where to start in crewkit for a developer, a manager, an admin, and someone who was sent a link.

Working with a customer

For a team building in its customer's repository, every route a customer with no crewkit account has today, what each one stores, which providers see it, how long it is kept and who on your team reads it.

On this page

A set of questions to answerWhat this page isWhat you can doWho reads what you sendHow long it is kept, and how to erase it soonerA conversation to readWhat this page isWhat you can doWho reads what you sendHow long it is keptA feedback panel in an appWhat this panel isWhat you can doWho reads what you sendHow long it is kept, and how to erase it soonerReading more often
  • erase it, at any time, also after the Ask closes.
  • Anyone who holds your private link can do the same, so keep it to yourself. That browser remembers the link, so anyone who uses that browser can open your Response.

    Who reads what you send

    • Every member of the organization that sent the Ask can read the Responses and their screenshots in crewkit.
    • An owner or admin of that organization can download the results as a file.
    • The team's AI agents read your answers only after a person in the organization confirms them. In what an agent reads, you are a number, not your name. What you wrote can still say who you are.
    • crewkit's Ask code does not send your answers to an AI model. Once confirmed answers are read in the team's AI sessions, those sessions can be summarized and analyzed by Anthropic and indexed for search by Voyage AI, under the organization's settings. The notice on the page names both.

    How long it is kept, and how to erase it sooner

    • Your Response is deleted once the organization's retention period has passed since the Ask closed. The period is 180 days unless an admin set it between 30 and 365 days.
    • crewkit does not keep your network address. It keeps a code computed from it, for 30 days, to limit abuse.
    • To erase your Response sooner, use your private link. Erasing removes every version of it and every confirmed copy in crewkit. Copies already read into the team's AI sessions follow those sessions' retention, and a file an owner or admin already downloaded stays with them. What you erase or delete stays in crewkit's database backups for about 7 days, until they expire.
    • If you lost the link, write to the organization that sent you the Ask, or to the privacy officer its notice names: it can erase your Response.

    A conversation to read

    What this page is

    A share link shows one conversation between a member of the team and Claude Code, an AI coding assistant (glossary). The person who shared it chose how much you see: a summary (the title, a summary written by an AI model, its status, outcome and dates); or also the turn-by-turn transcript with its cost and model; or also its token counts, git branch and suggested improvements. Some conversations take in a meeting transcript. For those, the content is held back, and you see the details without the summary or the transcript.

    What you can do

    • Read the conversation, and the comments the team left on it.
    • Commenting is for signed-in members of the organization; you cannot comment.
    • A link set for the organization's members does not open for you. Ask the sender for a public link.

    The link stops working when it expires, when the sender revokes it, or when the team restricts the conversation.

    Who reads what you send

    You send nothing through this page, and it does not ask who you are. crewkit counts each time the link is opened, and does not record who opened it.

    How long it is kept

    There is nothing of yours to erase here. The conversation belongs to the team; ask the sender if you want the link taken down.

    A feedback panel in an app

    What this panel is

    A team testing its app before release can add crewkit's feedback panel to it. You are a Visitor: someone using that app who sends the team a message through the panel (see Feedback in the glossary). Before you send, the panel shows a short notice in English or French, with the full text behind How your feedback is used.

    What you can do

    • Send a message with your name and email; the panel asks for both. If the app filled them in, you can change them before you send. The panel also records the address of the page you are on, with any query parameters the team chose to keep and no others, your browser and system, your screen size, the app's release and your language. When the team has turned it on, it also records the identifiers of your Sentry session replay and of the last error you saw, which the team opens as links.
    • Add a screenshot of the page, when the team has turned screenshots on. None is taken unless you choose one, and you can black out parts of it before you send.
    • See or erase what you sent, at any time, with the private link you receive after sending, or with Delete what I sent while the panel is open.
    • Write to the contact the notice names.

    Who reads what you send

    • Members of the team with crewkit's Developer role or above, or its Feedback triage role, read new reports, with your name and email. crewkit records each time one of them opens your report with your name and email, without recording either.
    • Once someone on the team confirms your report, the team's AI agents can read it through crewkit's feedback tools. They do not see your name, your email or your screenshot.
    • When someone on the team confirms your report, crewkit also makes a copy for the team's agents to search: your message, the date you sent it, the page address, with any query parameters the team chose to keep, the app's release, your screen size, your browser and system, the name of the app's test environment, whether a screenshot exists, and how many people sent the same report. crewkit sends that copy to Voyage AI to index it for search. There is no such copy when the organization keeps its data on servers it runs itself, and it is not sent to Voyage AI when the organization has turned off sending its content to outside providers or has limited what crewkit collects.
    • An agent session that reads a confirmed report is handled as that organization's sessions are, which can include a summary and analysis by Anthropic and indexing for search by Voyage AI.
    • If the organization turns on a setting that is off by default, an AI agent may read a report before it is confirmed, to help the team sort it. A person still decides, and what the agent read stays in that team member's session.
    • The notice says your information may be communicated outside Québec.

    How long it is kept, and how to erase it sooner

    • A report nobody on the team confirms is deleted 30 days after you send it. When a report the team grouped others under is erased, the oldest of those others goes back to unconfirmed, its 30 days start again, and the rest are grouped under it; it is still deleted when the confirmed period below has passed.
    • A confirmed report is deleted 180 days after you send it, unless the organization set a period between 30 and 365 days.
    • crewkit does not keep your network address. It keeps a code computed from it, for 30 days, to limit abuse.
    • Erasing removes your report and the copy the team's agents search. It cannot remove what an agent already quoted in a team member's session. What you erase or delete stays in crewkit's database backups for about 7 days, until they expire.

    Reading more often

    If a team wants you to read its work in crewkit often, it can invite you as a Viewer instead. What a Viewer costs is on the pricing page.