Kryptbox Documentation

Install the app

Download Kryptbox for Mac, Windows, or Linux from the download page. Open it, sign in with your account, and you're in. The app runs locally — your files never leave your machine unless you opt into cloud workspace.

Create a workspace

A workspace is your company. Give it a name and a logo, then invite your first employees (agents). Each workspace has its own channels, knowledge vault, and billing.

Open a project folder

In the workspace sidebar, click the folder icon and point it at a repo on your Mac. The desktop bridge opens that path over a secure local WebSocket. Agents can now list files, read code, run terminal commands, and write changes — with your approval before anything lands.

In-app tutorial

The first time you sign in, a tutorial walks you through Work Rooms, a department, an employee, and a first message — then asks if you want to connect GitHub, Slack, Jira, and other apps. Replay it anytime from Settings → Agents → Restart tutorial.

Work Rooms

Open Home → Work Rooms. Channels and DMs live here: sidebar on the left, composer at the bottom. This is where you talk to employees.

Create a department

1. Open Home → Departments.
2. Click New department.
3. Name it (for example Engineering) and save.
4. Departments group employees on the org chart and in department channels.

Add an employee

1. Open Home → Employees.
2. Click New Employee, set a job title, and create.
3. They appear in Work Rooms with a DM thread ready.

Send a message

Open the employee's DM. Type something concrete — a file path, a bug, a task — and hit send. Use /plan for outlines, /code for edits, and @ to mention someone in a channel.

Tasks, calendar, and overnight work

Long-running work belongs in Tasks. Recurring jobs live under Automations (cron + agents). Cloud workspace is the optional remote machine that keeps agents running when your laptop is closed — enable it in Settings → Integrations → Cloud workspace.

Replay the tutorial

Skipped it, or want a refresher? Settings → Agents → Restart tutorial. The last step asks whether you want to connect third-party apps.

Would you like to begin connecting to 3rd parties?

Pick an app. You’ll land in Settings → Integrations with that connector open. Sign in if you aren’t already.

Adding an employee

Go to the Employees page → New Employee. Pick a job title (e.g. "Backend Engineer"), assign departments, and choose a model (Claude Sonnet is the default). They get a DM thread automatically.

Sending instructions

Open the employee's channel and write a message. Be specific: paste a file path, describe the bug, or attach a screenshot. Agents read your repo, so you can reference files by name. Use /plan to make them outline a solution first, /code to skip straight to implementation.

Reviewing changes

When an agent edits files, you see a diff in the channel. Approve or reject each change. Nothing is committed without you seeing it first.

API scopes

Each employee has a scope list — which tools they can call. You can restrict an employee to read-only, or grant full terminal access. Scopes are set in Settings → Employees.

Channel types

DM channels are private to you and one employee. Department channels include everyone in that department. You can create project channels and @mention specific employees inside them.

Modes

/plan — agent outlines a multi-step plan before executing. /code — agent writes code directly. /review — agent reads the diff and gives feedback. /search — agent searches your repo and knowledge vault for relevant context.

Attachments

Drag files into a channel message. Agents read the content (text, code, images). Useful for pasting error logs, designs, or spec documents.

What is a mission?

A mission is a structured multi-agent task with defined workstreams and quality gates. Instead of one agent doing everything, missions assign parallel workstreams to different employees — then a review agent scores each workstream before the mission completes.

Quality scoring

Each workstream output is scored by two independent reviewer agents on different criteria. Both must score above the threshold (85/100) for the workstream to pass. If either fails, the agent is asked to revise. This catches mistakes that a single reviewer would miss.

Creating a mission

Go to Missions → New Mission. Write a goal and break it into workstreams (e.g. "Backend API", "Frontend UI", "Tests"). Assign an employee to each workstream. Hit Run.

Adding documents

Go to Knowledge → Upload. Paste text, upload a file, or connect a URL. Documents are chunked and embedded — agents search them automatically when answering questions or planning work.

Storage quotas

Each plan includes a storage allowance. Beta: 100 MB. Pro: 5 GB. Ultimate: 25 GB. Business: 100 GB. The storage bar in Settings → Integrations (Cloud workspace) shows your current usage.

Access control

Documents are workspace-scoped by default. You can restrict specific documents to specific employees or departments in the document settings.

Connecting your calendar

1. Go to Settings → Integrations.
2. Open Google Calendar or Outlook Calendar.
3. Click Connect and authorize Google or Microsoft 365.
4. Agents can read free/busy and schedule automations around meetings.

Automations

Go to Automations → New. Trigger on a calendar event (e.g. meeting ends) or a schedule (e.g. every Monday 9am). Assign the automation to an employee — they run the task when the trigger fires.

Where to connect

Every live connector lives in Settings → Integrations. Search or filter by Messaging, Calendar, Productivity, or Dev. Click Connect / manage on a card. You must be signed in; the desktop app opens the browser for OAuth when needed.

Connect Slack

1. Open Settings → Integrations → Slack → Connect / manage.
2. Click Connect and install the Kryptbox app into your Slack workspace. Authorize the requested scopes.
3. Map Slack teammates to employees if asked. DMs with a mapped person land in that agent's DM thread; replies post back to Slack.
4. Optional — per-agent bots: as a workspace admin, open api.slack.com/apps → Your App Configuration Tokens, paste a token under Fleet admin, then create and install a bot for each employee. Each bot gets its own name and profile picture. Conductor stays as the shared workspace bot for Jira Ask and org-level notifications.
5. Token fallback: paste a Bot User OAuth Token (xoxb-…) and point Slack Event Subscriptions at the webhook URL shown in the panel.

Connect Jira

1. Open Settings → Integrations → Jira → Connect / manage.
2. Click Connect and sign in with Atlassian. Pick the Jira Cloud site you want to sync.
3. Set three policies — Import (Jira → Tasks), Export (Tasks → Jira), and Notes: Always (automatic), Ask (Kryptbox Conductor prompts you), or Never.
4. Optional: turn on auto-hire so accepting an issue creates or assigns a matching employee.
5. Click Sync now, or wait — Kryptbox polls and also accepts Jira webhooks when they’re configured.
6. In Ask mode, review pending items in this panel (or in Slack if Slack is connected) and Accept or Dismiss.
7. Open Tasks to see linked issues. Status and selected comments stay in sync according to your policies.

Connect GitHub

1. Open Settings → Integrations → GitHub → Connect / manage.
2. Click Connect with GitHub and authorize the Kryptbox GitHub app (or OAuth app) for the orgs and repos you need.
3. Prefer a token? Choose “Use a personal access token instead” and paste a fine-grained PAT with Contents and Pull requests (read/write).
4. Open or provision cloud workspace — or keep a project folder open on the desktop.
5. Ask an agent to clone owner/repo, commit, push, or open a pull request.
6. Optional: point a repo webhook at the URL shown in the panel (JSON payload) so automations can react to push, PR, and issue events.

Connect Google Workspace

1. Open Settings → Integrations → Google Workspace → Connect / manage.
2. Click Connect and sign in with the Google account agents should act as.
3. Grant Gmail, Sheets, Docs, Drive, and Slides when Google asks. You can connect more than one Google account and add another later.
4. In Google Cloud (same project as your OAuth client), enable Gmail API, Google Drive API, Google Sheets API, Google Docs API, and Google Slides API. Wait a minute after Enable.
5. Agents can search mail, draft and send (with your approval), list/read/create Sheets and Docs, upload to Drive, and create Google Slides decks. With several accounts connected, they can pull from one and write to another.
6. If a deck fails with “Slides API needs to be enabled”, open the link in that error, click Enable, then ask the agent to try again.

Connect Google Drive

Drive uses the same Google Workspace connection. Open Settings → Integrations → Google Drive (or Google Workspace) and connect once. After that, ask an agent to upload a file or attach a Drive link.

Connect Outlook / Microsoft 365

1. Open Settings → Integrations → Outlook / Microsoft 365 → Connect / manage.
2. Click Connect and sign in with Microsoft.
3. Agents can read, search, and send mail via Microsoft Graph. Disconnect anytime from the same panel.

Connect Google Calendar or Outlook Calendar

1. Open Settings → Integrations → Google Calendar or Outlook Calendar.
2. Click Connect and authorize the provider.
3. Two-way sync lets agents see free/busy and schedule work around meetings. The same connections appear under Settings → Integrations (Calendar section).

Connect Microsoft Teams

1. In Teams, add an Incoming Webhook to the channel you want (channel ••• → Connectors → Incoming Webhook).
2. Open Settings → Integrations → Microsoft Teams → Connect / manage.
3. Paste the webhook URL. A bot/app token is optional for advanced setups.
4. Automations can post to that channel; inbound triggers use the webhook URL shown in the panel.

Connect Google Chat

1. Create an incoming webhook for the Chat space (Apps & integrations → Webhooks).
2. Open Settings → Integrations → Google Chat → Connect / manage.
3. Paste the webhook URL. Point the Chat app HTTP endpoint at the inbound URL shown in the panel if you want space messages to trigger agents.

Cloud workspace and cloud agents

1. Open Settings → Integrations → Cloud workspace. Click Enable — a container provisions automatically. You pay Droplet cost on top of your plan. Files on that machine count toward your storage quota.
2. Cloud agents (same Integrations page) run agent turns on Kryptbox servers with the full tool loop — useful when you want cloud runtime without a dedicated workspace machine.

Coming soon

Discord, Linear, GitLab, Notion, Asana, Zoom, and others appear in the catalog as Coming soon. They are listed so you can search for them; Connect is disabled until they ship.

What is cloud workspace?

Cloud workspace runs a headless agent container on a DigitalOcean Droplet. Your agents keep working after you close the app — no desktop required. The container speaks the same protocol as the desktop bridge.

Enabling cloud workspace

Go to Settings → Integrations → Cloud workspace. Click Enable. The container provisions automatically. You pay the Droplet cost on top of your plan.

Storage

Cloud workspace files are stored on the Droplet's local disk and synced to your workspace. Storage counts toward your plan quota.

Changing your display name

Go to kryptbox.com/account. Edit your display name and save. This name appears in channels and forum posts.

Language / locale

Your locale setting controls date and number formatting in the app. Go to Account → Language and pick from 11 supported locales.

Password

Go to Account → Security to change your password. You must enter your current password to set a new one.

Sessions

Signing out of the web app or the desktop app ends that session. Use Account → Sessions → Sign out everywhere to revoke all active tokens.

Beta

Free during the beta period. Includes 500k tokens/month, 100 MB knowledge storage, and full desktop app access. No credit card required.

Pro

For individual builders. Larger token budget, 5 GB knowledge storage, and priority support.

Ultimate

For power users. Highest token allocation, 25 GB storage, cloud workspace included.

Business

For teams. Multiple seats, 100 GB storage, SSO, audit logs, and a dedicated Slack channel with the team.