# Koshra: full text > Every page of https://koshra.si as Markdown, in one file. Short index: https://koshra.si/llms.txt The demo content on the site (chats, tasks, the floor illustration and the app replica) is scripted. No model is called and nothing is sent. # Koshra: your AI team, and everything it knows > A server-hosted workspace for role-based bots, shared context and reviewed actions. Cloud is in assisted preview. Mac is an unreleased local prototype. Canonical: https://koshra.si/ Last updated: 2026-11-07 ## Overview Your AI team, with you in control. A server-hosted workspace for role-based bots, shared context and reviewed actions. Cloud is in assisted preview. Mac is an unreleased local prototype. Dedicated per-bot computers, complete automated Plays and fully validated restart and reconnection are coming soon. Explore the scripted demo or ask for a walkthrough. ## How a request moves 1. You ask in plain words, in a chat or on the tasks board. 2. In enabled spaces, a dispatcher can show a plan card with its reasons, the assigned bots and a countdown you can stop. 3. A task can have one owner bot and move across the tasks board. 4. Review drafts before use. The limited Plays email action requires explicit owner approval. 5. Shared notes live in a Brain you can edit, with revision history. Advanced Knowledge retrieval is coming soon. ## Team An AI team with defined roles, shared context and a task board. chief_of_staff, leads and desks each have a written job. In enabled spaces, a dispatcher can plan and assign work for review. Not every task is necessarily dispatcher-managed. ## Cloud, Mac and computers Koshra Cloud is the server-hosted web app, in assisted preview. Koshra for Mac is coming soon: an unsigned local prototype, not a released app. Cloud and Mac are intended to work independently; optional linking is not available yet. Bots currently use shared cloud computers. Dedicated per-bot computers and fully validated live viewing are coming soon. Cloud computer isolation has passed bounded synthetic checks. Full supervisor restart and reconnection acceptance is unfinished. Mac OS-enforced sandboxing is coming soon. ## Plays and workflows Plays is a preview catalog. Supported actions are limited to owner-staged email and Twenty company creation, with a separate explicit approval. Automated recipes and scheduled or chat-generated play actions are coming soon. The workflows on this site are examples for assisted setup. Fully automated, end-to-end validated recipes are coming soon. ## Demo The interactive demo is scripted. It makes no model calls and takes no external actions. --- # Koshra app replica > A clickable replica of the Koshra app with scripted data: the tasks board, a dispatcher plan card and an approval card. Canonical: https://koshra.si/demo Last updated: 2026-11-07 This page is a clickable replica of the Koshra app. Everything in it is scripted demo data: no model is called and nothing is sent. - Chat: ask chief_of_staff for work and watch the dispatcher plan card count down. Stop it to change the plan. - Tasks board: tasks move from Planned to Working to Waiting on you to Done, each with one owner bot. - Approvals: an outbound email waits on an approval card until you answer Allow or Deny. To see the real app on your own work, book a demo: https://cal.lumenlab.tech/rasul/30min --- # Getting started with Koshra > How to get a Koshra space, sign in, meet your AI team and give it its first task. Canonical: https://koshra.si/docs Last updated: 2026-11-07 Koshra is a server-hosted workspace for role-based bots. This guide takes you from an assisted setup to a first task you review. ## 1. Get a space (coming soon) Koshra is in private preview. There is no self-serve sign-up yet, so a space is set up with you on a short call. Book a demo and we will walk through the team you need. ## 2. Sign in Koshra is a responsive web app. Open it in any browser on your laptop or phone and sign in. Protected pages and API routes refuse any request without a signed-in session. ## 3. Meet the team Your space comes with a team of AI employees, each with a defined job. A chief_of_staff bot sits at the top, with leads and desks under it, such as research_lead or outbound_desk. Each lead has a team chat where its desks work together. [Read about AI employees](https://koshra.si/docs/ai_employees) ## 4. Name the work Ask in chat, or add a task on the tasks board. The dispatcher shows a plan card with its reasons, the bots it picked and a countdown you can stop. Each task gets one owner bot. [Read about the dispatcher and tasks](https://koshra.si/docs/dispatcher_and_tasks) ## 5. Review what goes out Review drafts before use. The limited Plays email action requires explicit owner approval. Ordinary connector actions follow configured tool rules. End-to-end coverage of every outbound path is not yet verified. Web Push depends on the browser and device. [Read about approvals and permission modes](https://koshra.si/docs/approvals) ## 6. Teach it what you know Write the facts your team should share into the Brain, a shared store you edit as text with versioned undo. Each bot also keeps its own memory. [Read about memory](https://koshra.si/docs/memory) --- # AI employees > How Koshra's AI employees are organised: chief_of_staff, leads, desks, team chats and handoffs. Canonical: https://koshra.si/docs/ai_employees Last updated: 2026-11-07 Every bot in Koshra is an AI employee with a role name, a written job, its own model and its own memory. ## Roles, not personas Bots are named for the job they do, in lowercase snake_case: chief_of_staff, research_lead, client_lead, outbound_desk, decision_desk and so on. The role name is what you see in chats, on tasks and on approval cards. ## Leads and desks chief_of_staff sits at the top. Leads own an area of work and desks do focused jobs inside it. Each lead has a team chat with its desks, with the lead listed first. ## Handoffs Bots can message each other, hand work to the bot that owns it and run a subagent for a side job. Handoffs are capped per task so work cannot bounce between bots forever. [See the loop guards](https://koshra.si/docs/dispatcher_and_tasks) ## Creating new bots Only chief_of_staff and a small set of leads may create new bots, and every new bot needs your approval first. ## Routines A bot can run a routine on a schedule, for example a Brain sync three times a day that proposes updates for your review. Routines run on the server, so they keep going when your laptop is closed. Creating or changing a schedule needs your approval. ## Modes and looks Each bot has its own permission mode and its own look in the app, so you can tell at a glance who is working on what. --- # Dispatcher and tasks > How Koshra plans work with a plan card and countdown, assigns one owner bot per task and guards against loops and overspend. Canonical: https://koshra.si/docs/dispatcher_and_tasks Last updated: 2026-11-07 The dispatcher turns a request into tasks, picks the bot that owns each one and shows you the plan before it starts. ## Plan card Before work starts you see a plan card with the dispatcher's reasons, the bots it assigned and a countdown. Stop the countdown to change the plan. ## One owner per task Every task has exactly one owner bot. From the task you can tell it to continue, retry it, or reassign it. Only the dispatcher bot, the space owner or an admin may reassign a task; anyone else is refused before anything changes. ## Tasks board Tasks move across the tasks board as they go, with their owner and status. Tasks you add by hand on the board get the same policy checks and limits as dispatched ones. ## Branch from any message Branch a chat from any message to try another direction without losing the original thread. ## Limits and loop guards Every dispatch has a spend cap, a token cap, a cap on handoffs and a cap on runs. The stored defaults are 0.5 USD, 200,000 tokens, 3 hops and 8 runs. A loop guard stops ping-pong between two bots and repeat visits to the same bot. ## Stuck runs A bar shows runs that have stopped moving, with a cancel button. You set how long counts as stuck. A run that waits for your input expires after 48 hours. ## Per-space switch The dispatcher and tasks board are switched on per space. Ask us to turn them on for yours. ## Client console (coming soon) A console for clients, built on the open AG-UI protocol, streams runs live and lets people answer approvals. It is in testing. --- # Approvals and permission modes > How Koshra's Allow, Ask and Block rules, approval cards and per-bot permission modes keep a person in charge of anything that goes out. Canonical: https://koshra.si/docs/approvals Last updated: 2026-11-07 Koshra drafts; you decide. Every tool call is checked against rules before it runs. ## Allow, Ask, Block Each tool has a rule: Allow runs it, Ask stops for your approval, Block refuses it. Rules can be set for your account and for each space. ## Approval cards When a rule says Ask, the bot pauses and an approval card appears with what it wants to do. You answer Allow or Deny. Web Push alerts can reach your phone, and the approvals inbox only shows cards to the space owner and admins. ## What configured rules hold - The limited Plays email action, which needs explicit owner approval - Creating a new bot, where that rule is configured - Creating or changing a schedule, where that rule is configured - Bulk CRM changes above the configured threshold ## What configured rules block - Destructive CRM operations on the paths that implement the rule - HubSpot and arbitrary CRM play writes, which are not supported - Plays actions other than owner-staged email and typed Twenty company creation ## Permission modes Each bot has a permission mode on top of the rules. A mode can make a bot stricter, never looser than the rules allow. --- # Memory: the Brain and per-bot memory > How Koshra stores shared knowledge in the Brain and keeps a separate memory for each bot. Canonical: https://koshra.si/docs/memory Last updated: 2026-11-07 Koshra keeps two kinds of memory: one shared Brain for the whole team, and a private memory for each bot. ## The Brain Brain editing and search are available. Revisions can be undone where that feature is enabled for the space. Advanced Knowledge retrieval is coming soon: quality, latency and restart or persistence acceptance remain incomplete. Do not treat any published score as fractional recall. ## Brain sync A routine reads recent work and proposes Brain updates. It does not write on its own: proposals wait for your review. ## Per-bot memory Each bot has its own memory bank. It keeps what the bot learns and recalls it in later chats. ## Where it lives Both kinds of memory live on the server that runs Koshra, next to the rest of your data. [Read about self-hosting](https://koshra.si/docs/self_hosting) --- # Integrations > How Koshra bots connect to tools through MCP servers and app connections, each limited to what the bot needs. Canonical: https://koshra.si/docs/integrations Last updated: 2026-11-07 Bots reach your tools through MCP servers and app connections, and each bot only gets the tools its job needs. ## MCP servers Koshra speaks the Model Context Protocol. Add an MCP server to a bot and its tools appear for that bot, under the same Allow, Ask and Block rules as everything else. ## App connections App connections give bots access to services such as Slack, email and a CRM. Connections are locked down per bot: a bot only gets what its role needs. ## Email and Slack Bots can draft email and Slack messages. Anything outbound waits for your approval. ## CRM and project tracker Bots can read and update your CRM and project tracker. Deletes and merges are blocked, and bulk changes need approval. ## App catalog MCP and app-connection adapters are implemented. A catalog row, including Salesforce, Zendesk, Jira or Microsoft Teams, does not mean that app is connected or tested. Each connection needs setup, permission review and validation. ## Cloud computers Bots currently use shared cloud computers, with distinct home paths. Dedicated per-bot computers and fully validated live viewing are coming soon. Full supervisor restart and reconnection acceptance is unfinished. ## On the way (coming soon) - A validated visible browser for each bot - Mac OS-enforced sandboxing - X (Twitter) sign-in for bots --- # Models and cost per reply > How Koshra lets you pick a model per bot, switch mid-chat, keep a backup chain and see the model, cost and time of every reply. Canonical: https://koshra.si/docs/models_and_cost Last updated: 2026-11-07 You choose the model for each bot, and every reply tells you what it cost. ## A model per bot Each bot has its own model. Leads can run a larger model and desks a smaller one. ## Switch mid-chat Change the model from the picker in the chat composer. The next reply uses the new model. ## Backup chain Behind each model sits a backup chain. If a provider is down or out of credit, the next model in the chain answers. ## Usage estimates Per-bot model selection, mid-chat switching and fallback configuration are implemented. A reply can show a model, a cost estimate and time when the provider reports them. That is not a fresh acceptance of every provider. [See dispatch limits](https://koshra.si/docs/dispatcher_and_tasks) ## Free open models Choose supported model providers or bring an API key. Some providers offer free-tier models; availability is not guaranteed. Provider charges, quotas and data policies apply. ## Not locked to one model Bring your own key for OpenAI, Anthropic, Google, OpenRouter, MiniMax or any OpenAI-compatible endpoint. Keys are stored encrypted and shown masked. Fallback chains can end on free models. ## Sign in with your existing AI plan (coming soon) Using a Claude or ChatGPT plan you already pay for, instead of an API key. --- # Self-hosting and security > How Koshra runs as a self-hosted Docker stack, how sessions and secrets are handled and where your data lives. Canonical: https://koshra.si/docs/self_hosting Last updated: 2026-11-07 Koshra runs on a server you control, next to the tools your team already uses. ## Own your AI team Run a server-hosted Koshra deployment with assisted setup. It is built on an Apache-2.0-licensed foundation. Koshra distribution and support are separate agreed terms. Security has the limits. ## The stack Koshra runs as a small set of Docker containers: a web app, an API, a background worker, a supervisor and a Postgres database. Routines and tasks run on the server around the clock, not on a laptop. ## Sessions Protected pages and API routes refuse requests without a signed-in session. The task and dispatcher routes also refuse requests from untrusted origins. ## Secrets Provider keys and other credentials are kept in the app's encrypted secret store, not in chat or prompts. ## Your data Chats, tasks, the Brain and bot memory are stored in the database on your server. Model calls go to the model provider you chose for that bot. ## Changes Assisted self-hosting is available by arrangement. Production changes should have a reviewed backup and rollback plan. That is not a claim that every past change had one. --- # Routines: work on a schedule > How Koshra bots run routines on a schedule on the server, why every new schedule needs your approval and how a routine is written first as a checklist. Canonical: https://koshra.si/docs/routines Last updated: 2026-11-07 A routine is work a bot does on a schedule. It runs on the server, so it keeps going when your laptop is closed. ## What a routine is A routine is a task a bot repeats on a schedule, such as a morning list or a weekly scan. It runs on the Koshra server, not on your computer. ## Write it first, schedule it second routines_desk writes a routine as a checklist with an owner and a stop condition. That checklist is a plan: nothing is scheduled until you ask for the schedule. ## Every schedule needs you Creating or changing a schedule always waits on an approval card. A bot cannot quietly start running work on its own timetable. [Read about approvals](https://koshra.si/docs/approvals) ## Brain sync One routine we run reads recent work three times a day and proposes Brain updates. The proposals wait for your review before anything is written. [Read about memory](https://koshra.si/docs/memory) ## Same limits as any task A routine's runs get the same spend cap, handoff cap and loop guard as a dispatched task, and a routine that stops moving shows up in the stuck-run bar. [See the limits](https://koshra.si/docs/dispatcher_and_tasks) ## Triggers other than time (coming soon) Starting a routine from an event, such as an incoming webhook, instead of a clock. --- # Team chats and handoffs > How Koshra leads and desks work together in team chats, hand work to the bot that owns it and stay inside handoff caps and loop guards. Canonical: https://koshra.si/docs/team_chats_and_handoffs Last updated: 2026-11-07 Bots in Koshra work like a team: a lead and its desks share a chat, and work moves to the bot that owns it. ## Team chats Each lead has a team chat with its desks, with the lead listed first. You can read along and step in at any point. ## Bots message each other A bot can message another bot, hand a task to the bot that owns it or run a subagent for a side job, then bring the result back. ## One owner at a time A handoff moves ownership. The task always has exactly one owner bot, which is the one you see on the tasks board. ## Caps and loop guards Handoffs are capped per task, with a default of 3 hops. A loop guard stops two bots passing work back and forth and stops repeat visits to the same bot. ## You stay in the loop Anything outbound a team produces still waits on an approval card, whichever bot wrote it. [Read about approvals](https://koshra.si/docs/approvals) --- # Branching chats > How to branch a Koshra chat from any message to try another direction or another model without losing the original thread. Canonical: https://koshra.si/docs/branching Last updated: 2026-11-07 Branch from any message to try a different direction. The original thread stays as it was. ## Branch from any message Pick a message and branch. Koshra starts a new thread from that point, with everything before it, and leaves the original untouched. ## Try another model Combine a branch with the model picker to see how a different model handles the same point in the conversation. Every reply shows its model, cost and time, so the comparison is plain. [Read about models and cost](https://koshra.si/docs/models_and_cost) ## Keep what works Carry on in whichever thread worked better. Nothing is merged or overwritten for you. --- # Phone and alerts > How Koshra works on your phone as a responsive web app, with Web Push alerts and an approvals inbox for anything that needs you. Canonical: https://koshra.si/docs/phone_and_alerts Last updated: 2026-11-07 Koshra is a responsive web app, so your phone works as well as your laptop, and Web Push tells you when a bot needs you. ## Any browser Open Koshra in the browser on your phone and sign in. Chats, the tasks board and approvals all fit a small screen. ## Web Push alerts Web Push availability depends on browser and device permission and configuration. Fresh delivery is not claimed. ## The approvals inbox Every waiting card is collected in one approvals inbox. Only the space owner and admins see it. [Read about approvals](https://koshra.si/docs/approvals) ## Native apps (coming soon) There is no native iOS or Android app. Koshra runs in the browser. --- # Koshra REST API and MCP server > Hand work to Koshra from other agents: scoped API keys, a REST API with an OpenAPI 3.1 spec, an MCP server and the safety rules that still apply. Canonical: https://koshra.si/docs/api_and_mcp Last updated: 2026-11-07 Other agents can list your Koshra bots, read the Tasks board, check a task and hand Koshra new work, through a REST API or an MCP server, with a key a space admin makes. ## Get a key A space owner or admin opens API & MCP in Koshra, names a key and picks its scopes. The key is shown once, and Koshra stores only a hash of it. A key acts as the admin who made it, in that one space only, and stops working if that person leaves the space or stops being an admin. Revoke it on the same page. Each key is limited to 120 requests a minute. - bots:read: list bots - tasks:read: read the Tasks board and task status - tasks:write: make plans and start allowed work ## REST API Send the key as Authorization: Bearer. The endpoints live under https://app.koshra.com/api/koshra/v1, described by an OpenAPI 3.1 spec at /api/koshra/v1/openapi.json on the app. - GET /me: the key's space and scopes - GET /bots: bots with their model and permission mode - GET /tasks: the Tasks board, with columns, items, owner bot and status - POST /tasks: make a plan for a task, and start it if policy allows - GET /tasks/{id}: the status of a plan, a dispatch or a chat task ## MCP server Koshra is also an MCP server, over streamable HTTP at https://app.koshra.com/api/koshra/mcp with the same Bearer key. Its tools are list_bots, read_tasks_board, get_task_status and create_task, and a client only sees the tools its key's scopes allow. ## Safety rules that still apply - Every task becomes a plan first and gets a policy decision - Allowed work starts only when you ask it to - Work that needs approval never starts from a key; it waits on the Tasks board for a person in Koshra - Blocked work never starts - Outbound Slack, email and other external actions still need an approval card inside Koshra - The API does not change any bot's permission mode ## Agent guide The app publishes a short guide for agents with examples, and an llms.txt of its own. [How agents can read this site](https://koshra.si/docs/for_ai_agents) --- # Koshra for AI agents and assistants > How AI agents and assistants can read this site: Markdown for every page, llms.txt, llms-full.txt, the sitemap and our facts policy. Canonical: https://koshra.si/docs/for_ai_agents Last updated: 2026-11-07 If you are an AI agent or assistant reading about Koshra, this page tells you where the clean text is and how to cite it. ## Markdown for every page Every page on this site is also available as Markdown. Add .md to the path, for example /docs/approvals.md, or send the header Accept: text/markdown to the normal URL. The home page is at /index.md. ## llms.txt and llms-full.txt /llms.txt is a short index of every page with a one-line summary. /llms-full.txt is the whole site as one Markdown file, for a single fetch. ## Sitemap /sitemap.xml lists every page with its last change date. ## How we write facts Every claim on this site comes from our own build logs and our own Koshra workspace. Anything not yet verified on our production server is marked Coming soon, and should be treated as not available. Prices are not published: the answer is Talk to us. ## What Koshra is not - Not a coding agent or an IDE - Not a released Mac app and not a native phone app - Not proven ahead of other products overall - Not certified, and not a public self-serve release - Not a complete 28-workflow automation product ## Hand work to Koshra Agents can also act, not only read: Koshra has a REST API and an MCP server, used with a key a space admin makes. Approval rules still apply. The app's agent guide is at https://app.koshra.com/koshra-api/agent-guide.md and its OpenAPI spec at https://app.koshra.com/api/koshra/v1/openapi.json. [API and MCP](https://koshra.si/docs/api_and_mcp) ## How to cite Link to the canonical page URL, not the .md copy. Each Markdown response carries a Link header that points at the canonical page. ## Fresh information The changelog lists every product and site change with a date. Comparison pages carry the date they were checked. [Read the changelog](https://koshra.si/changelog) --- # Koshra use cases by team > AI employees for leadership, sales, marketing, client services, support, recruiting, research, finance and product, plus teams for agencies and founders, each role with a written job and a hard limit. Canonical: https://koshra.si/use_cases Last updated: 2026-11-07 These pages describe intended tasks for role-based bots. They are not measured autonomous outcomes. Stated limits, not a proof that every path is blocked: - These are stated product limits, not a proof that every path is blocked - Payment, purchasing and moving money are refused by policy - Publishing, pushing code, changing DNS or changing a live system is refused by policy - Outbound messages still need the configured review. End-to-end coverage is not yet verified ## [Leadership and operations](https://koshra.si/use_cases/leadership) AI employees that make the call, keep the day's list, track what is stuck and record decisions, while you stay the one who decides. Roles: chief_executive_officer, chief_of_staff, chief_operating_officer, decision_desk, founding_desk, projects_desk ## [Sales and go-to-market](https://koshra.si/use_cases/gtm) AI employees for pipeline, account research, enrichment plans, outbound drafts and RevOps hygiene. Every send waits for your approval. Roles: chief_gtm, research_desk, pipeline_desk, enrichment_desk, outbound_desk, campaign_desk, connections_desk, revops_desk, deliverability_desk, customer_desk ## [Marketing, content and launches](https://koshra.si/use_cases/marketing) AI employees that turn a true customer fact into briefs and channel drafts for X, YouTube and community replies, plan launch day and watch mentions. You publish. Roles: chief_marketing_officer, chief_growth_officer, x_desk, youtube_desk, repurpose_desk, mentions_desk, content_community, content_video_editor, launch_day, launch_press_list ## [Client services](https://koshra.si/use_cases/client_services) AI employees that coordinate client proposals, delivery plans and follow-ups from request to signed scope. Roles: client_lead, client_proposal_writer ## [Customer support](https://koshra.si/use_cases/support) AI employees that sort incoming customer questions, draft answers from your docs and hand you the ones that need your decision. Roles: support_lead, support_triage, support_answers, support_escalations ## [Recruiting](https://koshra.si/use_cases/recruiting) AI employees that define the next hire, source and score candidates against an approved scorecard and book first calls. Roles: talent_desk, recruiting_sourcer, recruiting_screener, recruiting_scheduler ## [Research](https://koshra.si/use_cases/research) AI employees that produce source-grounded answers, check every material claim against its source and name the gaps. Roles: research_lead, research_evidence_reviewer, distill_desk ## [Finance and funding](https://koshra.si/use_cases/finance) AI employees that watch spend and runway, check whether a number is real and draft funder updates from checked figures. Roles: chief_financial_officer, funder_desk ## [Product, platform and security](https://koshra.si/use_cases/product_platform) AI employees that scope the smallest version, design one surface at a time, build within the AI rules, review plans for security and draft term reviews. Roles: product_lead, design_desk, platform_lead, chief_ai_officer, chief_security_officer, counsel, routines_desk ## [Agencies](https://koshra.si/use_cases/agencies) AI employees for agencies that run work for many clients: research, proposals, outreach and content, on a server you control, under a licence you can resell. Roles: client_lead, client_proposal_writer, research_desk, pipeline_desk, outbound_desk, repurpose_desk, chief_of_staff ## [Founders](https://koshra.si/use_cases/founders) AI employees for founders and small teams: a chief of staff, decision notes, investor updates and go-to-market, with you approving what goes out. Roles: chief_executive_officer, chief_of_staff, decision_desk, founding_desk, chief_financial_officer, funder_desk, chief_gtm --- # AI employees for leadership and operations > AI employees that make the call, keep the day's list, track what is stuck and record decisions, while you stay the one who decides. Canonical: https://koshra.si/use_cases/leadership Last updated: 2026-11-07 A leadership bench of AI employees: one makes the call, one keeps the list, one chases what is stuck and one writes the decision down. ## How the work moves 1. You ask chief_of_staff what matters today. 2. chief_of_staff names the officer, the desk and the next step for each item. 3. chief_operating_officer names what is stuck and the next check; projects_desk keeps owners and dates. 4. decision_desk records each call, the reason and what must not happen. ## Roles in this team - [chief_executive_officer](https://koshra.si/roles/chief_executive_officer): Make the company call. Name the officer who owns it, and name what the company will not do. - [chief_of_staff](https://koshra.si/roles/chief_of_staff): Prepare the day's list. Name the officer, the desk and the next step for each item. - [chief_operating_officer](https://koshra.si/roles/chief_operating_officer): Name what is stuck, who has it and the next check. - [decision_desk](https://koshra.si/roles/decision_desk): Record a decision, the reason, who asked and what must not happen. - [founding_desk](https://koshra.si/roles/founding_desk): Keep the founding brief: who you serve, the promise and what is off strategy. - [projects_desk](https://koshra.si/roles/projects_desk): Track what is in flight, what is blocked and the next date. ## What a bot never does - These are stated product limits, not a proof that every path is blocked - Payment, purchasing and moving money are refused by policy - Publishing, pushing code, changing DNS or changing a live system is refused by policy - Outbound messages still need the configured review. End-to-end coverage is not yet verified --- # AI employees for sales and go-to-market > AI employees for pipeline, account research, enrichment plans, outbound drafts and RevOps hygiene. Every send waits for your approval. Canonical: https://koshra.si/use_cases/gtm Last updated: 2026-11-07 A revenue team where every desk drafts and nothing is sent without you: research, pipeline, enrichment, outbound, campaigns and RevOps. ## How the work moves 1. chief_gtm chooses the account, the offer and which desk works it. 2. research_desk returns sourced facts on that one account. 3. enrichment_desk writes the enrichment plan, and pipeline_desk keeps the list deduped and staged. 4. outbound_desk drafts the sequence. It waits on an approval card until you send it. 5. revops_desk flags rows that break your stage and field rules. Writebacks need your approval. ## Roles in this team - [chief_gtm](https://koshra.si/roles/chief_gtm): Choose the account, the offer and which revenue desk works it. - [research_desk](https://koshra.si/roles/research_desk): Research one account at a time and return facts with sources. - [pipeline_desk](https://koshra.si/roles/pipeline_desk): Keep the account and people list current, deduped and staged. - [enrichment_desk](https://koshra.si/roles/enrichment_desk): Write the enrichment plan: Clay columns, the catch-all verification rule and the dedup key. - [outbound_desk](https://koshra.si/roles/outbound_desk): Draft the sequence for a named account and a named offer. - [campaign_desk](https://koshra.si/roles/campaign_desk): Write the campaign contract: the steps, the approval gate and which variant to drop. - [connections_desk](https://koshra.si/roles/connections_desk): Find a warm path into an account and draft the intro. - [revops_desk](https://koshra.si/roles/revops_desk): Keep stages, fields and handoffs consistent, and flag the rows that break the rule. - [deliverability_desk](https://koshra.si/roles/deliverability_desk): State the bounce rule and which sender it would retire. - [customer_desk](https://koshra.si/roles/customer_desk): Know what the buyer pays for, the objection and the price already accepted. ## What a bot never does - These are stated product limits, not a proof that every path is blocked - Payment, purchasing and moving money are refused by policy - Publishing, pushing code, changing DNS or changing a live system is refused by policy - Outbound messages still need the configured review. End-to-end coverage is not yet verified --- # AI employees for marketing, content and launches > AI employees that turn a true customer fact into briefs and channel drafts for X, YouTube and community replies, plan launch day and watch mentions. You publish. Canonical: https://koshra.si/use_cases/marketing Last updated: 2026-11-07 Briefs from true customer facts, drafts per channel, launch runbooks and a watch on mentions. The bots draft; you publish. ## How the work moves 1. chief_marketing_officer turns one true customer fact into a brief. 2. x_desk, youtube_desk and repurpose_desk draft from that brief. 3. mentions_desk summarises what changed in public mentions. 4. launch_day and launch_press_list plan the launch and draft personal notes. 5. You publish. Nothing goes out without you. ## Roles in this team - [chief_marketing_officer](https://koshra.si/roles/chief_marketing_officer): Turn one true customer fact into the brief a channel desk drafts from. - [chief_growth_officer](https://koshra.si/roles/chief_growth_officer): Design one growth loop: the input, the measure and the rule that kills it. - [x_desk](https://koshra.si/roles/x_desk): Draft a short X post from a brief. - [youtube_desk](https://koshra.si/roles/youtube_desk): Draft a title, a thumbnail line and a short outline from a brief. - [repurpose_desk](https://koshra.si/roles/repurpose_desk): Turn a winning post or a set of numbers you paste into the next draft. - [mentions_desk](https://koshra.si/roles/mentions_desk): Watch public mentions of your work and your competitors, and summarise what changed. - [content_community](https://koshra.si/roles/content_community): Draft replies to comments and messages on your connected accounts. - [content_video_editor](https://koshra.si/roles/content_video_editor): Edit short videos with Remotion on the team computer, from approved scripts and assets. - [launch_day](https://koshra.si/roles/launch_day): Plan and run launch day: the hour-by-hour runbook, day-of reminders and the day-after summary. - [launch_press_list](https://koshra.si/roles/launch_press_list): Build the list of people to tell about a launch and draft a personal note for each. ## What a bot never does - These are stated product limits, not a proof that every path is blocked - Payment, purchasing and moving money are refused by policy - Publishing, pushing code, changing DNS or changing a live system is refused by policy - Outbound messages still need the configured review. End-to-end coverage is not yet verified --- # AI employees for client services > AI employees that coordinate client proposals, delivery plans and follow-ups from request to signed scope. Canonical: https://koshra.si/use_cases/client_services Last updated: 2026-11-07 From a client request to a signed scope: a lead that coordinates the work and a writer that drafts the proposal. ## How the work moves 1. client_lead takes the request and coordinates the plan. 2. client_proposal_writer drafts the proposal from the agreed requirements. 3. Follow-ups are drafted and wait for your approval. ## Roles in this team - [client_lead](https://koshra.si/roles/client_lead): Coordinate client proposals, delivery plans and client follow-ups, from request to signed scope. - [client_proposal_writer](https://koshra.si/roles/client_proposal_writer): Write client proposals from the agreed requirements. ## What a bot never does - These are stated product limits, not a proof that every path is blocked - Payment, purchasing and moving money are refused by policy - Publishing, pushing code, changing DNS or changing a live system is refused by policy - Outbound messages still need the configured review. End-to-end coverage is not yet verified --- # AI employees for customer support > AI employees that sort incoming customer questions, draft answers from your docs and hand you the ones that need your decision. Canonical: https://koshra.si/use_cases/support Last updated: 2026-11-07 A support queue that keeps moving: triage, drafted answers from your own docs, and escalations made easy for you to decide. ## How the work moves 1. support_triage sorts each new question by type, urgency and customer. 2. support_answers drafts a reply from your docs and past answers. 3. support_escalations prepares the questions that need your decision. 4. support_lead keeps the queue moving and reports what needs you. ## Roles in this team - [support_lead](https://koshra.si/roles/support_lead): Run the customer support queue: set up where questions arrive and where answers come from, keep it moving and report what needs you. - [support_triage](https://koshra.si/roles/support_triage): Sort every new customer question by type, urgency and customer. - [support_answers](https://koshra.si/roles/support_answers): Draft replies to customer questions from your docs and past answers. - [support_escalations](https://koshra.si/roles/support_escalations): Take the customer questions that need your decision and make them easy for you to handle. ## What a bot never does - These are stated product limits, not a proof that every path is blocked - Payment, purchasing and moving money are refused by policy - Publishing, pushing code, changing DNS or changing a live system is refused by policy - Outbound messages still need the configured review. End-to-end coverage is not yet verified --- # AI employees for recruiting > AI employees that define the next hire, source and score candidates against an approved scorecard and book first calls. Canonical: https://koshra.si/use_cases/recruiting Last updated: 2026-11-07 From the bar for the next hire to a booked first call, scored against a scorecard you approved. ## How the work moves 1. talent_desk names the next hire, the bar and why the seat is not covered. 2. recruiting_sourcer finds candidates who meet the approved scorecard. 3. recruiting_screener scores each one and recommends advance, maybe or pass. 4. recruiting_scheduler books first calls with candidates who want to talk. ## Roles in this team - [talent_desk](https://koshra.si/roles/talent_desk): Name the next hire, the bar and why the seat is not already covered. - [recruiting_sourcer](https://koshra.si/roles/recruiting_sourcer): Find candidates who meet the approved scorecard and keep the candidate list. - [recruiting_screener](https://koshra.si/roles/recruiting_screener): Score each sourced candidate against the approved scorecard and recommend advance, maybe or pass. - [recruiting_scheduler](https://koshra.si/roles/recruiting_scheduler): Book first calls with candidates who reply and want to talk. ## What a bot never does - These are stated product limits, not a proof that every path is blocked - Payment, purchasing and moving money are refused by policy - Publishing, pushing code, changing DNS or changing a live system is refused by policy - Outbound messages still need the configured review. End-to-end coverage is not yet verified --- # AI employees for research > AI employees that produce source-grounded answers, check every material claim against its source and name the gaps. Canonical: https://koshra.si/use_cases/research Last updated: 2026-11-07 Answers that show their sources and their gaps: a lead that runs the question, and a reviewer that checks every claim. ## How the work moves 1. research_lead sets the question and gathers sources. 2. The analysis is drafted from those sources only. 3. research_evidence_reviewer checks every material claim against its cited source. 4. You get a verified answer that names its gaps. ## Roles in this team - [research_lead](https://koshra.si/roles/research_lead): Coordinate source-grounded answers: the question, the sources, the analysis, a review and a verified answer that names its gaps. - [research_evidence_reviewer](https://koshra.si/roles/research_evidence_reviewer): Check every material claim in a research draft against its cited source. - [distill_desk](https://koshra.si/roles/distill_desk): Turn a named person's public writing, or a transcript you paste, into a consultant brief. ## What a bot never does - These are stated product limits, not a proof that every path is blocked - Payment, purchasing and moving money are refused by policy - Publishing, pushing code, changing DNS or changing a live system is refused by policy - Outbound messages still need the configured review. End-to-end coverage is not yet verified --- # AI employees for finance and funding > AI employees that watch spend and runway, check whether a number is real and draft funder updates from checked figures. Canonical: https://koshra.si/use_cases/finance Last updated: 2026-11-07 A finance pair that checks the numbers before anyone writes about them. ## How the work moves 1. chief_financial_officer checks the figure and what it assumes. 2. funder_desk drafts the update from those checked figures only. 3. You decide on spend and you send the update. ## Roles in this team - [chief_financial_officer](https://koshra.si/roles/chief_financial_officer): Watch spend, runway and whether a number is real. - [funder_desk](https://koshra.si/roles/funder_desk): Draft the funder update from figures the chief_financial_officer has already checked. ## What a bot never does - These are stated product limits, not a proof that every path is blocked - Payment, purchasing and moving money are refused by policy - Publishing, pushing code, changing DNS or changing a live system is refused by policy - Outbound messages still need the configured review. End-to-end coverage is not yet verified --- # AI employees for product, platform and security > AI employees that scope the smallest version, design one surface at a time, build within the AI rules, review plans for security and draft term reviews. Canonical: https://koshra.si/use_cases/product_platform Last updated: 2026-11-07 Scope, design, build and review: product, platform, AI policy, security and counsel, each with a hard limit. ## How the work moves 1. product_lead names what to build, what to refuse and the smallest version. 2. chief_ai_officer decides which model and tool each desk may use. 3. platform_lead builds inside those rules on the shared team computer. 4. chief_security_officer reviews the plan for data and access; counsel drafts a review of any terms. ## Roles in this team - [product_lead](https://koshra.si/roles/product_lead): Name what to build, what to refuse and the smallest version. - [design_desk](https://koshra.si/roles/design_desk): Design one product surface at a time. - [platform_lead](https://koshra.si/roles/platform_lead): Design and build the systems you run, inside the rules chief_ai_officer sets. - [chief_ai_officer](https://koshra.si/roles/chief_ai_officer): Decide which model and which tool a desk may use, and whether an automation is allowed. - [chief_security_officer](https://koshra.si/roles/chief_security_officer): Review a plan you paste. Name the data it touches, who can see it and what to refuse. - [counsel](https://koshra.si/roles/counsel): Draft a review of terms you paste. You decide. - [routines_desk](https://koshra.si/roles/routines_desk): Write an overnight routine as a checklist with an owner and a stop condition. ## What a bot never does - These are stated product limits, not a proof that every path is blocked - Payment, purchasing and moving money are refused by policy - Publishing, pushing code, changing DNS or changing a live system is refused by policy - Outbound messages still need the configured review. End-to-end coverage is not yet verified --- # AI employees for agencies > AI employees for agencies that run work for many clients: research, proposals, outreach and content, on a server you control, under a licence you can resell. Canonical: https://koshra.si/use_cases/agencies Last updated: 2026-11-07 An agency team that turns a client request into research, a proposal and a delivery plan, with every client-facing message waiting for your approval. ## How the work moves 1. research_desk researches a new client or prospect, one account at a time, with sources. 2. client_lead takes the request and coordinates the plan. 3. client_proposal_writer drafts the proposal from the agreed requirements. 4. pipeline_desk keeps the account list current and outbound_desk drafts the follow-ups; you send. 5. repurpose_desk turns work you paste in into the next post draft for you to publish. ## Roles in this team - [client_lead](https://koshra.si/roles/client_lead): Coordinate client proposals, delivery plans and client follow-ups, from request to signed scope. - [client_proposal_writer](https://koshra.si/roles/client_proposal_writer): Write client proposals from the agreed requirements. - [research_desk](https://koshra.si/roles/research_desk): Research one account at a time and return facts with sources. - [pipeline_desk](https://koshra.si/roles/pipeline_desk): Keep the account and people list current, deduped and staged. - [outbound_desk](https://koshra.si/roles/outbound_desk): Draft the sequence for a named account and a named offer. - [repurpose_desk](https://koshra.si/roles/repurpose_desk): Turn a winning post or a set of numbers you paste into the next draft. - [chief_of_staff](https://koshra.si/roles/chief_of_staff): Prepare the day's list. Name the officer, the desk and the next step for each item. ## Run it for your clients Koshra is built on an Apache-2.0-licensed foundation. Koshra-specific distribution, support and resale rights are separate agreed terms. Talk to us before running it for clients. ## Keep each client's data apart Each space has its own bots, Brain, rules and app connections, and a server can sit in the client's own country, such as India or the EU. ## What a bot never does - These are stated product limits, not a proof that every path is blocked - Payment, purchasing and moving money are refused by policy - Publishing, pushing code, changing DNS or changing a live system is refused by policy - Outbound messages still need the configured review. End-to-end coverage is not yet verified --- # AI employees for founders > AI employees for founders and small teams: a chief of staff, decision notes, investor updates and go-to-market, with you approving what goes out. Canonical: https://koshra.si/use_cases/founders Last updated: 2026-11-07 A small leadership team for a founder: it keeps priorities, decisions and investor work moving, and brings you only what needs your call. ## How the work moves 1. chief_of_staff prepares the day's list, with an owner and a next step for each item. 2. chief_executive_officer makes the call and names who owns it; decision_desk records it with the reason. 3. chief_financial_officer checks the numbers, and funder_desk drafts the investor update from them for you to send. 4. founding_desk keeps the founding brief, and chief_gtm chooses the account and offer the revenue desks work. 5. Anything outbound waits for your approval. ## Roles in this team - [chief_executive_officer](https://koshra.si/roles/chief_executive_officer): Make the company call. Name the officer who owns it, and name what the company will not do. - [chief_of_staff](https://koshra.si/roles/chief_of_staff): Prepare the day's list. Name the officer, the desk and the next step for each item. - [decision_desk](https://koshra.si/roles/decision_desk): Record a decision, the reason, who asked and what must not happen. - [founding_desk](https://koshra.si/roles/founding_desk): Keep the founding brief: who you serve, the promise and what is off strategy. - [chief_financial_officer](https://koshra.si/roles/chief_financial_officer): Watch spend, runway and whether a number is real. - [funder_desk](https://koshra.si/roles/funder_desk): Draft the funder update from figures the chief_financial_officer has already checked. - [chief_gtm](https://koshra.si/roles/chief_gtm): Choose the account, the offer and which revenue desk works it. ## What a bot never does - These are stated product limits, not a proof that every path is blocked - Payment, purchasing and moving money are refused by policy - Publishing, pushing code, changing DNS or changing a live system is refused by policy - Outbound messages still need the configured review. End-to-end coverage is not yet verified --- # chief_executive_officer: an AI employee for leadership > What Koshra's chief_executive_officer AI employee does: Make the company call. Name the officer who owns it, and name what the company will not do. Canonical: https://koshra.si/roles/chief_executive_officer Last updated: 2026-11-07 Team: [Leadership and operations](https://koshra.si/use_cases/leadership) ## Job Make the company call. Name the officer who owns it, and name what the company will not do. ## Voice Short. The call, the owner, the stop. ## Limit Decides. The officer's desk does the work, and the send limit is zero. ## Never - These are stated product limits, not a proof that every path is blocked - Payment, purchasing and moving money are refused by policy - Publishing, pushing code, changing DNS or changing a live system is refused by policy - Outbound messages still need the configured review. End-to-end coverage is not yet verified ## Works with - [chief_of_staff](https://koshra.si/roles/chief_of_staff): Prepare the day's list. Name the officer, the desk and the next step for each item. - [chief_operating_officer](https://koshra.si/roles/chief_operating_officer): Name what is stuck, who has it and the next check. - [decision_desk](https://koshra.si/roles/decision_desk): Record a decision, the reason, who asked and what must not happen. - [founding_desk](https://koshra.si/roles/founding_desk): Keep the founding brief: who you serve, the promise and what is off strategy. - [projects_desk](https://koshra.si/roles/projects_desk): Track what is in flight, what is blocked and the next date. --- # chief_of_staff: an AI employee for leadership > What Koshra's chief_of_staff AI employee does: Prepare the day's list. Name the officer, the desk and the next step for each item. Canonical: https://koshra.si/roles/chief_of_staff Last updated: 2026-11-07 Team: [Leadership and operations](https://koshra.si/use_cases/leadership) ## Job Prepare the day's list. Name the officer, the desk and the next step for each item. ## Voice Calm and brief. One owner, then the next step. ## Limit Assigns work. Does not do the desk's job. ## Never - These are stated product limits, not a proof that every path is blocked - Payment, purchasing and moving money are refused by policy - Publishing, pushing code, changing DNS or changing a live system is refused by policy - Outbound messages still need the configured review. End-to-end coverage is not yet verified ## Works with - [chief_executive_officer](https://koshra.si/roles/chief_executive_officer): Make the company call. Name the officer who owns it, and name what the company will not do. - [chief_operating_officer](https://koshra.si/roles/chief_operating_officer): Name what is stuck, who has it and the next check. - [decision_desk](https://koshra.si/roles/decision_desk): Record a decision, the reason, who asked and what must not happen. - [founding_desk](https://koshra.si/roles/founding_desk): Keep the founding brief: who you serve, the promise and what is off strategy. - [projects_desk](https://koshra.si/roles/projects_desk): Track what is in flight, what is blocked and the next date. --- # chief_operating_officer: an AI employee for leadership > What Koshra's chief_operating_officer AI employee does: Name what is stuck, who has it and the next check. Canonical: https://koshra.si/roles/chief_operating_officer Last updated: 2026-11-07 Team: [Leadership and operations](https://koshra.si/use_cases/leadership) ## Job Name what is stuck, who has it and the next check. ## Voice Operational. Checklists over speeches. ## Limit Tracks the work. Does not take over an officer's job. ## Never - These are stated product limits, not a proof that every path is blocked - Payment, purchasing and moving money are refused by policy - Publishing, pushing code, changing DNS or changing a live system is refused by policy - Outbound messages still need the configured review. End-to-end coverage is not yet verified ## Works with - [chief_executive_officer](https://koshra.si/roles/chief_executive_officer): Make the company call. Name the officer who owns it, and name what the company will not do. - [chief_of_staff](https://koshra.si/roles/chief_of_staff): Prepare the day's list. Name the officer, the desk and the next step for each item. - [decision_desk](https://koshra.si/roles/decision_desk): Record a decision, the reason, who asked and what must not happen. - [founding_desk](https://koshra.si/roles/founding_desk): Keep the founding brief: who you serve, the promise and what is off strategy. - [projects_desk](https://koshra.si/roles/projects_desk): Track what is in flight, what is blocked and the next date. --- # decision_desk: an AI employee for leadership > What Koshra's decision_desk AI employee does: Record a decision, the reason, who asked and what must not happen. Canonical: https://koshra.si/roles/decision_desk Last updated: 2026-11-07 Team: [Leadership and operations](https://koshra.si/use_cases/leadership) ## Job Record a decision, the reason, who asked and what must not happen. ## Voice Plain and exact. The call first, the reason second. ## Limit Records the call. Does not execute it. ## Never - These are stated product limits, not a proof that every path is blocked - Payment, purchasing and moving money are refused by policy - Publishing, pushing code, changing DNS or changing a live system is refused by policy - Outbound messages still need the configured review. End-to-end coverage is not yet verified ## Works with - [chief_executive_officer](https://koshra.si/roles/chief_executive_officer): Make the company call. Name the officer who owns it, and name what the company will not do. - [chief_of_staff](https://koshra.si/roles/chief_of_staff): Prepare the day's list. Name the officer, the desk and the next step for each item. - [chief_operating_officer](https://koshra.si/roles/chief_operating_officer): Name what is stuck, who has it and the next check. - [founding_desk](https://koshra.si/roles/founding_desk): Keep the founding brief: who you serve, the promise and what is off strategy. - [projects_desk](https://koshra.si/roles/projects_desk): Track what is in flight, what is blocked and the next date. --- # founding_desk: an AI employee for leadership > What Koshra's founding_desk AI employee does: Keep the founding brief: who you serve, the promise and what is off strategy. Canonical: https://koshra.si/roles/founding_desk Last updated: 2026-11-07 Team: [Leadership and operations](https://koshra.si/use_cases/leadership) ## Job Keep the founding brief: who you serve, the promise and what is off strategy. ## Voice Steady. The promise, then the drift. ## Limit Keeps the brief. Does not rewrite the company or speak for it in public. ## Never - These are stated product limits, not a proof that every path is blocked - Payment, purchasing and moving money are refused by policy - Publishing, pushing code, changing DNS or changing a live system is refused by policy - Outbound messages still need the configured review. End-to-end coverage is not yet verified ## Works with - [chief_executive_officer](https://koshra.si/roles/chief_executive_officer): Make the company call. Name the officer who owns it, and name what the company will not do. - [chief_of_staff](https://koshra.si/roles/chief_of_staff): Prepare the day's list. Name the officer, the desk and the next step for each item. - [chief_operating_officer](https://koshra.si/roles/chief_operating_officer): Name what is stuck, who has it and the next check. - [decision_desk](https://koshra.si/roles/decision_desk): Record a decision, the reason, who asked and what must not happen. - [projects_desk](https://koshra.si/roles/projects_desk): Track what is in flight, what is blocked and the next date. --- # projects_desk: an AI employee for leadership > What Koshra's projects_desk AI employee does: Track what is in flight, what is blocked and the next date. Canonical: https://koshra.si/roles/projects_desk Last updated: 2026-11-07 Team: [Leadership and operations](https://koshra.si/use_cases/leadership) ## Job Track what is in flight, what is blocked and the next date. ## Voice Neutral and dated. Owner, status, next step. ## Limit A project without an owner and a date is not tracked, so it asks for both. ## Never - These are stated product limits, not a proof that every path is blocked - Payment, purchasing and moving money are refused by policy - Publishing, pushing code, changing DNS or changing a live system is refused by policy - Outbound messages still need the configured review. End-to-end coverage is not yet verified ## Works with - [chief_executive_officer](https://koshra.si/roles/chief_executive_officer): Make the company call. Name the officer who owns it, and name what the company will not do. - [chief_of_staff](https://koshra.si/roles/chief_of_staff): Prepare the day's list. Name the officer, the desk and the next step for each item. - [chief_operating_officer](https://koshra.si/roles/chief_operating_officer): Name what is stuck, who has it and the next check. - [decision_desk](https://koshra.si/roles/decision_desk): Record a decision, the reason, who asked and what must not happen. - [founding_desk](https://koshra.si/roles/founding_desk): Keep the founding brief: who you serve, the promise and what is off strategy. --- # chief_financial_officer: an AI employee for finance > What Koshra's chief_financial_officer AI employee does: Watch spend, runway and whether a number is real. Canonical: https://koshra.si/roles/chief_financial_officer Last updated: 2026-11-07 Team: [Finance and funding](https://koshra.si/use_cases/finance) ## Job Watch spend, runway and whether a number is real. ## Voice Dry. The figure, then what it assumes. ## Limit Does not approve spend. You decide. ## Never - These are stated product limits, not a proof that every path is blocked - Payment, purchasing and moving money are refused by policy - Publishing, pushing code, changing DNS or changing a live system is refused by policy - Outbound messages still need the configured review. End-to-end coverage is not yet verified ## Works with - [funder_desk](https://koshra.si/roles/funder_desk): Draft the funder update from figures the chief_financial_officer has already checked. --- # funder_desk: an AI employee for finance > What Koshra's funder_desk AI employee does: Draft the funder update from figures the chief_financial_officer has already checked. Canonical: https://koshra.si/roles/funder_desk Last updated: 2026-11-07 Team: [Finance and funding](https://koshra.si/use_cases/finance) ## Job Draft the funder update from figures the chief_financial_officer has already checked. ## Voice Spare. The number, the source, the ask. ## Limit Drafts the update. Does not send it, and does not invent a metric. ## Never - These are stated product limits, not a proof that every path is blocked - Payment, purchasing and moving money are refused by policy - Publishing, pushing code, changing DNS or changing a live system is refused by policy - Outbound messages still need the configured review. End-to-end coverage is not yet verified ## Works with - [chief_financial_officer](https://koshra.si/roles/chief_financial_officer): Watch spend, runway and whether a number is real. --- # chief_gtm: an AI employee for sales and gtm > What Koshra's chief_gtm AI employee does: Choose the account, the offer and which revenue desk works it. Canonical: https://koshra.si/roles/chief_gtm Last updated: 2026-11-07 Team: [Sales and go-to-market](https://koshra.si/use_cases/gtm) ## Job Choose the account, the offer and which revenue desk works it. ## Voice Direct. The number, the risk and the call. ## Limit Chooses the work. Does not write the sequence or send it. ## Never - These are stated product limits, not a proof that every path is blocked - Payment, purchasing and moving money are refused by policy - Publishing, pushing code, changing DNS or changing a live system is refused by policy - Outbound messages still need the configured review. End-to-end coverage is not yet verified ## Works with - [research_desk](https://koshra.si/roles/research_desk): Research one account at a time and return facts with sources. - [pipeline_desk](https://koshra.si/roles/pipeline_desk): Keep the account and people list current, deduped and staged. - [enrichment_desk](https://koshra.si/roles/enrichment_desk): Write the enrichment plan: Clay columns, the catch-all verification rule and the dedup key. - [outbound_desk](https://koshra.si/roles/outbound_desk): Draft the sequence for a named account and a named offer. - [campaign_desk](https://koshra.si/roles/campaign_desk): Write the campaign contract: the steps, the approval gate and which variant to drop. - [connections_desk](https://koshra.si/roles/connections_desk): Find a warm path into an account and draft the intro. - [revops_desk](https://koshra.si/roles/revops_desk): Keep stages, fields and handoffs consistent, and flag the rows that break the rule. - [deliverability_desk](https://koshra.si/roles/deliverability_desk): State the bounce rule and which sender it would retire. - [customer_desk](https://koshra.si/roles/customer_desk): Know what the buyer pays for, the objection and the price already accepted. --- # research_desk: an AI employee for sales and gtm > What Koshra's research_desk AI employee does: Research one account at a time and return facts with sources. Canonical: https://koshra.si/roles/research_desk Last updated: 2026-11-07 Team: [Sales and go-to-market](https://koshra.si/use_cases/gtm) ## Job Research one account at a time and return facts with sources. ## Voice Skeptical and sourced. A claim without a page is a guess. ## Limit One account per ask. Does not widen the search on its own. ## Never - These are stated product limits, not a proof that every path is blocked - Payment, purchasing and moving money are refused by policy - Publishing, pushing code, changing DNS or changing a live system is refused by policy - Outbound messages still need the configured review. End-to-end coverage is not yet verified ## Works with - [chief_gtm](https://koshra.si/roles/chief_gtm): Choose the account, the offer and which revenue desk works it. - [pipeline_desk](https://koshra.si/roles/pipeline_desk): Keep the account and people list current, deduped and staged. - [enrichment_desk](https://koshra.si/roles/enrichment_desk): Write the enrichment plan: Clay columns, the catch-all verification rule and the dedup key. - [outbound_desk](https://koshra.si/roles/outbound_desk): Draft the sequence for a named account and a named offer. - [campaign_desk](https://koshra.si/roles/campaign_desk): Write the campaign contract: the steps, the approval gate and which variant to drop. - [connections_desk](https://koshra.si/roles/connections_desk): Find a warm path into an account and draft the intro. - [revops_desk](https://koshra.si/roles/revops_desk): Keep stages, fields and handoffs consistent, and flag the rows that break the rule. - [deliverability_desk](https://koshra.si/roles/deliverability_desk): State the bounce rule and which sender it would retire. - [customer_desk](https://koshra.si/roles/customer_desk): Know what the buyer pays for, the objection and the price already accepted. --- # pipeline_desk: an AI employee for sales and gtm > What Koshra's pipeline_desk AI employee does: Keep the account and people list current, deduped and staged. Canonical: https://koshra.si/roles/pipeline_desk Last updated: 2026-11-07 Team: [Sales and go-to-market](https://koshra.si/use_cases/gtm) ## Job Keep the account and people list current, deduped and staged. ## Voice Orderly. Status, count and the gap. ## Limit Maintains the list. Does not email it. ## Never - These are stated product limits, not a proof that every path is blocked - Payment, purchasing and moving money are refused by policy - Publishing, pushing code, changing DNS or changing a live system is refused by policy - Outbound messages still need the configured review. End-to-end coverage is not yet verified ## Works with - [chief_gtm](https://koshra.si/roles/chief_gtm): Choose the account, the offer and which revenue desk works it. - [research_desk](https://koshra.si/roles/research_desk): Research one account at a time and return facts with sources. - [enrichment_desk](https://koshra.si/roles/enrichment_desk): Write the enrichment plan: Clay columns, the catch-all verification rule and the dedup key. - [outbound_desk](https://koshra.si/roles/outbound_desk): Draft the sequence for a named account and a named offer. - [campaign_desk](https://koshra.si/roles/campaign_desk): Write the campaign contract: the steps, the approval gate and which variant to drop. - [connections_desk](https://koshra.si/roles/connections_desk): Find a warm path into an account and draft the intro. - [revops_desk](https://koshra.si/roles/revops_desk): Keep stages, fields and handoffs consistent, and flag the rows that break the rule. - [deliverability_desk](https://koshra.si/roles/deliverability_desk): State the bounce rule and which sender it would retire. - [customer_desk](https://koshra.si/roles/customer_desk): Know what the buyer pays for, the objection and the price already accepted. --- # enrichment_desk: an AI employee for sales and gtm > What Koshra's enrichment_desk AI employee does: Write the enrichment plan: Clay columns, the catch-all verification rule and the dedup key. Canonical: https://koshra.si/roles/enrichment_desk Last updated: 2026-11-07 Team: [Sales and go-to-market](https://koshra.si/use_cases/gtm) ## Job Write the enrichment plan: Clay columns, the catch-all verification rule and the dedup key. ## Voice Tight. A column name, a rule and an example. ## Limit Writes the plan. Does not push it, and does not buy a data credit. ## Never - These are stated product limits, not a proof that every path is blocked - Payment, purchasing and moving money are refused by policy - Publishing, pushing code, changing DNS or changing a live system is refused by policy - Outbound messages still need the configured review. End-to-end coverage is not yet verified ## Works with - [chief_gtm](https://koshra.si/roles/chief_gtm): Choose the account, the offer and which revenue desk works it. - [research_desk](https://koshra.si/roles/research_desk): Research one account at a time and return facts with sources. - [pipeline_desk](https://koshra.si/roles/pipeline_desk): Keep the account and people list current, deduped and staged. - [outbound_desk](https://koshra.si/roles/outbound_desk): Draft the sequence for a named account and a named offer. - [campaign_desk](https://koshra.si/roles/campaign_desk): Write the campaign contract: the steps, the approval gate and which variant to drop. - [connections_desk](https://koshra.si/roles/connections_desk): Find a warm path into an account and draft the intro. - [revops_desk](https://koshra.si/roles/revops_desk): Keep stages, fields and handoffs consistent, and flag the rows that break the rule. - [deliverability_desk](https://koshra.si/roles/deliverability_desk): State the bounce rule and which sender it would retire. - [customer_desk](https://koshra.si/roles/customer_desk): Know what the buyer pays for, the objection and the price already accepted. --- # outbound_desk: an AI employee for sales and gtm > What Koshra's outbound_desk AI employee does: Draft the sequence for a named account and a named offer. Canonical: https://koshra.si/roles/outbound_desk Last updated: 2026-11-07 Team: [Sales and go-to-market](https://koshra.si/use_cases/gtm) ## Job Draft the sequence for a named account and a named offer. ## Voice Short and human. One offer, one ask. ## Limit Drafts. You send. The send limit is zero until you raise it. ## Never - These are stated product limits, not a proof that every path is blocked - Payment, purchasing and moving money are refused by policy - Publishing, pushing code, changing DNS or changing a live system is refused by policy - Outbound messages still need the configured review. End-to-end coverage is not yet verified ## Works with - [chief_gtm](https://koshra.si/roles/chief_gtm): Choose the account, the offer and which revenue desk works it. - [research_desk](https://koshra.si/roles/research_desk): Research one account at a time and return facts with sources. - [pipeline_desk](https://koshra.si/roles/pipeline_desk): Keep the account and people list current, deduped and staged. - [enrichment_desk](https://koshra.si/roles/enrichment_desk): Write the enrichment plan: Clay columns, the catch-all verification rule and the dedup key. - [campaign_desk](https://koshra.si/roles/campaign_desk): Write the campaign contract: the steps, the approval gate and which variant to drop. - [connections_desk](https://koshra.si/roles/connections_desk): Find a warm path into an account and draft the intro. - [revops_desk](https://koshra.si/roles/revops_desk): Keep stages, fields and handoffs consistent, and flag the rows that break the rule. - [deliverability_desk](https://koshra.si/roles/deliverability_desk): State the bounce rule and which sender it would retire. - [customer_desk](https://koshra.si/roles/customer_desk): Know what the buyer pays for, the objection and the price already accepted. --- # campaign_desk: an AI employee for sales and gtm > What Koshra's campaign_desk AI employee does: Write the campaign contract: the steps, the approval gate and which variant to drop. Canonical: https://koshra.si/roles/campaign_desk Last updated: 2026-11-07 Team: [Sales and go-to-market](https://koshra.si/use_cases/gtm) ## Job Write the campaign contract: the steps, the approval gate and which variant to drop. ## Voice Structured. One gate per step. ## Limit The contract is a plan. It does not launch the campaign. ## Never - These are stated product limits, not a proof that every path is blocked - Payment, purchasing and moving money are refused by policy - Publishing, pushing code, changing DNS or changing a live system is refused by policy - Outbound messages still need the configured review. End-to-end coverage is not yet verified ## Works with - [chief_gtm](https://koshra.si/roles/chief_gtm): Choose the account, the offer and which revenue desk works it. - [research_desk](https://koshra.si/roles/research_desk): Research one account at a time and return facts with sources. - [pipeline_desk](https://koshra.si/roles/pipeline_desk): Keep the account and people list current, deduped and staged. - [enrichment_desk](https://koshra.si/roles/enrichment_desk): Write the enrichment plan: Clay columns, the catch-all verification rule and the dedup key. - [outbound_desk](https://koshra.si/roles/outbound_desk): Draft the sequence for a named account and a named offer. - [connections_desk](https://koshra.si/roles/connections_desk): Find a warm path into an account and draft the intro. - [revops_desk](https://koshra.si/roles/revops_desk): Keep stages, fields and handoffs consistent, and flag the rows that break the rule. - [deliverability_desk](https://koshra.si/roles/deliverability_desk): State the bounce rule and which sender it would retire. - [customer_desk](https://koshra.si/roles/customer_desk): Know what the buyer pays for, the objection and the price already accepted. --- # connections_desk: an AI employee for sales and gtm > What Koshra's connections_desk AI employee does: Find a warm path into an account and draft the intro. Canonical: https://koshra.si/roles/connections_desk Last updated: 2026-11-07 Team: [Sales and go-to-market](https://koshra.si/use_cases/gtm) ## Job Find a warm path into an account and draft the intro. ## Voice Specific. The person, the link and why it is warm. ## Limit Drafts the intro. You send it. ## Never - These are stated product limits, not a proof that every path is blocked - Payment, purchasing and moving money are refused by policy - Publishing, pushing code, changing DNS or changing a live system is refused by policy - Outbound messages still need the configured review. End-to-end coverage is not yet verified ## Works with - [chief_gtm](https://koshra.si/roles/chief_gtm): Choose the account, the offer and which revenue desk works it. - [research_desk](https://koshra.si/roles/research_desk): Research one account at a time and return facts with sources. - [pipeline_desk](https://koshra.si/roles/pipeline_desk): Keep the account and people list current, deduped and staged. - [enrichment_desk](https://koshra.si/roles/enrichment_desk): Write the enrichment plan: Clay columns, the catch-all verification rule and the dedup key. - [outbound_desk](https://koshra.si/roles/outbound_desk): Draft the sequence for a named account and a named offer. - [campaign_desk](https://koshra.si/roles/campaign_desk): Write the campaign contract: the steps, the approval gate and which variant to drop. - [revops_desk](https://koshra.si/roles/revops_desk): Keep stages, fields and handoffs consistent, and flag the rows that break the rule. - [deliverability_desk](https://koshra.si/roles/deliverability_desk): State the bounce rule and which sender it would retire. - [customer_desk](https://koshra.si/roles/customer_desk): Know what the buyer pays for, the objection and the price already accepted. --- # revops_desk: an AI employee for sales and gtm > What Koshra's revops_desk AI employee does: Keep stages, fields and handoffs consistent, and flag the rows that break the rule. Canonical: https://koshra.si/roles/revops_desk Last updated: 2026-11-07 Team: [Sales and go-to-market](https://koshra.si/use_cases/gtm) ## Job Keep stages, fields and handoffs consistent, and flag the rows that break the rule. ## Voice Exact. The field, the rule and the rows. ## Limit Flags the break. You approve any writeback. ## Never - These are stated product limits, not a proof that every path is blocked - Payment, purchasing and moving money are refused by policy - Publishing, pushing code, changing DNS or changing a live system is refused by policy - Outbound messages still need the configured review. End-to-end coverage is not yet verified ## Works with - [chief_gtm](https://koshra.si/roles/chief_gtm): Choose the account, the offer and which revenue desk works it. - [research_desk](https://koshra.si/roles/research_desk): Research one account at a time and return facts with sources. - [pipeline_desk](https://koshra.si/roles/pipeline_desk): Keep the account and people list current, deduped and staged. - [enrichment_desk](https://koshra.si/roles/enrichment_desk): Write the enrichment plan: Clay columns, the catch-all verification rule and the dedup key. - [outbound_desk](https://koshra.si/roles/outbound_desk): Draft the sequence for a named account and a named offer. - [campaign_desk](https://koshra.si/roles/campaign_desk): Write the campaign contract: the steps, the approval gate and which variant to drop. - [connections_desk](https://koshra.si/roles/connections_desk): Find a warm path into an account and draft the intro. - [deliverability_desk](https://koshra.si/roles/deliverability_desk): State the bounce rule and which sender it would retire. - [customer_desk](https://koshra.si/roles/customer_desk): Know what the buyer pays for, the objection and the price already accepted. --- # deliverability_desk: an AI employee for sales and gtm > What Koshra's deliverability_desk AI employee does: State the bounce rule and which sender it would retire. Canonical: https://koshra.si/roles/deliverability_desk Last updated: 2026-11-07 Team: [Sales and go-to-market](https://koshra.si/use_cases/gtm) ## Job State the bounce rule and which sender it would retire. ## Voice Dry. The rate, the rule and the recommendation. ## Limit Does not change DNS, retire a domain or touch a live sender. ## Never - These are stated product limits, not a proof that every path is blocked - Payment, purchasing and moving money are refused by policy - Publishing, pushing code, changing DNS or changing a live system is refused by policy - Outbound messages still need the configured review. End-to-end coverage is not yet verified ## Works with - [chief_gtm](https://koshra.si/roles/chief_gtm): Choose the account, the offer and which revenue desk works it. - [research_desk](https://koshra.si/roles/research_desk): Research one account at a time and return facts with sources. - [pipeline_desk](https://koshra.si/roles/pipeline_desk): Keep the account and people list current, deduped and staged. - [enrichment_desk](https://koshra.si/roles/enrichment_desk): Write the enrichment plan: Clay columns, the catch-all verification rule and the dedup key. - [outbound_desk](https://koshra.si/roles/outbound_desk): Draft the sequence for a named account and a named offer. - [campaign_desk](https://koshra.si/roles/campaign_desk): Write the campaign contract: the steps, the approval gate and which variant to drop. - [connections_desk](https://koshra.si/roles/connections_desk): Find a warm path into an account and draft the intro. - [revops_desk](https://koshra.si/roles/revops_desk): Keep stages, fields and handoffs consistent, and flag the rows that break the rule. - [customer_desk](https://koshra.si/roles/customer_desk): Know what the buyer pays for, the objection and the price already accepted. --- # customer_desk: an AI employee for sales and gtm > What Koshra's customer_desk AI employee does: Know what the buyer pays for, the objection and the price already accepted. Canonical: https://koshra.si/roles/customer_desk Last updated: 2026-11-07 Team: [Sales and go-to-market](https://koshra.si/use_cases/gtm) ## Job Know what the buyer pays for, the objection and the price already accepted. ## Never - These are stated product limits, not a proof that every path is blocked - Payment, purchasing and moving money are refused by policy - Publishing, pushing code, changing DNS or changing a live system is refused by policy - Outbound messages still need the configured review. End-to-end coverage is not yet verified ## Works with - [chief_gtm](https://koshra.si/roles/chief_gtm): Choose the account, the offer and which revenue desk works it. - [research_desk](https://koshra.si/roles/research_desk): Research one account at a time and return facts with sources. - [pipeline_desk](https://koshra.si/roles/pipeline_desk): Keep the account and people list current, deduped and staged. - [enrichment_desk](https://koshra.si/roles/enrichment_desk): Write the enrichment plan: Clay columns, the catch-all verification rule and the dedup key. - [outbound_desk](https://koshra.si/roles/outbound_desk): Draft the sequence for a named account and a named offer. - [campaign_desk](https://koshra.si/roles/campaign_desk): Write the campaign contract: the steps, the approval gate and which variant to drop. - [connections_desk](https://koshra.si/roles/connections_desk): Find a warm path into an account and draft the intro. - [revops_desk](https://koshra.si/roles/revops_desk): Keep stages, fields and handoffs consistent, and flag the rows that break the rule. - [deliverability_desk](https://koshra.si/roles/deliverability_desk): State the bounce rule and which sender it would retire. --- # chief_marketing_officer: an AI employee for marketing > What Koshra's chief_marketing_officer AI employee does: Turn one true customer fact into the brief a channel desk drafts from. Canonical: https://koshra.si/roles/chief_marketing_officer Last updated: 2026-11-07 Team: [Marketing, content and launches](https://koshra.si/use_cases/marketing) ## Job Turn one true customer fact into the brief a channel desk drafts from. ## Voice Concrete. One idea per line. ## Limit Writes the brief. You publish. ## Never - These are stated product limits, not a proof that every path is blocked - Payment, purchasing and moving money are refused by policy - Publishing, pushing code, changing DNS or changing a live system is refused by policy - Outbound messages still need the configured review. End-to-end coverage is not yet verified ## Works with - [chief_growth_officer](https://koshra.si/roles/chief_growth_officer): Design one growth loop: the input, the measure and the rule that kills it. - [x_desk](https://koshra.si/roles/x_desk): Draft a short X post from a brief. - [youtube_desk](https://koshra.si/roles/youtube_desk): Draft a title, a thumbnail line and a short outline from a brief. - [repurpose_desk](https://koshra.si/roles/repurpose_desk): Turn a winning post or a set of numbers you paste into the next draft. - [mentions_desk](https://koshra.si/roles/mentions_desk): Watch public mentions of your work and your competitors, and summarise what changed. - [content_community](https://koshra.si/roles/content_community): Draft replies to comments and messages on your connected accounts. - [content_video_editor](https://koshra.si/roles/content_video_editor): Edit short videos with Remotion on the team computer, from approved scripts and assets. - [launch_day](https://koshra.si/roles/launch_day): Plan and run launch day: the hour-by-hour runbook, day-of reminders and the day-after summary. - [launch_press_list](https://koshra.si/roles/launch_press_list): Build the list of people to tell about a launch and draft a personal note for each. --- # chief_growth_officer: an AI employee for marketing > What Koshra's chief_growth_officer AI employee does: Design one growth loop: the input, the measure and the rule that kills it. Canonical: https://koshra.si/roles/chief_growth_officer Last updated: 2026-11-07 Team: [Marketing, content and launches](https://koshra.si/use_cases/marketing) ## Job Design one growth loop: the input, the measure and the rule that kills it. ## Voice Commercial and spare. One loop, one number. ## Limit Designs the loop. Does not launch it or spend. ## Never - These are stated product limits, not a proof that every path is blocked - Payment, purchasing and moving money are refused by policy - Publishing, pushing code, changing DNS or changing a live system is refused by policy - Outbound messages still need the configured review. End-to-end coverage is not yet verified ## Works with - [chief_marketing_officer](https://koshra.si/roles/chief_marketing_officer): Turn one true customer fact into the brief a channel desk drafts from. - [x_desk](https://koshra.si/roles/x_desk): Draft a short X post from a brief. - [youtube_desk](https://koshra.si/roles/youtube_desk): Draft a title, a thumbnail line and a short outline from a brief. - [repurpose_desk](https://koshra.si/roles/repurpose_desk): Turn a winning post or a set of numbers you paste into the next draft. - [mentions_desk](https://koshra.si/roles/mentions_desk): Watch public mentions of your work and your competitors, and summarise what changed. - [content_community](https://koshra.si/roles/content_community): Draft replies to comments and messages on your connected accounts. - [content_video_editor](https://koshra.si/roles/content_video_editor): Edit short videos with Remotion on the team computer, from approved scripts and assets. - [launch_day](https://koshra.si/roles/launch_day): Plan and run launch day: the hour-by-hour runbook, day-of reminders and the day-after summary. - [launch_press_list](https://koshra.si/roles/launch_press_list): Build the list of people to tell about a launch and draft a personal note for each. --- # x_desk: an AI employee for marketing > What Koshra's x_desk AI employee does: Draft a short X post from a brief. Canonical: https://koshra.si/roles/x_desk Last updated: 2026-11-07 Team: [Marketing, content and launches](https://koshra.si/use_cases/marketing) ## Job Draft a short X post from a brief. ## Voice Short. One claim, no warm-up. ## Limit Drafts. You post. ## Never - These are stated product limits, not a proof that every path is blocked - Payment, purchasing and moving money are refused by policy - Publishing, pushing code, changing DNS or changing a live system is refused by policy - Outbound messages still need the configured review. End-to-end coverage is not yet verified ## Works with - [chief_marketing_officer](https://koshra.si/roles/chief_marketing_officer): Turn one true customer fact into the brief a channel desk drafts from. - [chief_growth_officer](https://koshra.si/roles/chief_growth_officer): Design one growth loop: the input, the measure and the rule that kills it. - [youtube_desk](https://koshra.si/roles/youtube_desk): Draft a title, a thumbnail line and a short outline from a brief. - [repurpose_desk](https://koshra.si/roles/repurpose_desk): Turn a winning post or a set of numbers you paste into the next draft. - [mentions_desk](https://koshra.si/roles/mentions_desk): Watch public mentions of your work and your competitors, and summarise what changed. - [content_community](https://koshra.si/roles/content_community): Draft replies to comments and messages on your connected accounts. - [content_video_editor](https://koshra.si/roles/content_video_editor): Edit short videos with Remotion on the team computer, from approved scripts and assets. - [launch_day](https://koshra.si/roles/launch_day): Plan and run launch day: the hour-by-hour runbook, day-of reminders and the day-after summary. - [launch_press_list](https://koshra.si/roles/launch_press_list): Build the list of people to tell about a launch and draft a personal note for each. --- # youtube_desk: an AI employee for marketing > What Koshra's youtube_desk AI employee does: Draft a title, a thumbnail line and a short outline from a brief. Canonical: https://koshra.si/roles/youtube_desk Last updated: 2026-11-07 Team: [Marketing, content and launches](https://koshra.si/use_cases/marketing) ## Job Draft a title, a thumbnail line and a short outline from a brief. ## Voice Clear. The title says the outcome. ## Limit Drafts the package. You publish the video. ## Never - These are stated product limits, not a proof that every path is blocked - Payment, purchasing and moving money are refused by policy - Publishing, pushing code, changing DNS or changing a live system is refused by policy - Outbound messages still need the configured review. End-to-end coverage is not yet verified ## Works with - [chief_marketing_officer](https://koshra.si/roles/chief_marketing_officer): Turn one true customer fact into the brief a channel desk drafts from. - [chief_growth_officer](https://koshra.si/roles/chief_growth_officer): Design one growth loop: the input, the measure and the rule that kills it. - [x_desk](https://koshra.si/roles/x_desk): Draft a short X post from a brief. - [repurpose_desk](https://koshra.si/roles/repurpose_desk): Turn a winning post or a set of numbers you paste into the next draft. - [mentions_desk](https://koshra.si/roles/mentions_desk): Watch public mentions of your work and your competitors, and summarise what changed. - [content_community](https://koshra.si/roles/content_community): Draft replies to comments and messages on your connected accounts. - [content_video_editor](https://koshra.si/roles/content_video_editor): Edit short videos with Remotion on the team computer, from approved scripts and assets. - [launch_day](https://koshra.si/roles/launch_day): Plan and run launch day: the hour-by-hour runbook, day-of reminders and the day-after summary. - [launch_press_list](https://koshra.si/roles/launch_press_list): Build the list of people to tell about a launch and draft a personal note for each. --- # repurpose_desk: an AI employee for marketing > What Koshra's repurpose_desk AI employee does: Turn a winning post or a set of numbers you paste into the next draft. Canonical: https://koshra.si/roles/repurpose_desk Last updated: 2026-11-07 Team: [Marketing, content and launches](https://koshra.si/use_cases/marketing) ## Job Turn a winning post or a set of numbers you paste into the next draft. ## Voice Practical. What worked, then what to reuse. ## Limit Works from what you paste. ## Never - These are stated product limits, not a proof that every path is blocked - Payment, purchasing and moving money are refused by policy - Publishing, pushing code, changing DNS or changing a live system is refused by policy - Outbound messages still need the configured review. End-to-end coverage is not yet verified ## Works with - [chief_marketing_officer](https://koshra.si/roles/chief_marketing_officer): Turn one true customer fact into the brief a channel desk drafts from. - [chief_growth_officer](https://koshra.si/roles/chief_growth_officer): Design one growth loop: the input, the measure and the rule that kills it. - [x_desk](https://koshra.si/roles/x_desk): Draft a short X post from a brief. - [youtube_desk](https://koshra.si/roles/youtube_desk): Draft a title, a thumbnail line and a short outline from a brief. - [mentions_desk](https://koshra.si/roles/mentions_desk): Watch public mentions of your work and your competitors, and summarise what changed. - [content_community](https://koshra.si/roles/content_community): Draft replies to comments and messages on your connected accounts. - [content_video_editor](https://koshra.si/roles/content_video_editor): Edit short videos with Remotion on the team computer, from approved scripts and assets. - [launch_day](https://koshra.si/roles/launch_day): Plan and run launch day: the hour-by-hour runbook, day-of reminders and the day-after summary. - [launch_press_list](https://koshra.si/roles/launch_press_list): Build the list of people to tell about a launch and draft a personal note for each. --- # mentions_desk: an AI employee for marketing > What Koshra's mentions_desk AI employee does: Watch public mentions of your work and your competitors, and summarise what changed. Canonical: https://koshra.si/roles/mentions_desk Last updated: 2026-11-07 Team: [Marketing, content and launches](https://koshra.si/use_cases/marketing) ## Job Watch public mentions of your work and your competitors, and summarise what changed. ## Voice Reportorial. Quote, source and why it matters. ## Limit Summarises. Does not reply to the mention. ## Never - These are stated product limits, not a proof that every path is blocked - Payment, purchasing and moving money are refused by policy - Publishing, pushing code, changing DNS or changing a live system is refused by policy - Outbound messages still need the configured review. End-to-end coverage is not yet verified ## Works with - [chief_marketing_officer](https://koshra.si/roles/chief_marketing_officer): Turn one true customer fact into the brief a channel desk drafts from. - [chief_growth_officer](https://koshra.si/roles/chief_growth_officer): Design one growth loop: the input, the measure and the rule that kills it. - [x_desk](https://koshra.si/roles/x_desk): Draft a short X post from a brief. - [youtube_desk](https://koshra.si/roles/youtube_desk): Draft a title, a thumbnail line and a short outline from a brief. - [repurpose_desk](https://koshra.si/roles/repurpose_desk): Turn a winning post or a set of numbers you paste into the next draft. - [content_community](https://koshra.si/roles/content_community): Draft replies to comments and messages on your connected accounts. - [content_video_editor](https://koshra.si/roles/content_video_editor): Edit short videos with Remotion on the team computer, from approved scripts and assets. - [launch_day](https://koshra.si/roles/launch_day): Plan and run launch day: the hour-by-hour runbook, day-of reminders and the day-after summary. - [launch_press_list](https://koshra.si/roles/launch_press_list): Build the list of people to tell about a launch and draft a personal note for each. --- # content_community: an AI employee for marketing > What Koshra's content_community AI employee does: Draft replies to comments and messages on your connected accounts. Canonical: https://koshra.si/roles/content_community Last updated: 2026-11-07 Team: [Marketing, content and launches](https://koshra.si/use_cases/marketing) ## Job Draft replies to comments and messages on your connected accounts. ## Never - These are stated product limits, not a proof that every path is blocked - Payment, purchasing and moving money are refused by policy - Publishing, pushing code, changing DNS or changing a live system is refused by policy - Outbound messages still need the configured review. End-to-end coverage is not yet verified ## Works with - [chief_marketing_officer](https://koshra.si/roles/chief_marketing_officer): Turn one true customer fact into the brief a channel desk drafts from. - [chief_growth_officer](https://koshra.si/roles/chief_growth_officer): Design one growth loop: the input, the measure and the rule that kills it. - [x_desk](https://koshra.si/roles/x_desk): Draft a short X post from a brief. - [youtube_desk](https://koshra.si/roles/youtube_desk): Draft a title, a thumbnail line and a short outline from a brief. - [repurpose_desk](https://koshra.si/roles/repurpose_desk): Turn a winning post or a set of numbers you paste into the next draft. - [mentions_desk](https://koshra.si/roles/mentions_desk): Watch public mentions of your work and your competitors, and summarise what changed. - [content_video_editor](https://koshra.si/roles/content_video_editor): Edit short videos with Remotion on the team computer, from approved scripts and assets. - [launch_day](https://koshra.si/roles/launch_day): Plan and run launch day: the hour-by-hour runbook, day-of reminders and the day-after summary. - [launch_press_list](https://koshra.si/roles/launch_press_list): Build the list of people to tell about a launch and draft a personal note for each. --- # content_video_editor: an AI employee for marketing > What Koshra's content_video_editor AI employee does: Edit short videos with Remotion on the team computer, from approved scripts and assets. Canonical: https://koshra.si/roles/content_video_editor Last updated: 2026-11-07 Team: [Marketing, content and launches](https://koshra.si/use_cases/marketing) ## Job Edit short videos with Remotion on the team computer, from approved scripts and assets. ## Never - These are stated product limits, not a proof that every path is blocked - Payment, purchasing and moving money are refused by policy - Publishing, pushing code, changing DNS or changing a live system is refused by policy - Outbound messages still need the configured review. End-to-end coverage is not yet verified ## Works with - [chief_marketing_officer](https://koshra.si/roles/chief_marketing_officer): Turn one true customer fact into the brief a channel desk drafts from. - [chief_growth_officer](https://koshra.si/roles/chief_growth_officer): Design one growth loop: the input, the measure and the rule that kills it. - [x_desk](https://koshra.si/roles/x_desk): Draft a short X post from a brief. - [youtube_desk](https://koshra.si/roles/youtube_desk): Draft a title, a thumbnail line and a short outline from a brief. - [repurpose_desk](https://koshra.si/roles/repurpose_desk): Turn a winning post or a set of numbers you paste into the next draft. - [mentions_desk](https://koshra.si/roles/mentions_desk): Watch public mentions of your work and your competitors, and summarise what changed. - [content_community](https://koshra.si/roles/content_community): Draft replies to comments and messages on your connected accounts. - [launch_day](https://koshra.si/roles/launch_day): Plan and run launch day: the hour-by-hour runbook, day-of reminders and the day-after summary. - [launch_press_list](https://koshra.si/roles/launch_press_list): Build the list of people to tell about a launch and draft a personal note for each. --- # launch_day: an AI employee for marketing > What Koshra's launch_day AI employee does: Plan and run launch day: the hour-by-hour runbook, day-of reminders and the day-after summary. Canonical: https://koshra.si/roles/launch_day Last updated: 2026-11-07 Team: [Marketing, content and launches](https://koshra.si/use_cases/marketing) ## Job Plan and run launch day: the hour-by-hour runbook, day-of reminders and the day-after summary. ## Never - These are stated product limits, not a proof that every path is blocked - Payment, purchasing and moving money are refused by policy - Publishing, pushing code, changing DNS or changing a live system is refused by policy - Outbound messages still need the configured review. End-to-end coverage is not yet verified ## Works with - [chief_marketing_officer](https://koshra.si/roles/chief_marketing_officer): Turn one true customer fact into the brief a channel desk drafts from. - [chief_growth_officer](https://koshra.si/roles/chief_growth_officer): Design one growth loop: the input, the measure and the rule that kills it. - [x_desk](https://koshra.si/roles/x_desk): Draft a short X post from a brief. - [youtube_desk](https://koshra.si/roles/youtube_desk): Draft a title, a thumbnail line and a short outline from a brief. - [repurpose_desk](https://koshra.si/roles/repurpose_desk): Turn a winning post or a set of numbers you paste into the next draft. - [mentions_desk](https://koshra.si/roles/mentions_desk): Watch public mentions of your work and your competitors, and summarise what changed. - [content_community](https://koshra.si/roles/content_community): Draft replies to comments and messages on your connected accounts. - [content_video_editor](https://koshra.si/roles/content_video_editor): Edit short videos with Remotion on the team computer, from approved scripts and assets. - [launch_press_list](https://koshra.si/roles/launch_press_list): Build the list of people to tell about a launch and draft a personal note for each. --- # launch_press_list: an AI employee for marketing > What Koshra's launch_press_list AI employee does: Build the list of people to tell about a launch and draft a personal note for each. Canonical: https://koshra.si/roles/launch_press_list Last updated: 2026-11-07 Team: [Marketing, content and launches](https://koshra.si/use_cases/marketing) ## Job Build the list of people to tell about a launch and draft a personal note for each. ## Never - These are stated product limits, not a proof that every path is blocked - Payment, purchasing and moving money are refused by policy - Publishing, pushing code, changing DNS or changing a live system is refused by policy - Outbound messages still need the configured review. End-to-end coverage is not yet verified ## Works with - [chief_marketing_officer](https://koshra.si/roles/chief_marketing_officer): Turn one true customer fact into the brief a channel desk drafts from. - [chief_growth_officer](https://koshra.si/roles/chief_growth_officer): Design one growth loop: the input, the measure and the rule that kills it. - [x_desk](https://koshra.si/roles/x_desk): Draft a short X post from a brief. - [youtube_desk](https://koshra.si/roles/youtube_desk): Draft a title, a thumbnail line and a short outline from a brief. - [repurpose_desk](https://koshra.si/roles/repurpose_desk): Turn a winning post or a set of numbers you paste into the next draft. - [mentions_desk](https://koshra.si/roles/mentions_desk): Watch public mentions of your work and your competitors, and summarise what changed. - [content_community](https://koshra.si/roles/content_community): Draft replies to comments and messages on your connected accounts. - [content_video_editor](https://koshra.si/roles/content_video_editor): Edit short videos with Remotion on the team computer, from approved scripts and assets. - [launch_day](https://koshra.si/roles/launch_day): Plan and run launch day: the hour-by-hour runbook, day-of reminders and the day-after summary. --- # client_lead: an AI employee for client services > What Koshra's client_lead AI employee does: Coordinate client proposals, delivery plans and client follow-ups, from request to signed scope. Canonical: https://koshra.si/roles/client_lead Last updated: 2026-11-07 Team: [Client services](https://koshra.si/use_cases/client_services) ## Job Coordinate client proposals, delivery plans and client follow-ups, from request to signed scope. ## Never - These are stated product limits, not a proof that every path is blocked - Payment, purchasing and moving money are refused by policy - Publishing, pushing code, changing DNS or changing a live system is refused by policy - Outbound messages still need the configured review. End-to-end coverage is not yet verified ## Works with - [client_proposal_writer](https://koshra.si/roles/client_proposal_writer): Write client proposals from the agreed requirements. --- # client_proposal_writer: an AI employee for client services > What Koshra's client_proposal_writer AI employee does: Write client proposals from the agreed requirements. Canonical: https://koshra.si/roles/client_proposal_writer Last updated: 2026-11-07 Team: [Client services](https://koshra.si/use_cases/client_services) ## Job Write client proposals from the agreed requirements. ## Never - These are stated product limits, not a proof that every path is blocked - Payment, purchasing and moving money are refused by policy - Publishing, pushing code, changing DNS or changing a live system is refused by policy - Outbound messages still need the configured review. End-to-end coverage is not yet verified ## Works with - [client_lead](https://koshra.si/roles/client_lead): Coordinate client proposals, delivery plans and client follow-ups, from request to signed scope. --- # support_lead: an AI employee for support > What Koshra's support_lead AI employee does: Run the customer support queue: set up where questions arrive and where answers come from, keep it moving and report what needs you. Canonical: https://koshra.si/roles/support_lead Last updated: 2026-11-07 Team: [Customer support](https://koshra.si/use_cases/support) ## Job Run the customer support queue: set up where questions arrive and where answers come from, keep it moving and report what needs you. ## Never - These are stated product limits, not a proof that every path is blocked - Payment, purchasing and moving money are refused by policy - Publishing, pushing code, changing DNS or changing a live system is refused by policy - Outbound messages still need the configured review. End-to-end coverage is not yet verified ## Works with - [support_triage](https://koshra.si/roles/support_triage): Sort every new customer question by type, urgency and customer. - [support_answers](https://koshra.si/roles/support_answers): Draft replies to customer questions from your docs and past answers. - [support_escalations](https://koshra.si/roles/support_escalations): Take the customer questions that need your decision and make them easy for you to handle. --- # support_triage: an AI employee for support > What Koshra's support_triage AI employee does: Sort every new customer question by type, urgency and customer. Canonical: https://koshra.si/roles/support_triage Last updated: 2026-11-07 Team: [Customer support](https://koshra.si/use_cases/support) ## Job Sort every new customer question by type, urgency and customer. ## Never - These are stated product limits, not a proof that every path is blocked - Payment, purchasing and moving money are refused by policy - Publishing, pushing code, changing DNS or changing a live system is refused by policy - Outbound messages still need the configured review. End-to-end coverage is not yet verified ## Works with - [support_lead](https://koshra.si/roles/support_lead): Run the customer support queue: set up where questions arrive and where answers come from, keep it moving and report what needs you. - [support_answers](https://koshra.si/roles/support_answers): Draft replies to customer questions from your docs and past answers. - [support_escalations](https://koshra.si/roles/support_escalations): Take the customer questions that need your decision and make them easy for you to handle. --- # support_answers: an AI employee for support > What Koshra's support_answers AI employee does: Draft replies to customer questions from your docs and past answers. Canonical: https://koshra.si/roles/support_answers Last updated: 2026-11-07 Team: [Customer support](https://koshra.si/use_cases/support) ## Job Draft replies to customer questions from your docs and past answers. ## Never - These are stated product limits, not a proof that every path is blocked - Payment, purchasing and moving money are refused by policy - Publishing, pushing code, changing DNS or changing a live system is refused by policy - Outbound messages still need the configured review. End-to-end coverage is not yet verified ## Works with - [support_lead](https://koshra.si/roles/support_lead): Run the customer support queue: set up where questions arrive and where answers come from, keep it moving and report what needs you. - [support_triage](https://koshra.si/roles/support_triage): Sort every new customer question by type, urgency and customer. - [support_escalations](https://koshra.si/roles/support_escalations): Take the customer questions that need your decision and make them easy for you to handle. --- # support_escalations: an AI employee for support > What Koshra's support_escalations AI employee does: Take the customer questions that need your decision and make them easy for you to handle. Canonical: https://koshra.si/roles/support_escalations Last updated: 2026-11-07 Team: [Customer support](https://koshra.si/use_cases/support) ## Job Take the customer questions that need your decision and make them easy for you to handle. ## Never - These are stated product limits, not a proof that every path is blocked - Payment, purchasing and moving money are refused by policy - Publishing, pushing code, changing DNS or changing a live system is refused by policy - Outbound messages still need the configured review. End-to-end coverage is not yet verified ## Works with - [support_lead](https://koshra.si/roles/support_lead): Run the customer support queue: set up where questions arrive and where answers come from, keep it moving and report what needs you. - [support_triage](https://koshra.si/roles/support_triage): Sort every new customer question by type, urgency and customer. - [support_answers](https://koshra.si/roles/support_answers): Draft replies to customer questions from your docs and past answers. --- # talent_desk: an AI employee for recruiting > What Koshra's talent_desk AI employee does: Name the next hire, the bar and why the seat is not already covered. Canonical: https://koshra.si/roles/talent_desk Last updated: 2026-11-07 Team: [Recruiting](https://koshra.si/use_cases/recruiting) ## Job Name the next hire, the bar and why the seat is not already covered. ## Never - These are stated product limits, not a proof that every path is blocked - Payment, purchasing and moving money are refused by policy - Publishing, pushing code, changing DNS or changing a live system is refused by policy - Outbound messages still need the configured review. End-to-end coverage is not yet verified ## Works with - [recruiting_sourcer](https://koshra.si/roles/recruiting_sourcer): Find candidates who meet the approved scorecard and keep the candidate list. - [recruiting_screener](https://koshra.si/roles/recruiting_screener): Score each sourced candidate against the approved scorecard and recommend advance, maybe or pass. - [recruiting_scheduler](https://koshra.si/roles/recruiting_scheduler): Book first calls with candidates who reply and want to talk. --- # recruiting_sourcer: an AI employee for recruiting > What Koshra's recruiting_sourcer AI employee does: Find candidates who meet the approved scorecard and keep the candidate list. Canonical: https://koshra.si/roles/recruiting_sourcer Last updated: 2026-11-07 Team: [Recruiting](https://koshra.si/use_cases/recruiting) ## Job Find candidates who meet the approved scorecard and keep the candidate list. ## Never - These are stated product limits, not a proof that every path is blocked - Payment, purchasing and moving money are refused by policy - Publishing, pushing code, changing DNS or changing a live system is refused by policy - Outbound messages still need the configured review. End-to-end coverage is not yet verified ## Works with - [talent_desk](https://koshra.si/roles/talent_desk): Name the next hire, the bar and why the seat is not already covered. - [recruiting_screener](https://koshra.si/roles/recruiting_screener): Score each sourced candidate against the approved scorecard and recommend advance, maybe or pass. - [recruiting_scheduler](https://koshra.si/roles/recruiting_scheduler): Book first calls with candidates who reply and want to talk. --- # recruiting_screener: an AI employee for recruiting > What Koshra's recruiting_screener AI employee does: Score each sourced candidate against the approved scorecard and recommend advance, maybe or pass. Canonical: https://koshra.si/roles/recruiting_screener Last updated: 2026-11-07 Team: [Recruiting](https://koshra.si/use_cases/recruiting) ## Job Score each sourced candidate against the approved scorecard and recommend advance, maybe or pass. ## Never - These are stated product limits, not a proof that every path is blocked - Payment, purchasing and moving money are refused by policy - Publishing, pushing code, changing DNS or changing a live system is refused by policy - Outbound messages still need the configured review. End-to-end coverage is not yet verified ## Works with - [talent_desk](https://koshra.si/roles/talent_desk): Name the next hire, the bar and why the seat is not already covered. - [recruiting_sourcer](https://koshra.si/roles/recruiting_sourcer): Find candidates who meet the approved scorecard and keep the candidate list. - [recruiting_scheduler](https://koshra.si/roles/recruiting_scheduler): Book first calls with candidates who reply and want to talk. --- # recruiting_scheduler: an AI employee for recruiting > What Koshra's recruiting_scheduler AI employee does: Book first calls with candidates who reply and want to talk. Canonical: https://koshra.si/roles/recruiting_scheduler Last updated: 2026-11-07 Team: [Recruiting](https://koshra.si/use_cases/recruiting) ## Job Book first calls with candidates who reply and want to talk. ## Never - These are stated product limits, not a proof that every path is blocked - Payment, purchasing and moving money are refused by policy - Publishing, pushing code, changing DNS or changing a live system is refused by policy - Outbound messages still need the configured review. End-to-end coverage is not yet verified ## Works with - [talent_desk](https://koshra.si/roles/talent_desk): Name the next hire, the bar and why the seat is not already covered. - [recruiting_sourcer](https://koshra.si/roles/recruiting_sourcer): Find candidates who meet the approved scorecard and keep the candidate list. - [recruiting_screener](https://koshra.si/roles/recruiting_screener): Score each sourced candidate against the approved scorecard and recommend advance, maybe or pass. --- # research_lead: an AI employee for research > What Koshra's research_lead AI employee does: Coordinate source-grounded answers: the question, the sources, the analysis, a review and a verified answer that names its gaps. Canonical: https://koshra.si/roles/research_lead Last updated: 2026-11-07 Team: [Research](https://koshra.si/use_cases/research) ## Job Coordinate source-grounded answers: the question, the sources, the analysis, a review and a verified answer that names its gaps. ## Never - These are stated product limits, not a proof that every path is blocked - Payment, purchasing and moving money are refused by policy - Publishing, pushing code, changing DNS or changing a live system is refused by policy - Outbound messages still need the configured review. End-to-end coverage is not yet verified ## Works with - [research_evidence_reviewer](https://koshra.si/roles/research_evidence_reviewer): Check every material claim in a research draft against its cited source. - [distill_desk](https://koshra.si/roles/distill_desk): Turn a named person's public writing, or a transcript you paste, into a consultant brief. --- # research_evidence_reviewer: an AI employee for research > What Koshra's research_evidence_reviewer AI employee does: Check every material claim in a research draft against its cited source. Canonical: https://koshra.si/roles/research_evidence_reviewer Last updated: 2026-11-07 Team: [Research](https://koshra.si/use_cases/research) ## Job Check every material claim in a research draft against its cited source. ## Never - These are stated product limits, not a proof that every path is blocked - Payment, purchasing and moving money are refused by policy - Publishing, pushing code, changing DNS or changing a live system is refused by policy - Outbound messages still need the configured review. End-to-end coverage is not yet verified ## Works with - [research_lead](https://koshra.si/roles/research_lead): Coordinate source-grounded answers: the question, the sources, the analysis, a review and a verified answer that names its gaps. - [distill_desk](https://koshra.si/roles/distill_desk): Turn a named person's public writing, or a transcript you paste, into a consultant brief. --- # distill_desk: an AI employee for research > What Koshra's distill_desk AI employee does: Turn a named person's public writing, or a transcript you paste, into a consultant brief. Canonical: https://koshra.si/roles/distill_desk Last updated: 2026-11-07 Team: [Research](https://koshra.si/use_cases/research) ## Job Turn a named person's public writing, or a transcript you paste, into a consultant brief. ## Voice Careful and sourced. A point without a line from the source is a guess. ## Limit The brief is about that person. It is not a message from them, and it never posts as them. ## Never - These are stated product limits, not a proof that every path is blocked - Payment, purchasing and moving money are refused by policy - Publishing, pushing code, changing DNS or changing a live system is refused by policy - Outbound messages still need the configured review. End-to-end coverage is not yet verified ## Works with - [research_lead](https://koshra.si/roles/research_lead): Coordinate source-grounded answers: the question, the sources, the analysis, a review and a verified answer that names its gaps. - [research_evidence_reviewer](https://koshra.si/roles/research_evidence_reviewer): Check every material claim in a research draft against its cited source. --- # product_lead: an AI employee for product and platform > What Koshra's product_lead AI employee does: Name what to build, what to refuse and the smallest version. Canonical: https://koshra.si/roles/product_lead Last updated: 2026-11-07 Team: [Product, platform and security](https://koshra.si/use_cases/product_platform) ## Job Name what to build, what to refuse and the smallest version. ## Never - These are stated product limits, not a proof that every path is blocked - Payment, purchasing and moving money are refused by policy - Publishing, pushing code, changing DNS or changing a live system is refused by policy - Outbound messages still need the configured review. End-to-end coverage is not yet verified ## Works with - [design_desk](https://koshra.si/roles/design_desk): Design one product surface at a time. - [platform_lead](https://koshra.si/roles/platform_lead): Design and build the systems you run, inside the rules chief_ai_officer sets. - [chief_ai_officer](https://koshra.si/roles/chief_ai_officer): Decide which model and which tool a desk may use, and whether an automation is allowed. - [chief_security_officer](https://koshra.si/roles/chief_security_officer): Review a plan you paste. Name the data it touches, who can see it and what to refuse. - [counsel](https://koshra.si/roles/counsel): Draft a review of terms you paste. You decide. - [routines_desk](https://koshra.si/roles/routines_desk): Write an overnight routine as a checklist with an owner and a stop condition. --- # design_desk: an AI employee for product and platform > What Koshra's design_desk AI employee does: Design one product surface at a time. Canonical: https://koshra.si/roles/design_desk Last updated: 2026-11-07 Team: [Product, platform and security](https://koshra.si/use_cases/product_platform) ## Job Design one product surface at a time. ## Never - These are stated product limits, not a proof that every path is blocked - Payment, purchasing and moving money are refused by policy - Publishing, pushing code, changing DNS or changing a live system is refused by policy - Outbound messages still need the configured review. End-to-end coverage is not yet verified ## Works with - [product_lead](https://koshra.si/roles/product_lead): Name what to build, what to refuse and the smallest version. - [platform_lead](https://koshra.si/roles/platform_lead): Design and build the systems you run, inside the rules chief_ai_officer sets. - [chief_ai_officer](https://koshra.si/roles/chief_ai_officer): Decide which model and which tool a desk may use, and whether an automation is allowed. - [chief_security_officer](https://koshra.si/roles/chief_security_officer): Review a plan you paste. Name the data it touches, who can see it and what to refuse. - [counsel](https://koshra.si/roles/counsel): Draft a review of terms you paste. You decide. - [routines_desk](https://koshra.si/roles/routines_desk): Write an overnight routine as a checklist with an owner and a stop condition. --- # platform_lead: an AI employee for product and platform > What Koshra's platform_lead AI employee does: Design and build the systems you run, inside the rules chief_ai_officer sets. Canonical: https://koshra.si/roles/platform_lead Last updated: 2026-11-07 Team: [Product, platform and security](https://koshra.si/use_cases/product_platform) ## Job Design and build the systems you run, inside the rules chief_ai_officer sets. ## Voice Precise. The file, the constraint and the tradeoff. ## Limit The one desk allowed on the shared team computer. Does not add an MCP server or spend money. ## Never - These are stated product limits, not a proof that every path is blocked - Payment, purchasing and moving money are refused by policy - Publishing, pushing code, changing DNS or changing a live system is refused by policy - Outbound messages still need the configured review. End-to-end coverage is not yet verified ## Works with - [product_lead](https://koshra.si/roles/product_lead): Name what to build, what to refuse and the smallest version. - [design_desk](https://koshra.si/roles/design_desk): Design one product surface at a time. - [chief_ai_officer](https://koshra.si/roles/chief_ai_officer): Decide which model and which tool a desk may use, and whether an automation is allowed. - [chief_security_officer](https://koshra.si/roles/chief_security_officer): Review a plan you paste. Name the data it touches, who can see it and what to refuse. - [counsel](https://koshra.si/roles/counsel): Draft a review of terms you paste. You decide. - [routines_desk](https://koshra.si/roles/routines_desk): Write an overnight routine as a checklist with an owner and a stop condition. --- # chief_ai_officer: an AI employee for product and platform > What Koshra's chief_ai_officer AI employee does: Decide which model and which tool a desk may use, and whether an automation is allowed. Canonical: https://koshra.si/roles/chief_ai_officer Last updated: 2026-11-07 Team: [Product, platform and security](https://koshra.si/use_cases/product_platform) ## Job Decide which model and which tool a desk may use, and whether an automation is allowed. ## Voice Precise. The tool, the limit and the reason. ## Limit Sets the rule. Does not add an MCP server, spend or run the computer. ## Never - These are stated product limits, not a proof that every path is blocked - Payment, purchasing and moving money are refused by policy - Publishing, pushing code, changing DNS or changing a live system is refused by policy - Outbound messages still need the configured review. End-to-end coverage is not yet verified ## Works with - [product_lead](https://koshra.si/roles/product_lead): Name what to build, what to refuse and the smallest version. - [design_desk](https://koshra.si/roles/design_desk): Design one product surface at a time. - [platform_lead](https://koshra.si/roles/platform_lead): Design and build the systems you run, inside the rules chief_ai_officer sets. - [chief_security_officer](https://koshra.si/roles/chief_security_officer): Review a plan you paste. Name the data it touches, who can see it and what to refuse. - [counsel](https://koshra.si/roles/counsel): Draft a review of terms you paste. You decide. - [routines_desk](https://koshra.si/roles/routines_desk): Write an overnight routine as a checklist with an owner and a stop condition. --- # chief_security_officer: an AI employee for product and platform > What Koshra's chief_security_officer AI employee does: Review a plan you paste. Name the data it touches, who can see it and what to refuse. Canonical: https://koshra.si/roles/chief_security_officer Last updated: 2026-11-07 Team: [Product, platform and security](https://koshra.si/use_cases/product_platform) ## Job Review a plan you paste. Name the data it touches, who can see it and what to refuse. ## Voice Plain. The risk, then the refusal. ## Limit Reviews plans. Does not probe, scan or break a system, and does not write an exploit. ## Never - These are stated product limits, not a proof that every path is blocked - Payment, purchasing and moving money are refused by policy - Publishing, pushing code, changing DNS or changing a live system is refused by policy - Outbound messages still need the configured review. End-to-end coverage is not yet verified ## Works with - [product_lead](https://koshra.si/roles/product_lead): Name what to build, what to refuse and the smallest version. - [design_desk](https://koshra.si/roles/design_desk): Design one product surface at a time. - [platform_lead](https://koshra.si/roles/platform_lead): Design and build the systems you run, inside the rules chief_ai_officer sets. - [chief_ai_officer](https://koshra.si/roles/chief_ai_officer): Decide which model and which tool a desk may use, and whether an automation is allowed. - [counsel](https://koshra.si/roles/counsel): Draft a review of terms you paste. You decide. - [routines_desk](https://koshra.si/roles/routines_desk): Write an overnight routine as a checklist with an owner and a stop condition. --- # counsel: an AI employee for product and platform > What Koshra's counsel AI employee does: Draft a review of terms you paste. You decide. Canonical: https://koshra.si/roles/counsel Last updated: 2026-11-07 Team: [Product, platform and security](https://koshra.si/use_cases/product_platform) ## Job Draft a review of terms you paste. You decide. ## Limit Not a law firm. ## Never - These are stated product limits, not a proof that every path is blocked - Payment, purchasing and moving money are refused by policy - Publishing, pushing code, changing DNS or changing a live system is refused by policy - Outbound messages still need the configured review. End-to-end coverage is not yet verified ## Works with - [product_lead](https://koshra.si/roles/product_lead): Name what to build, what to refuse and the smallest version. - [design_desk](https://koshra.si/roles/design_desk): Design one product surface at a time. - [platform_lead](https://koshra.si/roles/platform_lead): Design and build the systems you run, inside the rules chief_ai_officer sets. - [chief_ai_officer](https://koshra.si/roles/chief_ai_officer): Decide which model and which tool a desk may use, and whether an automation is allowed. - [chief_security_officer](https://koshra.si/roles/chief_security_officer): Review a plan you paste. Name the data it touches, who can see it and what to refuse. - [routines_desk](https://koshra.si/roles/routines_desk): Write an overnight routine as a checklist with an owner and a stop condition. --- # routines_desk: an AI employee for product and platform > What Koshra's routines_desk AI employee does: Write an overnight routine as a checklist with an owner and a stop condition. Canonical: https://koshra.si/roles/routines_desk Last updated: 2026-11-07 Team: [Product, platform and security](https://koshra.si/use_cases/product_platform) ## Job Write an overnight routine as a checklist with an owner and a stop condition. ## Voice Operational. Step, owner, stop. ## Limit Does not create a schedule. A schedule starts only when you ask for it, and creating one needs your approval. ## Never - These are stated product limits, not a proof that every path is blocked - Payment, purchasing and moving money are refused by policy - Publishing, pushing code, changing DNS or changing a live system is refused by policy - Outbound messages still need the configured review. End-to-end coverage is not yet verified ## Works with - [product_lead](https://koshra.si/roles/product_lead): Name what to build, what to refuse and the smallest version. - [design_desk](https://koshra.si/roles/design_desk): Design one product surface at a time. - [platform_lead](https://koshra.si/roles/platform_lead): Design and build the systems you run, inside the rules chief_ai_officer sets. - [chief_ai_officer](https://koshra.si/roles/chief_ai_officer): Decide which model and which tool a desk may use, and whether an automation is allowed. - [chief_security_officer](https://koshra.si/roles/chief_security_officer): Review a plan you paste. Name the data it touches, who can see it and what to refuse. - [counsel](https://koshra.si/roles/counsel): Draft a review of terms you paste. You decide. --- # Koshra integrations > The apps and MCP servers Koshra bots use, how each is reached and the approval rules on each, from our own Koshra workspace and the Koshra app catalog. Canonical: https://koshra.si/integrations Last updated: 2026-11-07 Bots reach apps through per-bot MCP servers and app connections. Each bot only gets the apps its role needs, and every tool call is checked against Allow, Ask or Block rules. ## How bots connect - Per-bot MCP server: Each bot gets its own MCP server for this app, with its own key, so access is scoped to that bot. - Nango connection: Reached through a Nango connection. Each role has an allowlist of apps; reads are open and writes stop on an approval card. - Composio connection: Reached through a Composio connection, with a per-bot allowlist so each bot only sees the apps its role needs. - Built in: Part of the Koshra server itself. ## Chat and email - [Slack](https://koshra.si/integrations/slack): Bots read and draft in Slack, and each bot posts under its own role name so you can see who said what. - [Bot email inboxes](https://koshra.si/integrations/email_inboxes): Each bot can have its own email inbox. It reads its mail freely and drafts replies. - [Gmail](https://koshra.si/integrations/gmail): Bots read and draft in your Gmail. Google Workspace can also be connected inside the Koshra app. - [Microsoft Teams](https://koshra.si/integrations/microsoft_teams) (app catalog): Bots read channels and chats they are given and draft replies, for teams that work in Teams rather than Slack. - [Outlook](https://koshra.si/integrations/outlook) (app catalog): Bots read mail and calendar in Outlook and draft replies and meeting prep. ## Google Workspace - [Google Calendar](https://koshra.si/integrations/google_calendar): Bots read your calendar to prepare for meetings and propose times. - [Google Drive](https://koshra.si/integrations/google_drive): Bots find and read the files they need for a task. - [Google Docs](https://koshra.si/integrations/google_docs): Bots read docs and draft new ones, such as a brief or a proposal. - [Google Sheets](https://koshra.si/integrations/google_sheets): Bots read and update sheets, such as an account list or a scorecard. - [Google Meet](https://koshra.si/integrations/google_meet): Bots see your Meet calls so a meeting can become a meeting record. - [Google Tasks](https://koshra.si/integrations/google_tasks): Bots read and add to your Google Tasks lists. - [Google Maps](https://koshra.si/integrations/google_maps): Bots look up places and addresses during research. ## CRM and sales - [HubSpot](https://koshra.si/integrations/hubspot): Revenue desks read contacts, companies and deals, and propose clean-ups. - [Twenty CRM](https://koshra.si/integrations/twenty): Bots read and update the open-source Twenty CRM with a key of their own, so every change shows which bot made it. - [Clay](https://koshra.si/integrations/clay): Revenue desks read Clay tables and plan enrichment columns. Only go-to-market bots get it. - [Apollo](https://koshra.si/integrations/apollo): Revenue desks look up companies and people for research and enrichment. - [Salesforce](https://koshra.si/integrations/salesforce) (app catalog): Revenue desks read accounts, contacts and opportunities to research a deal and propose updates. - [Pipedrive](https://koshra.si/integrations/pipedrive) (app catalog): Revenue desks read deals and people, and draft follow-ups for deals that have gone quiet. - [Attio](https://koshra.si/integrations/attio) (app catalog): Revenue desks read records and lists, and propose enrichment and clean-ups. - [Close](https://koshra.si/integrations/close) (app catalog): Revenue desks read leads and activity, and draft the next touch for each lead. - [Zoho CRM](https://koshra.si/integrations/zoho) (app catalog): Revenue desks read leads, accounts and deals, and propose updates. ## Projects and engineering - [Plane](https://koshra.si/integrations/plane): Bots track work in the open-source Plane project tracker, each as a member with its own token. - [Linear](https://koshra.si/integrations/linear): Bots read and file issues in Linear. - [ClickUp](https://koshra.si/integrations/clickup): Bots read and update tasks in ClickUp. - [Notion](https://koshra.si/integrations/notion): Bots read pages and databases in Notion for context. - [GitHub](https://koshra.si/integrations/github): Platform and product bots read repositories, issues and pull requests. - [Vercel](https://koshra.si/integrations/vercel): Platform bots read projects and deployments. - [Neon](https://koshra.si/integrations/neon): Platform bots read Neon Postgres projects. - [Jira](https://koshra.si/integrations/jira) (app catalog): Bots read issues and boards, write up bugs and status, and propose new issues. - [Asana](https://koshra.si/integrations/asana) (app catalog): Bots read projects and tasks, write status updates and propose next tasks. - [Trello](https://koshra.si/integrations/trello) (app catalog): Bots read boards and cards and propose moves and new cards. - [Airtable](https://koshra.si/integrations/airtable) (app catalog): Bots read bases, such as a content calendar or an account list, and propose updates. ## Customer support - [Zendesk](https://koshra.si/integrations/zendesk) (app catalog): Support desks read tickets, sort them by urgency and draft answers from your help content. - [Intercom](https://koshra.si/integrations/intercom) (app catalog): Support desks read conversations and draft replies for a person to send. - [Freshdesk](https://koshra.si/integrations/freshdesk) (app catalog): Support desks read tickets, tag and route them, and draft answers. ## Meetings and scheduling - [Zoom](https://koshra.si/integrations/zoom) (app catalog): Bots see meetings and recordings so a call can become notes, decisions and follow-ups. - [Calendly](https://koshra.si/integrations/calendly) (app catalog): Bots read event types and bookings to prepare for calls and offer booking links. - [Gong](https://koshra.si/integrations/gong) (app catalog): Revenue desks read call notes and deal signals to prepare the next step. - [Fireflies](https://koshra.si/integrations/fireflies) (app catalog): Bots read meeting transcripts to write up decisions and follow-ups. ## Files and documents - [Confluence](https://koshra.si/integrations/confluence) (app catalog): Bots read pages so answers and briefs use what your team already wrote down. - [Dropbox](https://koshra.si/integrations/dropbox) (app catalog): Bots find and read the files a task needs, such as a past proposal. - [OneDrive](https://koshra.si/integrations/one_drive) (app catalog): Bots find and read files in OneDrive for a task. - [SharePoint](https://koshra.si/integrations/share_point) (app catalog): Bots read SharePoint sites and documents so answers use your own policies and notes. ## Recruiting - [Greenhouse](https://koshra.si/integrations/greenhouse) (app catalog): Recruiting desks read roles and candidates, prepare screens and draft notes. - [Lever](https://koshra.si/integrations/lever) (app catalog): Recruiting desks read postings and candidates, and draft outreach and screen notes. ## Finance and payments - [Stripe](https://koshra.si/integrations/stripe) (app catalog): Finance desks read payments, invoices and subscriptions for reports and follow-ups. - [QuickBooks](https://koshra.si/integrations/quickbooks) (app catalog): Finance desks read invoices, bills and reports to prepare a monthly summary. - [Xero](https://koshra.si/integrations/xero) (app catalog): Finance desks read invoices, bills and reports to prepare a monthly summary. ## Content and social - [YouTube](https://koshra.si/integrations/youtube): youtube_desk drafts a title, a thumbnail line and an outline. You upload and publish. - [Instagram](https://koshra.si/integrations/instagram): Content bots read your account to draft replies and next posts. - [Reddit](https://koshra.si/integrations/reddit): Research and mentions bots read public threads. - [Image generation](https://koshra.si/integrations/image_generation): Content and design bots generate draft images through a MiniMax image model. Only those bots get it. - [X](https://koshra.si/integrations/x) (coming soon): Read and draft on X from inside Koshra. x_desk drafts posts today; you post. - [Mailchimp](https://koshra.si/integrations/mailchimp) (app catalog): Marketing desks read audiences and campaigns and draft the next email for you to send. - [Webflow](https://koshra.si/integrations/webflow) (app catalog): Marketing desks read your site's collections and draft new pages and posts for review. ## Web research - [Firecrawl](https://koshra.si/integrations/firecrawl): Bots search and scrape public pages when a plain fetch is not enough. - [Scrapling](https://koshra.si/integrations/scrapling): A self-hosted scraper on the Koshra server. Bots fetch public pages and pick out elements with CSS selectors. ## Memory and knowledge - [Hindsight memory](https://koshra.si/integrations/hindsight): Each bot has a private Hindsight memory bank that keeps what it learns and recalls it in later chats. - [Mem0](https://koshra.si/integrations/mem0): A self-hosted Mem0 memory store that bots can read and add to. - [Code graph](https://koshra.si/integrations/graphify): A graph of your code that platform_lead can query to find where things live. - [nao analytics](https://koshra.si/integrations/nao): The nao analytics agent, connected over MCP with OAuth, so bots can ask questions of your data warehouse. ## Platform and connectors - [Voice](https://koshra.si/integrations/voice): Self-hosted speech, so bots can speak replies and take voice input. - [Cloudflare R2](https://koshra.si/integrations/cloudflare_r2): Files the bots make, such as reports and exports, are kept in Cloudflare R2 object storage. - [Nango](https://koshra.si/integrations/nango): A connection layer for many apps. Koshra keeps an allowlist of apps per role and holds every write for approval. - [Composio](https://koshra.si/integrations/composio): A connection layer for many apps. Koshra gives each bot its own allowlist, so it only sees what its role needs. - [Any MCP server](https://koshra.si/integrations/custom_mcp): Add any MCP server over streamable HTTP and its tools appear for the bots you choose, under the same Allow, Ask and Block rules as everything else. ## App catalog Apps marked app catalog are configuration-dependent and not individually validated here. A listing does not mean the app is connected or tested. --- # Slack integration > How Koshra AI employees use Slack: Bots read and draft in Slack, and each bot posts under its own role name so you can see who said what. Canonical: https://koshra.si/integrations/slack Last updated: 2026-11-07 Status: in use in our own Koshra workspace. Bots read and draft in Slack, and each bot posts under its own role name so you can see who said what. ## How bots reach it - Per-bot MCP server: Each bot gets its own MCP server for this app, with its own key, so access is scoped to that bot. ## Rules - Anything outbound waits on an approval card until you answer Allow. - Rules can mark any external Slack action as Ask. - Every tool call is checked against your Allow, Ask or Block rules first. Official site: https://slack.com --- # Bot email inboxes integration > How Koshra AI employees use Bot email inboxes: Each bot can have its own email inbox. It reads its mail freely and drafts replies. Canonical: https://koshra.si/integrations/email_inboxes Last updated: 2026-11-07 Status: in use in our own Koshra workspace. Each bot can have its own email inbox. It reads its mail freely and drafts replies. ## How bots reach it - Per-bot MCP server: Each bot gets its own MCP server for this app, with its own key, so access is scoped to that bot. - Built in: Part of the Koshra server itself. ## Rules - Every send needs your approval card. - Every tool call is checked against your Allow, Ask or Block rules first. --- # Gmail integration > How Koshra AI employees use Gmail: Bots read and draft in your Gmail. Google Workspace can also be connected inside the Koshra app. Canonical: https://koshra.si/integrations/gmail Last updated: 2026-11-07 Status: in use in our own Koshra workspace. Bots read and draft in your Gmail. Google Workspace can also be connected inside the Koshra app. ## How bots reach it - Composio connection: Reached through a Composio connection, with a per-bot allowlist so each bot only sees the apps its role needs. - Built in: Part of the Koshra server itself. ## Rules - Anything outbound waits on an approval card until you answer Allow. - Every tool call is checked against your Allow, Ask or Block rules first. Official site: https://mail.google.com --- # Google Calendar integration > How Koshra AI employees use Google Calendar: Bots read your calendar to prepare for meetings and propose times. Canonical: https://koshra.si/integrations/google_calendar Last updated: 2026-11-07 Status: in use in our own Koshra workspace. Bots read your calendar to prepare for meetings and propose times. ## How bots reach it - Composio connection: Reached through a Composio connection, with a per-bot allowlist so each bot only sees the apps its role needs. - Nango connection: Reached through a Nango connection. Each role has an allowlist of apps; reads are open and writes stop on an approval card. ## Rules - Creating or changing events follows your Allow, Ask or Block rules. - Every tool call is checked against your Allow, Ask or Block rules first. Official site: https://calendar.google.com --- # Google Drive integration > How Koshra AI employees use Google Drive: Bots find and read the files they need for a task. Canonical: https://koshra.si/integrations/google_drive Last updated: 2026-11-07 Status: in use in our own Koshra workspace. Bots find and read the files they need for a task. ## How bots reach it - Composio connection: Reached through a Composio connection, with a per-bot allowlist so each bot only sees the apps its role needs. - Nango connection: Reached through a Nango connection. Each role has an allowlist of apps; reads are open and writes stop on an approval card. ## Rules - Every tool call is checked against your Allow, Ask or Block rules first. Official site: https://drive.google.com --- # Google Docs integration > How Koshra AI employees use Google Docs: Bots read docs and draft new ones, such as a brief or a proposal. Canonical: https://koshra.si/integrations/google_docs Last updated: 2026-11-07 Status: in use in our own Koshra workspace. Bots read docs and draft new ones, such as a brief or a proposal. ## How bots reach it - Composio connection: Reached through a Composio connection, with a per-bot allowlist so each bot only sees the apps its role needs. ## Rules - Every tool call is checked against your Allow, Ask or Block rules first. Official site: https://docs.google.com --- # Google Sheets integration > How Koshra AI employees use Google Sheets: Bots read and update sheets, such as an account list or a scorecard. Canonical: https://koshra.si/integrations/google_sheets Last updated: 2026-11-07 Status: in use in our own Koshra workspace. Bots read and update sheets, such as an account list or a scorecard. ## How bots reach it - Composio connection: Reached through a Composio connection, with a per-bot allowlist so each bot only sees the apps its role needs. - Nango connection: Reached through a Nango connection. Each role has an allowlist of apps; reads are open and writes stop on an approval card. ## Rules - Every tool call is checked against your Allow, Ask or Block rules first. Official site: https://sheets.google.com --- # Google Meet integration > How Koshra AI employees use Google Meet: Bots see your Meet calls so a meeting can become a meeting record. Canonical: https://koshra.si/integrations/google_meet Last updated: 2026-11-07 Status: in use in our own Koshra workspace. Bots see your Meet calls so a meeting can become a meeting record. ## How bots reach it - Composio connection: Reached through a Composio connection, with a per-bot allowlist so each bot only sees the apps its role needs. ## Rules - Every tool call is checked against your Allow, Ask or Block rules first. Official site: https://meet.google.com --- # Google Tasks integration > How Koshra AI employees use Google Tasks: Bots read and add to your Google Tasks lists. Canonical: https://koshra.si/integrations/google_tasks Last updated: 2026-11-07 Status: in use in our own Koshra workspace. Bots read and add to your Google Tasks lists. ## How bots reach it - Composio connection: Reached through a Composio connection, with a per-bot allowlist so each bot only sees the apps its role needs. ## Rules - Every tool call is checked against your Allow, Ask or Block rules first. Official site: https://tasks.google.com --- # Google Maps integration > How Koshra AI employees use Google Maps: Bots look up places and addresses during research. Canonical: https://koshra.si/integrations/google_maps Last updated: 2026-11-07 Status: in use in our own Koshra workspace. Bots look up places and addresses during research. ## How bots reach it - Composio connection: Reached through a Composio connection, with a per-bot allowlist so each bot only sees the apps its role needs. ## Rules - Every tool call is checked against your Allow, Ask or Block rules first. Official site: https://maps.google.com --- # HubSpot integration > How Koshra AI employees use HubSpot: Revenue desks read contacts, companies and deals, and propose clean-ups. Canonical: https://koshra.si/integrations/hubspot Last updated: 2026-11-07 Status: in use in our own Koshra workspace. Revenue desks read contacts, companies and deals, and propose clean-ups. ## How bots reach it - Nango connection: Reached through a Nango connection. Each role has an allowlist of apps; reads are open and writes stop on an approval card. - Composio connection: Reached through a Composio connection, with a per-bot allowlist so each bot only sees the apps its role needs. ## Rules - Writes stop on an approval card. - Deletes and merges are blocked, and bulk changes or writes over 25 records need approval. - Every tool call is checked against your Allow, Ask or Block rules first. Official site: https://www.hubspot.com --- # Twenty CRM integration > How Koshra AI employees use Twenty CRM: Bots read and update the open-source Twenty CRM with a key of their own, so every change shows which bot made it. Canonical: https://koshra.si/integrations/twenty Last updated: 2026-11-07 Status: in use in our own Koshra workspace. Bots read and update the open-source Twenty CRM with a key of their own, so every change shows which bot made it. ## How bots reach it - Per-bot MCP server: Each bot gets its own MCP server for this app, with its own key, so access is scoped to that bot. ## Rules - Deletes and merges are blocked, and bulk changes or writes over 25 records need approval. - Every tool call is checked against your Allow, Ask or Block rules first. Official site: https://twenty.com --- # Clay integration > How Koshra AI employees use Clay: Revenue desks read Clay tables and plan enrichment columns. Only go-to-market bots get it. Canonical: https://koshra.si/integrations/clay Last updated: 2026-11-07 Status: in use in our own Koshra workspace. Revenue desks read Clay tables and plan enrichment columns. Only go-to-market bots get it. ## How bots reach it - Per-bot MCP server: Each bot gets its own MCP server for this app, with its own key, so access is scoped to that bot. ## Rules - Reads are open. Writes need your approval card. - Bots stay inside the one workspace you allow. - Every tool call is checked against your Allow, Ask or Block rules first. Official site: https://www.clay.com --- # Apollo integration > How Koshra AI employees use Apollo: Revenue desks look up companies and people for research and enrichment. Canonical: https://koshra.si/integrations/apollo Last updated: 2026-11-07 Status: in use in our own Koshra workspace. Revenue desks look up companies and people for research and enrichment. ## How bots reach it - Nango connection: Reached through a Nango connection. Each role has an allowlist of apps; reads are open and writes stop on an approval card. ## Rules - Writes stop on an approval card. - Every tool call is checked against your Allow, Ask or Block rules first. Official site: https://www.apollo.io --- # Plane integration > How Koshra AI employees use Plane: Bots track work in the open-source Plane project tracker, each as a member with its own token. Canonical: https://koshra.si/integrations/plane Last updated: 2026-11-07 Status: in use in our own Koshra workspace. Bots track work in the open-source Plane project tracker, each as a member with its own token. ## How bots reach it - Per-bot MCP server: Each bot gets its own MCP server for this app, with its own key, so access is scoped to that bot. ## Rules - Deleting or merging items is blocked. - Every tool call is checked against your Allow, Ask or Block rules first. Official site: https://plane.so --- # Linear integration > How Koshra AI employees use Linear: Bots read and file issues in Linear. Canonical: https://koshra.si/integrations/linear Last updated: 2026-11-07 Status: in use in our own Koshra workspace. Bots read and file issues in Linear. ## How bots reach it - Composio connection: Reached through a Composio connection, with a per-bot allowlist so each bot only sees the apps its role needs. ## Rules - Every tool call is checked against your Allow, Ask or Block rules first. Official site: https://linear.app --- # ClickUp integration > How Koshra AI employees use ClickUp: Bots read and update tasks in ClickUp. Canonical: https://koshra.si/integrations/clickup Last updated: 2026-11-07 Status: in use in our own Koshra workspace. Bots read and update tasks in ClickUp. ## How bots reach it - Composio connection: Reached through a Composio connection, with a per-bot allowlist so each bot only sees the apps its role needs. ## Rules - Every tool call is checked against your Allow, Ask or Block rules first. Official site: https://clickup.com --- # Notion integration > How Koshra AI employees use Notion: Bots read pages and databases in Notion for context. Canonical: https://koshra.si/integrations/notion Last updated: 2026-11-07 Status: in use in our own Koshra workspace. Bots read pages and databases in Notion for context. ## How bots reach it - Nango connection: Reached through a Nango connection. Each role has an allowlist of apps; reads are open and writes stop on an approval card. ## Rules - Writes stop on an approval card. - Every tool call is checked against your Allow, Ask or Block rules first. Official site: https://www.notion.so --- # GitHub integration > How Koshra AI employees use GitHub: Platform and product bots read repositories, issues and pull requests. Canonical: https://koshra.si/integrations/github Last updated: 2026-11-07 Status: in use in our own Koshra workspace. Platform and product bots read repositories, issues and pull requests. ## How bots reach it - Nango connection: Reached through a Nango connection. Each role has an allowlist of apps; reads are open and writes stop on an approval card. - Composio connection: Reached through a Composio connection, with a per-bot allowlist so each bot only sees the apps its role needs. ## Rules - Pushing code is outside every role's limits. - Every tool call is checked against your Allow, Ask or Block rules first. Official site: https://github.com --- # Vercel integration > How Koshra AI employees use Vercel: Platform bots read projects and deployments. Canonical: https://koshra.si/integrations/vercel Last updated: 2026-11-07 Status: in use in our own Koshra workspace. Platform bots read projects and deployments. ## How bots reach it - Nango connection: Reached through a Nango connection. Each role has an allowlist of apps; reads are open and writes stop on an approval card. ## Rules - Changing a live system is outside every role's limits. - Every tool call is checked against your Allow, Ask or Block rules first. Official site: https://vercel.com --- # Neon integration > How Koshra AI employees use Neon: Platform bots read Neon Postgres projects. Canonical: https://koshra.si/integrations/neon Last updated: 2026-11-07 Status: in use in our own Koshra workspace. Platform bots read Neon Postgres projects. ## How bots reach it - Composio connection: Reached through a Composio connection, with a per-bot allowlist so each bot only sees the apps its role needs. ## Rules - Every tool call is checked against your Allow, Ask or Block rules first. Official site: https://neon.tech --- # YouTube integration > How Koshra AI employees use YouTube: youtube_desk drafts a title, a thumbnail line and an outline. You upload and publish. Canonical: https://koshra.si/integrations/youtube Last updated: 2026-11-07 Status: in use in our own Koshra workspace. youtube_desk drafts a title, a thumbnail line and an outline. You upload and publish. ## How bots reach it - Composio connection: Reached through a Composio connection, with a per-bot allowlist so each bot only sees the apps its role needs. ## Rules - Bots do not publish. - Every tool call is checked against your Allow, Ask or Block rules first. Official site: https://www.youtube.com --- # Instagram integration > How Koshra AI employees use Instagram: Content bots read your account to draft replies and next posts. Canonical: https://koshra.si/integrations/instagram Last updated: 2026-11-07 Status: in use in our own Koshra workspace. Content bots read your account to draft replies and next posts. ## How bots reach it - Composio connection: Reached through a Composio connection, with a per-bot allowlist so each bot only sees the apps its role needs. ## Rules - Anything outbound waits on an approval card until you answer Allow. - Every tool call is checked against your Allow, Ask or Block rules first. Official site: https://www.instagram.com --- # Reddit integration > How Koshra AI employees use Reddit: Research and mentions bots read public threads. Canonical: https://koshra.si/integrations/reddit Last updated: 2026-11-07 Status: in use in our own Koshra workspace. Research and mentions bots read public threads. ## How bots reach it - Composio connection: Reached through a Composio connection, with a per-bot allowlist so each bot only sees the apps its role needs. ## Rules - Anything outbound waits on an approval card until you answer Allow. - Every tool call is checked against your Allow, Ask or Block rules first. Official site: https://www.reddit.com --- # Image generation integration > How Koshra AI employees use Image generation: Content and design bots generate draft images through a MiniMax image model. Only those bots get it. Canonical: https://koshra.si/integrations/image_generation Last updated: 2026-11-07 Status: in use in our own Koshra workspace. Content and design bots generate draft images through a MiniMax image model. Only those bots get it. ## How bots reach it - Per-bot MCP server: Each bot gets its own MCP server for this app, with its own key, so access is scoped to that bot. ## Rules - Every tool call is checked against your Allow, Ask or Block rules first. Official site: https://www.minimax.io --- # X integration > How Koshra AI employees use X (coming soon): Read and draft on X from inside Koshra. x_desk drafts posts today; you post. Canonical: https://koshra.si/integrations/x Last updated: 2026-11-07 Status: coming soon. Read and draft on X from inside Koshra. x_desk drafts posts today; you post. ## How bots reach it - Per-bot MCP server: Each bot gets its own MCP server for this app, with its own key, so access is scoped to that bot. ## Rules - Bots do not post. - Every tool call is checked against your Allow, Ask or Block rules first. Official site: https://x.com --- # Firecrawl integration > How Koshra AI employees use Firecrawl: Bots search and scrape public pages when a plain fetch is not enough. Canonical: https://koshra.si/integrations/firecrawl Last updated: 2026-11-07 Status: in use in our own Koshra workspace. Bots search and scrape public pages when a plain fetch is not enough. ## How bots reach it - Per-bot MCP server: Each bot gets its own MCP server for this app, with its own key, so access is scoped to that bot. ## Rules - Every tool call is checked against your Allow, Ask or Block rules first. Official site: https://www.firecrawl.dev --- # Scrapling integration > How Koshra AI employees use Scrapling: A self-hosted scraper on the Koshra server. Bots fetch public pages and pick out elements with CSS selectors. Canonical: https://koshra.si/integrations/scrapling Last updated: 2026-11-07 Status: in use in our own Koshra workspace. A self-hosted scraper on the Koshra server. Bots fetch public pages and pick out elements with CSS selectors. ## How bots reach it - Per-bot MCP server: Each bot gets its own MCP server for this app, with its own key, so access is scoped to that bot. ## Rules - Every tool call is checked against your Allow, Ask or Block rules first. Official site: https://github.com/D4Vinci/Scrapling --- # Hindsight memory integration > How Koshra AI employees use Hindsight memory: Each bot has a private Hindsight memory bank that keeps what it learns and recalls it in later chats. Canonical: https://koshra.si/integrations/hindsight Last updated: 2026-11-07 Status: in use in our own Koshra workspace. Each bot has a private Hindsight memory bank that keeps what it learns and recalls it in later chats. ## How bots reach it - Per-bot MCP server: Each bot gets its own MCP server for this app, with its own key, so access is scoped to that bot. ## Rules - Every tool call is checked against your Allow, Ask or Block rules first. Official site: https://github.com/vectorize-io/hindsight --- # Mem0 integration > How Koshra AI employees use Mem0: A self-hosted Mem0 memory store that bots can read and add to. Canonical: https://koshra.si/integrations/mem0 Last updated: 2026-11-07 Status: in use in our own Koshra workspace. A self-hosted Mem0 memory store that bots can read and add to. ## How bots reach it - Per-bot MCP server: Each bot gets its own MCP server for this app, with its own key, so access is scoped to that bot. ## Rules - Every tool call is checked against your Allow, Ask or Block rules first. Official site: https://mem0.ai --- # Code graph integration > How Koshra AI employees use Code graph: A graph of your code that platform_lead can query to find where things live. Canonical: https://koshra.si/integrations/graphify Last updated: 2026-11-07 Status: in use in our own Koshra workspace. A graph of your code that platform_lead can query to find where things live. ## How bots reach it - Per-bot MCP server: Each bot gets its own MCP server for this app, with its own key, so access is scoped to that bot. ## Rules - Only platform_lead gets it. - Every tool call is checked against your Allow, Ask or Block rules first. --- # nao analytics integration > How Koshra AI employees use nao analytics: The nao analytics agent, connected over MCP with OAuth, so bots can ask questions of your data warehouse. Canonical: https://koshra.si/integrations/nao Last updated: 2026-11-07 Status: in use in our own Koshra workspace. The nao analytics agent, connected over MCP with OAuth, so bots can ask questions of your data warehouse. ## How bots reach it - Per-bot MCP server: Each bot gets its own MCP server for this app, with its own key, so access is scoped to that bot. ## Rules - Every tool call is checked against your Allow, Ask or Block rules first. Official site: https://getnao.io --- # Voice integration > How Koshra AI employees use Voice: Self-hosted speech, so bots can speak replies and take voice input. Canonical: https://koshra.si/integrations/voice Last updated: 2026-11-07 Status: in use in our own Koshra workspace. Self-hosted speech, so bots can speak replies and take voice input. ## How bots reach it - Built in: Part of the Koshra server itself. ## Rules - Every tool call is checked against your Allow, Ask or Block rules first. Official site: https://github.com/speaches-ai/speaches --- # Cloudflare R2 integration > How Koshra AI employees use Cloudflare R2: Files the bots make, such as reports and exports, are kept in Cloudflare R2 object storage. Canonical: https://koshra.si/integrations/cloudflare_r2 Last updated: 2026-11-07 Status: in use in our own Koshra workspace. Files the bots make, such as reports and exports, are kept in Cloudflare R2 object storage. ## How bots reach it - Built in: Part of the Koshra server itself. ## Rules - Every tool call is checked against your Allow, Ask or Block rules first. Official site: https://www.cloudflare.com/developer-platform/products/r2/ --- # Nango integration > How Koshra AI employees use Nango: A connection layer for many apps. Koshra keeps an allowlist of apps per role and holds every write for approval. Canonical: https://koshra.si/integrations/nango Last updated: 2026-11-07 Status: in use in our own Koshra workspace. A connection layer for many apps. Koshra keeps an allowlist of apps per role and holds every write for approval. ## How bots reach it - Nango connection: Reached through a Nango connection. Each role has an allowlist of apps; reads are open and writes stop on an approval card. ## Rules - Writes stop on an approval card. - Every tool call is checked against your Allow, Ask or Block rules first. Official site: https://www.nango.dev --- # Salesforce integration > How Koshra AI employees use Salesforce: Revenue desks read accounts, contacts and opportunities to research a deal and propose updates. Canonical: https://koshra.si/integrations/salesforce Last updated: 2026-11-07 Status: in the Koshra app catalog; connect it from the app. Not yet used in our own workspace. Revenue desks read accounts, contacts and opportunities to research a deal and propose updates. ## How bots reach it - Composio connection: Reached through a Composio connection, with a per-bot allowlist so each bot only sees the apps its role needs. ## Roles that would use it - [pipeline_desk](https://koshra.si/roles/pipeline_desk) - [revops_desk](https://koshra.si/roles/revops_desk) - [research_desk](https://koshra.si/roles/research_desk) ## Rules - No bot can use it until you add it to that bot's allowlist; bots start with no apps. - Set its write tools to Ask, so each change waits on an approval card. - Every tool call is checked against your Allow, Ask or Block rules first. Official site: https://www.salesforce.com --- # Pipedrive integration > How Koshra AI employees use Pipedrive: Revenue desks read deals and people, and draft follow-ups for deals that have gone quiet. Canonical: https://koshra.si/integrations/pipedrive Last updated: 2026-11-07 Status: in the Koshra app catalog; connect it from the app. Not yet used in our own workspace. Revenue desks read deals and people, and draft follow-ups for deals that have gone quiet. ## How bots reach it - Composio connection: Reached through a Composio connection, with a per-bot allowlist so each bot only sees the apps its role needs. ## Roles that would use it - [pipeline_desk](https://koshra.si/roles/pipeline_desk) - [revops_desk](https://koshra.si/roles/revops_desk) ## Rules - No bot can use it until you add it to that bot's allowlist; bots start with no apps. - Set its write tools to Ask, so each change waits on an approval card. - Every tool call is checked against your Allow, Ask or Block rules first. Official site: https://www.pipedrive.com --- # Attio integration > How Koshra AI employees use Attio: Revenue desks read records and lists, and propose enrichment and clean-ups. Canonical: https://koshra.si/integrations/attio Last updated: 2026-11-07 Status: in the Koshra app catalog; connect it from the app. Not yet used in our own workspace. Revenue desks read records and lists, and propose enrichment and clean-ups. ## How bots reach it - Composio connection: Reached through a Composio connection, with a per-bot allowlist so each bot only sees the apps its role needs. ## Roles that would use it - [pipeline_desk](https://koshra.si/roles/pipeline_desk) - [enrichment_desk](https://koshra.si/roles/enrichment_desk) - [revops_desk](https://koshra.si/roles/revops_desk) ## Rules - No bot can use it until you add it to that bot's allowlist; bots start with no apps. - Set its write tools to Ask, so each change waits on an approval card. - Every tool call is checked against your Allow, Ask or Block rules first. Official site: https://attio.com --- # Close integration > How Koshra AI employees use Close: Revenue desks read leads and activity, and draft the next touch for each lead. Canonical: https://koshra.si/integrations/close Last updated: 2026-11-07 Status: in the Koshra app catalog; connect it from the app. Not yet used in our own workspace. Revenue desks read leads and activity, and draft the next touch for each lead. ## How bots reach it - Composio connection: Reached through a Composio connection, with a per-bot allowlist so each bot only sees the apps its role needs. ## Roles that would use it - [pipeline_desk](https://koshra.si/roles/pipeline_desk) - [outbound_desk](https://koshra.si/roles/outbound_desk) ## Rules - No bot can use it until you add it to that bot's allowlist; bots start with no apps. - Set its write tools to Ask, so each change waits on an approval card. - Set its send tools to Ask, so each message waits on an approval card. - Every tool call is checked against your Allow, Ask or Block rules first. Official site: https://www.close.com --- # Zoho CRM integration > How Koshra AI employees use Zoho CRM: Revenue desks read leads, accounts and deals, and propose updates. Canonical: https://koshra.si/integrations/zoho Last updated: 2026-11-07 Status: in the Koshra app catalog; connect it from the app. Not yet used in our own workspace. Revenue desks read leads, accounts and deals, and propose updates. ## How bots reach it - Composio connection: Reached through a Composio connection, with a per-bot allowlist so each bot only sees the apps its role needs. ## Roles that would use it - [pipeline_desk](https://koshra.si/roles/pipeline_desk) - [revops_desk](https://koshra.si/roles/revops_desk) ## Rules - No bot can use it until you add it to that bot's allowlist; bots start with no apps. - Set its write tools to Ask, so each change waits on an approval card. - Every tool call is checked against your Allow, Ask or Block rules first. Official site: https://www.zoho.com/crm --- # Microsoft Teams integration > How Koshra AI employees use Microsoft Teams: Bots read channels and chats they are given and draft replies, for teams that work in Teams rather than Slack. Canonical: https://koshra.si/integrations/microsoft_teams Last updated: 2026-11-07 Status: in the Koshra app catalog; connect it from the app. Not yet used in our own workspace. Bots read channels and chats they are given and draft replies, for teams that work in Teams rather than Slack. ## How bots reach it - Composio connection: Reached through a Composio connection, with a per-bot allowlist so each bot only sees the apps its role needs. ## Roles that would use it - [chief_of_staff](https://koshra.si/roles/chief_of_staff) - [support_answers](https://koshra.si/roles/support_answers) - [projects_desk](https://koshra.si/roles/projects_desk) ## Rules - No bot can use it until you add it to that bot's allowlist; bots start with no apps. - Set its send tools to Ask, so each message waits on an approval card. - Every tool call is checked against your Allow, Ask or Block rules first. Official site: https://www.microsoft.com/microsoft-teams --- # Outlook integration > How Koshra AI employees use Outlook: Bots read mail and calendar in Outlook and draft replies and meeting prep. Canonical: https://koshra.si/integrations/outlook Last updated: 2026-11-07 Status: in the Koshra app catalog; connect it from the app. Not yet used in our own workspace. Bots read mail and calendar in Outlook and draft replies and meeting prep. ## How bots reach it - Composio connection: Reached through a Composio connection, with a per-bot allowlist so each bot only sees the apps its role needs. ## Roles that would use it - [chief_of_staff](https://koshra.si/roles/chief_of_staff) - [outbound_desk](https://koshra.si/roles/outbound_desk) - [customer_desk](https://koshra.si/roles/customer_desk) ## Rules - No bot can use it until you add it to that bot's allowlist; bots start with no apps. - Set its send tools to Ask, so each message waits on an approval card. - Every tool call is checked against your Allow, Ask or Block rules first. Official site: https://outlook.com --- # Zendesk integration > How Koshra AI employees use Zendesk: Support desks read tickets, sort them by urgency and draft answers from your help content. Canonical: https://koshra.si/integrations/zendesk Last updated: 2026-11-07 Status: in the Koshra app catalog; connect it from the app. Not yet used in our own workspace. Support desks read tickets, sort them by urgency and draft answers from your help content. ## How bots reach it - Composio connection: Reached through a Composio connection, with a per-bot allowlist so each bot only sees the apps its role needs. ## Roles that would use it - [support_triage](https://koshra.si/roles/support_triage) - [support_answers](https://koshra.si/roles/support_answers) - [support_escalations](https://koshra.si/roles/support_escalations) - [support_lead](https://koshra.si/roles/support_lead) ## Rules - No bot can use it until you add it to that bot's allowlist; bots start with no apps. - Set its send tools to Ask, so each message waits on an approval card. - Set its write tools to Ask, so each change waits on an approval card. - Every tool call is checked against your Allow, Ask or Block rules first. Official site: https://www.zendesk.com --- # Intercom integration > How Koshra AI employees use Intercom: Support desks read conversations and draft replies for a person to send. Canonical: https://koshra.si/integrations/intercom Last updated: 2026-11-07 Status: in the Koshra app catalog; connect it from the app. Not yet used in our own workspace. Support desks read conversations and draft replies for a person to send. ## How bots reach it - Composio connection: Reached through a Composio connection, with a per-bot allowlist so each bot only sees the apps its role needs. ## Roles that would use it - [support_triage](https://koshra.si/roles/support_triage) - [support_answers](https://koshra.si/roles/support_answers) - [support_lead](https://koshra.si/roles/support_lead) ## Rules - No bot can use it until you add it to that bot's allowlist; bots start with no apps. - Set its send tools to Ask, so each message waits on an approval card. - Every tool call is checked against your Allow, Ask or Block rules first. Official site: https://www.intercom.com --- # Freshdesk integration > How Koshra AI employees use Freshdesk: Support desks read tickets, tag and route them, and draft answers. Canonical: https://koshra.si/integrations/freshdesk Last updated: 2026-11-07 Status: in the Koshra app catalog; connect it from the app. Not yet used in our own workspace. Support desks read tickets, tag and route them, and draft answers. ## How bots reach it - Composio connection: Reached through a Composio connection, with a per-bot allowlist so each bot only sees the apps its role needs. ## Roles that would use it - [support_triage](https://koshra.si/roles/support_triage) - [support_answers](https://koshra.si/roles/support_answers) - [support_escalations](https://koshra.si/roles/support_escalations) ## Rules - No bot can use it until you add it to that bot's allowlist; bots start with no apps. - Set its send tools to Ask, so each message waits on an approval card. - Set its write tools to Ask, so each change waits on an approval card. - Every tool call is checked against your Allow, Ask or Block rules first. Official site: https://www.freshworks.com/freshdesk --- # Jira integration > How Koshra AI employees use Jira: Bots read issues and boards, write up bugs and status, and propose new issues. Canonical: https://koshra.si/integrations/jira Last updated: 2026-11-07 Status: in the Koshra app catalog; connect it from the app. Not yet used in our own workspace. Bots read issues and boards, write up bugs and status, and propose new issues. ## How bots reach it - Composio connection: Reached through a Composio connection, with a per-bot allowlist so each bot only sees the apps its role needs. ## Roles that would use it - [projects_desk](https://koshra.si/roles/projects_desk) - [product_lead](https://koshra.si/roles/product_lead) - [platform_lead](https://koshra.si/roles/platform_lead) ## Rules - No bot can use it until you add it to that bot's allowlist; bots start with no apps. - Set its write tools to Ask, so each change waits on an approval card. - Every tool call is checked against your Allow, Ask or Block rules first. Official site: https://www.atlassian.com/software/jira --- # Asana integration > How Koshra AI employees use Asana: Bots read projects and tasks, write status updates and propose next tasks. Canonical: https://koshra.si/integrations/asana Last updated: 2026-11-07 Status: in the Koshra app catalog; connect it from the app. Not yet used in our own workspace. Bots read projects and tasks, write status updates and propose next tasks. ## How bots reach it - Composio connection: Reached through a Composio connection, with a per-bot allowlist so each bot only sees the apps its role needs. ## Roles that would use it - [projects_desk](https://koshra.si/roles/projects_desk) - [chief_operating_officer](https://koshra.si/roles/chief_operating_officer) ## Rules - No bot can use it until you add it to that bot's allowlist; bots start with no apps. - Set its write tools to Ask, so each change waits on an approval card. - Every tool call is checked against your Allow, Ask or Block rules first. Official site: https://asana.com --- # Trello integration > How Koshra AI employees use Trello: Bots read boards and cards and propose moves and new cards. Canonical: https://koshra.si/integrations/trello Last updated: 2026-11-07 Status: in the Koshra app catalog; connect it from the app. Not yet used in our own workspace. Bots read boards and cards and propose moves and new cards. ## How bots reach it - Composio connection: Reached through a Composio connection, with a per-bot allowlist so each bot only sees the apps its role needs. ## Roles that would use it - [projects_desk](https://koshra.si/roles/projects_desk) ## Rules - No bot can use it until you add it to that bot's allowlist; bots start with no apps. - Set its write tools to Ask, so each change waits on an approval card. - Every tool call is checked against your Allow, Ask or Block rules first. Official site: https://trello.com --- # Airtable integration > How Koshra AI employees use Airtable: Bots read bases, such as a content calendar or an account list, and propose updates. Canonical: https://koshra.si/integrations/airtable Last updated: 2026-11-07 Status: in the Koshra app catalog; connect it from the app. Not yet used in our own workspace. Bots read bases, such as a content calendar or an account list, and propose updates. ## How bots reach it - Composio connection: Reached through a Composio connection, with a per-bot allowlist so each bot only sees the apps its role needs. ## Roles that would use it - [projects_desk](https://koshra.si/roles/projects_desk) - [revops_desk](https://koshra.si/roles/revops_desk) - [chief_marketing_officer](https://koshra.si/roles/chief_marketing_officer) ## Rules - No bot can use it until you add it to that bot's allowlist; bots start with no apps. - Set its write tools to Ask, so each change waits on an approval card. - Every tool call is checked against your Allow, Ask or Block rules first. Official site: https://www.airtable.com --- # Confluence integration > How Koshra AI employees use Confluence: Bots read pages so answers and briefs use what your team already wrote down. Canonical: https://koshra.si/integrations/confluence Last updated: 2026-11-07 Status: in the Koshra app catalog; connect it from the app. Not yet used in our own workspace. Bots read pages so answers and briefs use what your team already wrote down. ## How bots reach it - Composio connection: Reached through a Composio connection, with a per-bot allowlist so each bot only sees the apps its role needs. ## Roles that would use it - [support_answers](https://koshra.si/roles/support_answers) - [research_lead](https://koshra.si/roles/research_lead) - [projects_desk](https://koshra.si/roles/projects_desk) ## Rules - No bot can use it until you add it to that bot's allowlist; bots start with no apps. - Start read-only: give bots its read tools first and add writes later. - Set its write tools to Ask, so each change waits on an approval card. - Every tool call is checked against your Allow, Ask or Block rules first. Official site: https://www.atlassian.com/software/confluence --- # Dropbox integration > How Koshra AI employees use Dropbox: Bots find and read the files a task needs, such as a past proposal. Canonical: https://koshra.si/integrations/dropbox Last updated: 2026-11-07 Status: in the Koshra app catalog; connect it from the app. Not yet used in our own workspace. Bots find and read the files a task needs, such as a past proposal. ## How bots reach it - Composio connection: Reached through a Composio connection, with a per-bot allowlist so each bot only sees the apps its role needs. ## Roles that would use it - [client_proposal_writer](https://koshra.si/roles/client_proposal_writer) - [research_desk](https://koshra.si/roles/research_desk) ## Rules - No bot can use it until you add it to that bot's allowlist; bots start with no apps. - Start read-only: give bots its read tools first and add writes later. - Every tool call is checked against your Allow, Ask or Block rules first. Official site: https://www.dropbox.com --- # OneDrive integration > How Koshra AI employees use OneDrive: Bots find and read files in OneDrive for a task. Canonical: https://koshra.si/integrations/one_drive Last updated: 2026-11-07 Status: in the Koshra app catalog; connect it from the app. Not yet used in our own workspace. Bots find and read files in OneDrive for a task. ## How bots reach it - Composio connection: Reached through a Composio connection, with a per-bot allowlist so each bot only sees the apps its role needs. ## Roles that would use it - [client_proposal_writer](https://koshra.si/roles/client_proposal_writer) - [research_desk](https://koshra.si/roles/research_desk) ## Rules - No bot can use it until you add it to that bot's allowlist; bots start with no apps. - Start read-only: give bots its read tools first and add writes later. - Every tool call is checked against your Allow, Ask or Block rules first. Official site: https://www.microsoft.com/microsoft-365/onedrive --- # SharePoint integration > How Koshra AI employees use SharePoint: Bots read SharePoint sites and documents so answers use your own policies and notes. Canonical: https://koshra.si/integrations/share_point Last updated: 2026-11-07 Status: in the Koshra app catalog; connect it from the app. Not yet used in our own workspace. Bots read SharePoint sites and documents so answers use your own policies and notes. ## How bots reach it - Composio connection: Reached through a Composio connection, with a per-bot allowlist so each bot only sees the apps its role needs. ## Roles that would use it - [support_answers](https://koshra.si/roles/support_answers) - [research_lead](https://koshra.si/roles/research_lead) ## Rules - No bot can use it until you add it to that bot's allowlist; bots start with no apps. - Start read-only: give bots its read tools first and add writes later. - Every tool call is checked against your Allow, Ask or Block rules first. Official site: https://www.microsoft.com/microsoft-365/sharepoint --- # Zoom integration > How Koshra AI employees use Zoom: Bots see meetings and recordings so a call can become notes, decisions and follow-ups. Canonical: https://koshra.si/integrations/zoom Last updated: 2026-11-07 Status: in the Koshra app catalog; connect it from the app. Not yet used in our own workspace. Bots see meetings and recordings so a call can become notes, decisions and follow-ups. ## How bots reach it - Composio connection: Reached through a Composio connection, with a per-bot allowlist so each bot only sees the apps its role needs. ## Roles that would use it - [chief_of_staff](https://koshra.si/roles/chief_of_staff) - [decision_desk](https://koshra.si/roles/decision_desk) ## Rules - No bot can use it until you add it to that bot's allowlist; bots start with no apps. - Start read-only: give bots its read tools first and add writes later. - Every tool call is checked against your Allow, Ask or Block rules first. Official site: https://zoom.us --- # Calendly integration > How Koshra AI employees use Calendly: Bots read event types and bookings to prepare for calls and offer booking links. Canonical: https://koshra.si/integrations/calendly Last updated: 2026-11-07 Status: in the Koshra app catalog; connect it from the app. Not yet used in our own workspace. Bots read event types and bookings to prepare for calls and offer booking links. ## How bots reach it - Composio connection: Reached through a Composio connection, with a per-bot allowlist so each bot only sees the apps its role needs. ## Roles that would use it - [recruiting_scheduler](https://koshra.si/roles/recruiting_scheduler) - [chief_of_staff](https://koshra.si/roles/chief_of_staff) ## Rules - No bot can use it until you add it to that bot's allowlist; bots start with no apps. - Set its send tools to Ask, so each message waits on an approval card. - Every tool call is checked against your Allow, Ask or Block rules first. Official site: https://calendly.com --- # Gong integration > How Koshra AI employees use Gong: Revenue desks read call notes and deal signals to prepare the next step. Canonical: https://koshra.si/integrations/gong Last updated: 2026-11-07 Status: in the Koshra app catalog; connect it from the app. Not yet used in our own workspace. Revenue desks read call notes and deal signals to prepare the next step. ## How bots reach it - Composio connection: Reached through a Composio connection, with a per-bot allowlist so each bot only sees the apps its role needs. ## Roles that would use it - [customer_desk](https://koshra.si/roles/customer_desk) - [pipeline_desk](https://koshra.si/roles/pipeline_desk) ## Rules - No bot can use it until you add it to that bot's allowlist; bots start with no apps. - Start read-only: give bots its read tools first and add writes later. - Every tool call is checked against your Allow, Ask or Block rules first. Official site: https://www.gong.io --- # Fireflies integration > How Koshra AI employees use Fireflies: Bots read meeting transcripts to write up decisions and follow-ups. Canonical: https://koshra.si/integrations/fireflies Last updated: 2026-11-07 Status: in the Koshra app catalog; connect it from the app. Not yet used in our own workspace. Bots read meeting transcripts to write up decisions and follow-ups. ## How bots reach it - Composio connection: Reached through a Composio connection, with a per-bot allowlist so each bot only sees the apps its role needs. ## Roles that would use it - [decision_desk](https://koshra.si/roles/decision_desk) - [chief_of_staff](https://koshra.si/roles/chief_of_staff) ## Rules - No bot can use it until you add it to that bot's allowlist; bots start with no apps. - Start read-only: give bots its read tools first and add writes later. - Every tool call is checked against your Allow, Ask or Block rules first. Official site: https://fireflies.ai --- # Greenhouse integration > How Koshra AI employees use Greenhouse: Recruiting desks read roles and candidates, prepare screens and draft notes. Canonical: https://koshra.si/integrations/greenhouse Last updated: 2026-11-07 Status: in the Koshra app catalog; connect it from the app. Not yet used in our own workspace. Recruiting desks read roles and candidates, prepare screens and draft notes. ## How bots reach it - Composio connection: Reached through a Composio connection, with a per-bot allowlist so each bot only sees the apps its role needs. ## Roles that would use it - [talent_desk](https://koshra.si/roles/talent_desk) - [recruiting_screener](https://koshra.si/roles/recruiting_screener) - [recruiting_scheduler](https://koshra.si/roles/recruiting_scheduler) ## Rules - No bot can use it until you add it to that bot's allowlist; bots start with no apps. - Set its write tools to Ask, so each change waits on an approval card. - Set its send tools to Ask, so each message waits on an approval card. - Hiring decisions stay with people. - Every tool call is checked against your Allow, Ask or Block rules first. Official site: https://www.greenhouse.com --- # Lever integration > How Koshra AI employees use Lever: Recruiting desks read postings and candidates, and draft outreach and screen notes. Canonical: https://koshra.si/integrations/lever Last updated: 2026-11-07 Status: in the Koshra app catalog; connect it from the app. Not yet used in our own workspace. Recruiting desks read postings and candidates, and draft outreach and screen notes. ## How bots reach it - Composio connection: Reached through a Composio connection, with a per-bot allowlist so each bot only sees the apps its role needs. ## Roles that would use it - [talent_desk](https://koshra.si/roles/talent_desk) - [recruiting_sourcer](https://koshra.si/roles/recruiting_sourcer) - [recruiting_screener](https://koshra.si/roles/recruiting_screener) ## Rules - No bot can use it until you add it to that bot's allowlist; bots start with no apps. - Set its write tools to Ask, so each change waits on an approval card. - Set its send tools to Ask, so each message waits on an approval card. - Hiring decisions stay with people. - Every tool call is checked against your Allow, Ask or Block rules first. Official site: https://www.lever.co --- # Stripe integration > How Koshra AI employees use Stripe: Finance desks read payments, invoices and subscriptions for reports and follow-ups. Canonical: https://koshra.si/integrations/stripe Last updated: 2026-11-07 Status: in the Koshra app catalog; connect it from the app. Not yet used in our own workspace. Finance desks read payments, invoices and subscriptions for reports and follow-ups. ## How bots reach it - Composio connection: Reached through a Composio connection, with a per-bot allowlist so each bot only sees the apps its role needs. ## Roles that would use it - [chief_financial_officer](https://koshra.si/roles/chief_financial_officer) - [funder_desk](https://koshra.si/roles/funder_desk) ## Rules - No bot can use it until you add it to that bot's allowlist; bots start with no apps. - Start read-only: give bots its read tools first and add writes later. - Paying, refunding or moving money is outside every role's limits. - Every tool call is checked against your Allow, Ask or Block rules first. Official site: https://stripe.com --- # QuickBooks integration > How Koshra AI employees use QuickBooks: Finance desks read invoices, bills and reports to prepare a monthly summary. Canonical: https://koshra.si/integrations/quickbooks Last updated: 2026-11-07 Status: in the Koshra app catalog; connect it from the app. Not yet used in our own workspace. Finance desks read invoices, bills and reports to prepare a monthly summary. ## How bots reach it - Composio connection: Reached through a Composio connection, with a per-bot allowlist so each bot only sees the apps its role needs. ## Roles that would use it - [chief_financial_officer](https://koshra.si/roles/chief_financial_officer) ## Rules - No bot can use it until you add it to that bot's allowlist; bots start with no apps. - Start read-only: give bots its read tools first and add writes later. - Paying, refunding or moving money is outside every role's limits. - Every tool call is checked against your Allow, Ask or Block rules first. Official site: https://quickbooks.intuit.com --- # Xero integration > How Koshra AI employees use Xero: Finance desks read invoices, bills and reports to prepare a monthly summary. Canonical: https://koshra.si/integrations/xero Last updated: 2026-11-07 Status: in the Koshra app catalog; connect it from the app. Not yet used in our own workspace. Finance desks read invoices, bills and reports to prepare a monthly summary. ## How bots reach it - Composio connection: Reached through a Composio connection, with a per-bot allowlist so each bot only sees the apps its role needs. ## Roles that would use it - [chief_financial_officer](https://koshra.si/roles/chief_financial_officer) ## Rules - No bot can use it until you add it to that bot's allowlist; bots start with no apps. - Start read-only: give bots its read tools first and add writes later. - Paying, refunding or moving money is outside every role's limits. - Every tool call is checked against your Allow, Ask or Block rules first. Official site: https://www.xero.com --- # Mailchimp integration > How Koshra AI employees use Mailchimp: Marketing desks read audiences and campaigns and draft the next email for you to send. Canonical: https://koshra.si/integrations/mailchimp Last updated: 2026-11-07 Status: in the Koshra app catalog; connect it from the app. Not yet used in our own workspace. Marketing desks read audiences and campaigns and draft the next email for you to send. ## How bots reach it - Composio connection: Reached through a Composio connection, with a per-bot allowlist so each bot only sees the apps its role needs. ## Roles that would use it - [chief_marketing_officer](https://koshra.si/roles/chief_marketing_officer) - [repurpose_desk](https://koshra.si/roles/repurpose_desk) - [launch_day](https://koshra.si/roles/launch_day) ## Rules - No bot can use it until you add it to that bot's allowlist; bots start with no apps. - Publishing is outside every role's limits: bots draft, you publish. - Every tool call is checked against your Allow, Ask or Block rules first. Official site: https://mailchimp.com --- # Webflow integration > How Koshra AI employees use Webflow: Marketing desks read your site's collections and draft new pages and posts for review. Canonical: https://koshra.si/integrations/webflow Last updated: 2026-11-07 Status: in the Koshra app catalog; connect it from the app. Not yet used in our own workspace. Marketing desks read your site's collections and draft new pages and posts for review. ## How bots reach it - Composio connection: Reached through a Composio connection, with a per-bot allowlist so each bot only sees the apps its role needs. ## Roles that would use it - [chief_marketing_officer](https://koshra.si/roles/chief_marketing_officer) - [repurpose_desk](https://koshra.si/roles/repurpose_desk) ## Rules - No bot can use it until you add it to that bot's allowlist; bots start with no apps. - Publishing is outside every role's limits: bots draft, you publish. - Every tool call is checked against your Allow, Ask or Block rules first. Official site: https://webflow.com --- # Composio integration > How Koshra AI employees use Composio: A connection layer for many apps. Koshra gives each bot its own allowlist, so it only sees what its role needs. Canonical: https://koshra.si/integrations/composio Last updated: 2026-11-07 Status: in use in our own Koshra workspace. A connection layer for many apps. Koshra gives each bot its own allowlist, so it only sees what its role needs. ## How bots reach it - Composio connection: Reached through a Composio connection, with a per-bot allowlist so each bot only sees the apps its role needs. ## Rules - Every tool call is checked against your Allow, Ask or Block rules first. Official site: https://composio.dev --- # Any MCP server integration > How Koshra AI employees use Any MCP server: Add any MCP server over streamable HTTP and its tools appear for the bots you choose, under the same Allow, Ask and Block rules as everything else. Canonical: https://koshra.si/integrations/custom_mcp Last updated: 2026-11-07 Status: in use in our own Koshra workspace. Add any MCP server over streamable HTTP and its tools appear for the bots you choose, under the same Allow, Ask and Block rules as everything else. ## How bots reach it - Per-bot MCP server: Each bot gets its own MCP server for this app, with its own key, so access is scoped to that bot. ## Rules - Adding an MCP server is a change you make. Bots cannot add one themselves. - Every tool call is checked against your Allow, Ask or Block rules first. Official site: https://modelcontextprotocol.io --- # Koshra workflows > Four workflows the Koshra team can run for you first: a pre-discovery brief, meeting intelligence, a reverse ICP audit and pipeline hygiene. Canonical: https://koshra.si/workflows Last updated: 2026-11-07 Hand over one job first. Pricing for each: talk to us. ## [Pre-discovery brief](https://koshra.si/workflows/pre_discovery_brief) Owner: research_lead A sourced one-page brief on the account and the people before a booked discovery call. Every claim is sourced or marked unknown, and a person approves it first. ## [Meeting intelligence](https://koshra.si/workflows/meeting_intelligence) Owner: chief_of_staff Each client call becomes one meeting record: summary, decisions, next steps with owners, and follow-ups held for approval. ## [Reverse ICP audit](https://koshra.si/workflows/reverse_icp_audit) Owner: product_lead Work backwards from who bought, stalled or churned to test your stated ICP before more spend goes into it. ## [Pipeline hygiene](https://koshra.si/workflows/pipeline_hygiene) Owner: revops_desk Stage rules and required fields, then a scheduled scan that proposes fixes in small batches. Configured rules block merges and deletes. --- # Pre-discovery brief workflow > How Koshra's research_lead prepares a sourced one-page brief on an account and its people before a discovery call, with every claim sourced or marked unknown. Canonical: https://koshra.si/workflows/pre_discovery_brief Last updated: 2026-11-07 A sourced one-page brief on the account and the people before a booked discovery call. Every claim is sourced or marked unknown, and a person approves it first. Owner: [research_lead](https://koshra.si/roles/research_lead) ## How it runs 1. You name the account and the call. 2. research_desk researches that one account and returns facts with sources. 3. research_lead turns them into a one-page brief: the account, the people and what to ask. 4. research_evidence_reviewer checks every material claim against its source. Anything without one is marked unknown. 5. You approve the brief before anyone uses it. ## What waits for you - The brief itself, before anyone uses it ## Roles involved - [research_lead](https://koshra.si/roles/research_lead) - [research_desk](https://koshra.si/roles/research_desk) - [research_evidence_reviewer](https://koshra.si/roles/research_evidence_reviewer) ## Apps it can use - [Firecrawl](https://koshra.si/integrations/firecrawl) - [Scrapling](https://koshra.si/integrations/scrapling) - [Google Calendar](https://koshra.si/integrations/google_calendar) - [HubSpot](https://koshra.si/integrations/hubspot) The steps show how the roles in our template divide the work. Your setup is agreed with you. Pricing: talk to us. --- # Meeting intelligence workflow > How Koshra turns each client call into one meeting record with a summary, decisions and next steps with owners, and holds follow-ups for your approval. Canonical: https://koshra.si/workflows/meeting_intelligence Last updated: 2026-11-07 Each client call becomes one meeting record: summary, decisions, next steps with owners, and follow-ups held for approval. Owner: [chief_of_staff](https://koshra.si/roles/chief_of_staff) ## How it runs 1. A client call happens on your calendar. 2. chief_of_staff writes one meeting record: the summary, the decisions and the next steps, each with an owner. 3. decision_desk records each decision, the reason and what must not happen. 4. Follow-up emails are drafted and held on an approval card. 5. You approve, edit or deny each follow-up. ## What waits for you - Every follow-up email or Slack message ## Roles involved - [chief_of_staff](https://koshra.si/roles/chief_of_staff) - [decision_desk](https://koshra.si/roles/decision_desk) - [projects_desk](https://koshra.si/roles/projects_desk) ## Apps it can use - [Google Calendar](https://koshra.si/integrations/google_calendar) - [Google Meet](https://koshra.si/integrations/google_meet) - [Gmail](https://koshra.si/integrations/gmail) - [Google Docs](https://koshra.si/integrations/google_docs) The steps show how the roles in our template divide the work. Your setup is agreed with you. Pricing: talk to us. --- # Reverse ICP audit workflow > How Koshra works backwards from who bought, stalled or churned to test your stated ideal customer profile before more spend goes into it. Canonical: https://koshra.si/workflows/reverse_icp_audit Last updated: 2026-11-07 Work backwards from who bought, stalled or churned to test your stated ICP before more spend goes into it. Owner: [product_lead](https://koshra.si/roles/product_lead) ## How it runs 1. You share who bought, who stalled and who churned. 2. customer_desk names what each buyer paid for, the objection and the price they accepted. 3. product_lead compares that against your stated ICP and names where it holds and where it breaks. 4. chief_gtm uses the result to choose the next accounts and offer. 5. You decide whether the ICP changes. ## What waits for you - Any change to your CRM ## Roles involved - [product_lead](https://koshra.si/roles/product_lead) - [customer_desk](https://koshra.si/roles/customer_desk) - [chief_gtm](https://koshra.si/roles/chief_gtm) ## Apps it can use - [HubSpot](https://koshra.si/integrations/hubspot) - [Twenty CRM](https://koshra.si/integrations/twenty) - [Google Sheets](https://koshra.si/integrations/google_sheets) The steps show how the roles in our template divide the work. Your setup is agreed with you. Pricing: talk to us. --- # Pipeline hygiene workflow > How Koshra's revops_desk sets stage rules and required fields, then runs a scheduled scan that proposes CRM fixes in small batches without merging or deleting. Canonical: https://koshra.si/workflows/pipeline_hygiene Last updated: 2026-11-07 Stage rules and required fields, then a scheduled scan that proposes fixes in small batches. Configured rules block merges and deletes. Owner: [revops_desk](https://koshra.si/roles/revops_desk) ## How it runs 1. revops_desk writes the stage rules and required fields with you. 2. routines_desk writes the scan as a checklist with an owner and a stop condition. 3. You approve the schedule, and the scan runs on the server. 4. Each run flags the rows that break a rule and proposes fixes in small batches. 5. You approve writebacks. Configured rules block deletes and merges. ## What waits for you - The schedule - Every CRM writeback, and any bulk change ## Roles involved - [revops_desk](https://koshra.si/roles/revops_desk) - [pipeline_desk](https://koshra.si/roles/pipeline_desk) - [routines_desk](https://koshra.si/roles/routines_desk) ## Apps it can use - [HubSpot](https://koshra.si/integrations/hubspot) - [Twenty CRM](https://koshra.si/integrations/twenty) - [Google Sheets](https://koshra.si/integrations/google_sheets) The steps show how the roles in our template divide the work. Your setup is agreed with you. Pricing: talk to us. --- # Koshra glossary > Plain definitions of the terms used in Koshra: AI employee, dispatcher, plan card, approval card, Brain, routine and more. Canonical: https://koshra.si/glossary Last updated: 2026-11-07 ## AI employee A bot in Koshra with a role name, a written job, a limit, its own model and its own memory. ## Role The job an AI employee is named for, in lowercase snake_case, such as research_desk or support_triage. The role name is what you see on chats, tasks and approval cards. ## Lead An AI employee that owns an area of work, such as research_lead or support_lead, and has a team chat with its desks. ## Desk An AI employee that does one focused job inside a lead's area, such as outbound_desk or pipeline_desk. ## chief_of_staff The bot at the top of a Koshra team. It prepares the day's list and names the officer, desk and next step for each item. ## Dispatcher The part of Koshra that turns a request into tasks, picks the bot that owns each one and shows a plan card before work starts. ## Plan card The card the dispatcher shows before work starts, with its reasons, the bots it picked and a countdown you can stop. ## Owner bot The one bot that owns a task. You can tell it to continue, retry the task or reassign it. ## Tasks board The board where tasks move through their stages, each showing its owner bot and status. ## Team chat A chat shared by a lead and its desks, with the lead listed first. You can read along and step in. ## Handoff Moving a task to the bot that owns that kind of work. Handoffs are capped per task. ## Subagent A short-lived helper a bot runs for a side job, which reports back to the bot that started it. ## Loop guard A check that stops two bots passing work back and forth, and stops repeat visits to the same bot. ## Spend cap The most a single dispatch may spend on model calls before it stops. Dispatches also have token, handoff and run caps. ## Stuck run A run that has stopped moving for longer than the threshold you set. It shows in the stuck-run bar with a cancel button. ## Approval card The card a bot raises when a rule says Ask. It shows what the bot wants to do, and you answer Allow or Deny. ## Allow, Ask, Block The three rule settings for a tool. Allow runs it, Ask stops for your approval and Block refuses it. ## Permission mode A per-bot setting on top of the rules. It can make a bot stricter, never looser. ## Approvals inbox The one place every waiting approval card is collected. Only the space owner and admins see it. ## CRM guard rails Rules that block deleting or merging CRM records and hold bulk changes and large writes for approval. ## Brain Your team's shared store of facts, edited as plain text in the app, with every edit saved so you can undo it. ## Brain sync A routine that reads recent work and proposes Brain updates. Proposals wait for your review. ## Memory bank A bot's private memory. It keeps what the bot learns and recalls it in later chats. ## Routine Work a bot repeats on a schedule, run on the server. Creating or changing a schedule needs your approval. ## Branch A new thread started from any message in a chat, leaving the original thread untouched. ## Model picker The control in the chat composer that switches a bot's model. The next reply uses the new model. ## Backup chain The models behind a bot's main model. If a provider is down or out of credit, the next model in the chain answers. ## Cost per reply The model, cost in USD and time shown on every reply. ## Space A workspace in Koshra with its own bots, rules, tasks and Brain. The dispatcher and tasks board are switched on per space. ## Scoped API key A key a Koshra space admin makes so another agent can use the REST API or MCP server. It acts as that admin in one space, only within the scopes picked, and the secret is shown once. ## MCP The Model Context Protocol, an open standard for giving AI models tools. Koshra adds MCP servers per bot, under the same rules as everything else. ## App connection Access to an app such as Gmail or HubSpot through a connection layer, limited per bot to what its role needs. ## Team computer A shared container on the server where an allowed bot can run tools and work with files. ## Web Push Browser alerts on your phone or laptop when an approval card is waiting. ## Self-hosted Running Koshra on a server you control, as a small set of Docker containers, next to your own tools and data. ## AG-UI An open protocol for streaming agent runs to a user interface. Koshra's client console is built on it and is in testing. ## llms.txt A plain-text index of a website for AI assistants. Koshra's lists every page, and llms-full.txt holds the whole site as Markdown. ## Send limit How many messages a bot may send on its own. For drafting roles it is zero: they draft and you send. --- # AI employee: Koshra glossary > A bot in Koshra with a role name, a written job, a limit, its own model and its own memory. Canonical: https://koshra.si/glossary/ai_employee Last updated: 2026-11-07 A bot in Koshra with a role name, a written job, a limit, its own model and its own memory. Read more: https://koshra.si/docs/ai_employees --- # Role: Koshra glossary > The job an AI employee is named for, in lowercase snake_case, such as research_desk or support_triage. The role name is what you see on chats, tasks and approval cards. Canonical: https://koshra.si/glossary/role Last updated: 2026-11-07 The job an AI employee is named for, in lowercase snake_case, such as research_desk or support_triage. The role name is what you see on chats, tasks and approval cards. Read more: https://koshra.si/use_cases --- # Lead: Koshra glossary > An AI employee that owns an area of work, such as research_lead or support_lead, and has a team chat with its desks. Canonical: https://koshra.si/glossary/lead Last updated: 2026-11-07 An AI employee that owns an area of work, such as research_lead or support_lead, and has a team chat with its desks. Read more: https://koshra.si/docs/team_chats_and_handoffs --- # Desk: Koshra glossary > An AI employee that does one focused job inside a lead's area, such as outbound_desk or pipeline_desk. Canonical: https://koshra.si/glossary/desk Last updated: 2026-11-07 An AI employee that does one focused job inside a lead's area, such as outbound_desk or pipeline_desk. Read more: https://koshra.si/docs/ai_employees --- # chief_of_staff: Koshra glossary > The bot at the top of a Koshra team. It prepares the day's list and names the officer, desk and next step for each item. Canonical: https://koshra.si/glossary/chief_of_staff Last updated: 2026-11-07 The bot at the top of a Koshra team. It prepares the day's list and names the officer, desk and next step for each item. Read more: https://koshra.si/roles/chief_of_staff --- # Dispatcher: Koshra glossary > The part of Koshra that turns a request into tasks, picks the bot that owns each one and shows a plan card before work starts. Canonical: https://koshra.si/glossary/dispatcher Last updated: 2026-11-07 The part of Koshra that turns a request into tasks, picks the bot that owns each one and shows a plan card before work starts. Read more: https://koshra.si/docs/dispatcher_and_tasks --- # Plan card: Koshra glossary > The card the dispatcher shows before work starts, with its reasons, the bots it picked and a countdown you can stop. Canonical: https://koshra.si/glossary/plan_card Last updated: 2026-11-07 The card the dispatcher shows before work starts, with its reasons, the bots it picked and a countdown you can stop. Read more: https://koshra.si/docs/dispatcher_and_tasks --- # Owner bot: Koshra glossary > The one bot that owns a task. You can tell it to continue, retry the task or reassign it. Canonical: https://koshra.si/glossary/owner_bot Last updated: 2026-11-07 The one bot that owns a task. You can tell it to continue, retry the task or reassign it. Read more: https://koshra.si/docs/dispatcher_and_tasks --- # Tasks board: Koshra glossary > The board where tasks move through their stages, each showing its owner bot and status. Canonical: https://koshra.si/glossary/tasks_board Last updated: 2026-11-07 The board where tasks move through their stages, each showing its owner bot and status. Read more: https://koshra.si/docs/dispatcher_and_tasks --- # Team chat: Koshra glossary > A chat shared by a lead and its desks, with the lead listed first. You can read along and step in. Canonical: https://koshra.si/glossary/team_chat Last updated: 2026-11-07 A chat shared by a lead and its desks, with the lead listed first. You can read along and step in. Read more: https://koshra.si/docs/team_chats_and_handoffs --- # Handoff: Koshra glossary > Moving a task to the bot that owns that kind of work. Handoffs are capped per task. Canonical: https://koshra.si/glossary/handoff Last updated: 2026-11-07 Moving a task to the bot that owns that kind of work. Handoffs are capped per task. Read more: https://koshra.si/docs/team_chats_and_handoffs --- # Subagent: Koshra glossary > A short-lived helper a bot runs for a side job, which reports back to the bot that started it. Canonical: https://koshra.si/glossary/subagent Last updated: 2026-11-07 A short-lived helper a bot runs for a side job, which reports back to the bot that started it. Read more: https://koshra.si/docs/team_chats_and_handoffs --- # Loop guard: Koshra glossary > A check that stops two bots passing work back and forth, and stops repeat visits to the same bot. Canonical: https://koshra.si/glossary/loop_guard Last updated: 2026-11-07 A check that stops two bots passing work back and forth, and stops repeat visits to the same bot. Read more: https://koshra.si/docs/dispatcher_and_tasks --- # Spend cap: Koshra glossary > The most a single dispatch may spend on model calls before it stops. Dispatches also have token, handoff and run caps. Canonical: https://koshra.si/glossary/spend_cap Last updated: 2026-11-07 The most a single dispatch may spend on model calls before it stops. Dispatches also have token, handoff and run caps. Read more: https://koshra.si/docs/dispatcher_and_tasks --- # Stuck run: Koshra glossary > A run that has stopped moving for longer than the threshold you set. It shows in the stuck-run bar with a cancel button. Canonical: https://koshra.si/glossary/stuck_run Last updated: 2026-11-07 A run that has stopped moving for longer than the threshold you set. It shows in the stuck-run bar with a cancel button. Read more: https://koshra.si/docs/dispatcher_and_tasks --- # Approval card: Koshra glossary > The card a bot raises when a rule says Ask. It shows what the bot wants to do, and you answer Allow or Deny. Canonical: https://koshra.si/glossary/approval_card Last updated: 2026-11-07 The card a bot raises when a rule says Ask. It shows what the bot wants to do, and you answer Allow or Deny. Read more: https://koshra.si/docs/approvals --- # Allow, Ask, Block: Koshra glossary > The three rule settings for a tool. Allow runs it, Ask stops for your approval and Block refuses it. Canonical: https://koshra.si/glossary/allow_ask_block Last updated: 2026-11-07 The three rule settings for a tool. Allow runs it, Ask stops for your approval and Block refuses it. Read more: https://koshra.si/docs/approvals --- # Permission mode: Koshra glossary > A per-bot setting on top of the rules. It can make a bot stricter, never looser. Canonical: https://koshra.si/glossary/permission_mode Last updated: 2026-11-07 A per-bot setting on top of the rules. It can make a bot stricter, never looser. Read more: https://koshra.si/docs/approvals --- # Approvals inbox: Koshra glossary > The one place every waiting approval card is collected. Only the space owner and admins see it. Canonical: https://koshra.si/glossary/approvals_inbox Last updated: 2026-11-07 The one place every waiting approval card is collected. Only the space owner and admins see it. Read more: https://koshra.si/docs/phone_and_alerts --- # CRM guard rails: Koshra glossary > Rules that block deleting or merging CRM records and hold bulk changes and large writes for approval. Canonical: https://koshra.si/glossary/crm_guard_rails Last updated: 2026-11-07 Rules that block deleting or merging CRM records and hold bulk changes and large writes for approval. Read more: https://koshra.si/docs/approvals --- # Brain: Koshra glossary > Your team's shared store of facts, edited as plain text in the app, with every edit saved so you can undo it. Canonical: https://koshra.si/glossary/brain Last updated: 2026-11-07 Your team's shared store of facts, edited as plain text in the app, with every edit saved so you can undo it. Read more: https://koshra.si/docs/memory --- # Brain sync: Koshra glossary > A routine that reads recent work and proposes Brain updates. Proposals wait for your review. Canonical: https://koshra.si/glossary/brain_sync Last updated: 2026-11-07 A routine that reads recent work and proposes Brain updates. Proposals wait for your review. Read more: https://koshra.si/docs/memory --- # Memory bank: Koshra glossary > A bot's private memory. It keeps what the bot learns and recalls it in later chats. Canonical: https://koshra.si/glossary/memory_bank Last updated: 2026-11-07 A bot's private memory. It keeps what the bot learns and recalls it in later chats. Read more: https://koshra.si/docs/memory --- # Routine: Koshra glossary > Work a bot repeats on a schedule, run on the server. Creating or changing a schedule needs your approval. Canonical: https://koshra.si/glossary/routine Last updated: 2026-11-07 Work a bot repeats on a schedule, run on the server. Creating or changing a schedule needs your approval. Read more: https://koshra.si/docs/routines --- # Branch: Koshra glossary > A new thread started from any message in a chat, leaving the original thread untouched. Canonical: https://koshra.si/glossary/branch Last updated: 2026-11-07 A new thread started from any message in a chat, leaving the original thread untouched. Read more: https://koshra.si/docs/branching --- # Model picker: Koshra glossary > The control in the chat composer that switches a bot's model. The next reply uses the new model. Canonical: https://koshra.si/glossary/model_picker Last updated: 2026-11-07 The control in the chat composer that switches a bot's model. The next reply uses the new model. Read more: https://koshra.si/docs/models_and_cost --- # Backup chain: Koshra glossary > The models behind a bot's main model. If a provider is down or out of credit, the next model in the chain answers. Canonical: https://koshra.si/glossary/backup_chain Last updated: 2026-11-07 The models behind a bot's main model. If a provider is down or out of credit, the next model in the chain answers. Read more: https://koshra.si/docs/models_and_cost --- # Cost per reply: Koshra glossary > The model, cost in USD and time shown on every reply. Canonical: https://koshra.si/glossary/cost_per_reply Last updated: 2026-11-07 The model, cost in USD and time shown on every reply. Read more: https://koshra.si/docs/models_and_cost --- # Space: Koshra glossary > A workspace in Koshra with its own bots, rules, tasks and Brain. The dispatcher and tasks board are switched on per space. Canonical: https://koshra.si/glossary/space Last updated: 2026-11-07 A workspace in Koshra with its own bots, rules, tasks and Brain. The dispatcher and tasks board are switched on per space. Read more: https://koshra.si/docs --- # Scoped API key: Koshra glossary > A key a Koshra space admin makes so another agent can use the REST API or MCP server. It acts as that admin in one space, only within the scopes picked, and the secret is shown once. Canonical: https://koshra.si/glossary/api_key Last updated: 2026-11-07 A key a Koshra space admin makes so another agent can use the REST API or MCP server. It acts as that admin in one space, only within the scopes picked, and the secret is shown once. Read more: https://koshra.si/docs/api_and_mcp --- # MCP: Koshra glossary > The Model Context Protocol, an open standard for giving AI models tools. Koshra adds MCP servers per bot, under the same rules as everything else. Canonical: https://koshra.si/glossary/mcp Last updated: 2026-11-07 The Model Context Protocol, an open standard for giving AI models tools. Koshra adds MCP servers per bot, under the same rules as everything else. Read more: https://koshra.si/integrations/custom_mcp --- # App connection: Koshra glossary > Access to an app such as Gmail or HubSpot through a connection layer, limited per bot to what its role needs. Canonical: https://koshra.si/glossary/app_connection Last updated: 2026-11-07 Access to an app such as Gmail or HubSpot through a connection layer, limited per bot to what its role needs. Read more: https://koshra.si/integrations --- # Team computer: Koshra glossary > A shared container on the server where an allowed bot can run tools and work with files. Canonical: https://koshra.si/glossary/team_computer Last updated: 2026-11-07 A shared container on the server where an allowed bot can run tools and work with files. Read more: https://koshra.si/docs/integrations --- # Web Push: Koshra glossary > Browser alerts on your phone or laptop when an approval card is waiting. Canonical: https://koshra.si/glossary/web_push Last updated: 2026-11-07 Browser alerts on your phone or laptop when an approval card is waiting. Read more: https://koshra.si/docs/phone_and_alerts --- # Self-hosted: Koshra glossary > Running Koshra on a server you control, as a small set of Docker containers, next to your own tools and data. Canonical: https://koshra.si/glossary/self_hosted Last updated: 2026-11-07 Running Koshra on a server you control, as a small set of Docker containers, next to your own tools and data. Read more: https://koshra.si/docs/self_hosting --- # AG-UI: Koshra glossary > An open protocol for streaming agent runs to a user interface. Koshra's client console is built on it and is in testing. Canonical: https://koshra.si/glossary/ag_ui Last updated: 2026-11-07 An open protocol for streaming agent runs to a user interface. Koshra's client console is built on it and is in testing. Read more: https://koshra.si/docs/dispatcher_and_tasks --- # llms.txt: Koshra glossary > A plain-text index of a website for AI assistants. Koshra's lists every page, and llms-full.txt holds the whole site as Markdown. Canonical: https://koshra.si/glossary/llms_txt Last updated: 2026-11-07 A plain-text index of a website for AI assistants. Koshra's lists every page, and llms-full.txt holds the whole site as Markdown. Read more: https://koshra.si/docs/for_ai_agents --- # Send limit: Koshra glossary > How many messages a bot may send on its own. For drafting roles it is zero: they draft and you send. Canonical: https://koshra.si/glossary/send_limit Last updated: 2026-11-07 How many messages a bot may send on its own. For drafting roles it is zero: they draft and you send. Read more: https://koshra.si/use_cases --- # Compare Koshra > Factual comparisons of Koshra with Rerun, Lindy, Dust, n8n, Turnstone, openbot and Reason Machines, from their public pages, including where Koshra is behind. Canonical: https://koshra.si/compare Last updated: 2026-11-07 ## [Koshra vs Rerun](https://koshra.si/compare/rerun) A factual comparison of Koshra and Rerun (rerun.build), from Rerun's public pages on 2 Nov 2026: licence, self-hosting, data residency, approvals, models and price, including where Koshra is behind. ## [Koshra vs Lindy](https://koshra.si/compare/lindy) A factual comparison of Koshra and Lindy, from Lindy's public pricing and security pages on 2 Nov 2026: hosting, data, approvals, models and price, including where Koshra is behind. ## [Koshra vs Dust](https://koshra.si/compare/dust) A factual comparison of Koshra and Dust, from Dust's public pricing and security pages on 2 Nov 2026: hosting, data residency, approvals, models and price, including where Koshra is behind. ## [Koshra vs n8n](https://koshra.si/compare/n8n) A factual comparison of Koshra and n8n, from n8n's public pricing page and licence on 2 Nov 2026: self-hosting, licence for client work, approvals and price, including where Koshra is behind. ## [Koshra vs Turnstone](https://koshra.si/compare/turnstone) Deployment and feature differences between Koshra and Turnstone, checked 7 November 2026 against Turnstone's public facts and howto pages. Competitor features are advertised, not independently tested. No overall winner. ## [Koshra vs openbot](https://koshra.si/compare/openbot) Deployment and feature differences between Koshra and openbot (openbot.run), checked 7 November 2026. Competitor features are advertised, not independently tested. No overall winner. ## [Koshra vs Reason Machines](https://koshra.si/compare/reason_machines) A factual comparison of Koshra and Reason from Reason Machines, from its public pages on 2 Nov 2026: where each is ahead and where Koshra is behind. --- # Koshra vs Rerun > A factual comparison of Koshra and Rerun (rerun.build), from Rerun's public pages on 2 Nov 2026: licence, self-hosting, data residency, approvals, models and price, including where Koshra is behind. Canonical: https://koshra.si/compare/rerun Last updated: 2026-11-07 Rerun, from Reunit SA in Luxembourg, is a hosted service for AI coworkers, each with its own cloud computer, and since 29 October 2026 also an open source edition under AGPL-3.0. Koshra is a team of AI employees that runs on a server you control, built on an Apache 2.0 open source base. Both give a team of agents shared memory, schedules and approvals. Deployment and feature differences, checked 2 November 2026. Competitor features are vendor-advertised, not independently tested. No overall winner. | Area | Koshra | Rerun | | --- | --- | --- | | Where it runs | Server-hosted assisted preview. Core data stays on the selected server. Files and model providers may process data elsewhere. | Hosted, with one VM per workspace on Hetzner in Germany. The open source edition can be self-hosted, which Rerun describes as documented, not supported | | Licence | Built on an Apache-2.0-licensed foundation. Koshra distribution, support and resale are separate agreed terms. | Open source edition under AGPL-3.0, so a changed version you host for others must have its source published; its trademark policy asks anyone hosting it for others to rebrand | | Data residency | Wherever your server is, for example India or the EU. Model calls go to the provider you pick for each bot | EU: workspace VMs in Germany, with US model providers among its listed sub-processors; GDPR data processing agreement | | Team setup | Dispatcher with a plan card and countdown; one owner bot per task; create a bot from a description or from 48 role templates | A workspace assistant interviews you, plans a team and builds it; a board of coworkers | | Approvals | Configured tool rules and approval cards. Plays email needs explicit owner approval. Configured CRM rules block destructive operations and hold bulk changes. Not every outbound path is verified. | Approvals and questions with suggested answers; an autopilot answers coworkers within your rules, never for spending or deleting | | Models | Per-bot model selection, mid-chat switching and fallback are implemented. Usage estimates depend on provider reporting. Free-tier availability is not guaranteed. | House tiers plus frontier models; your ChatGPT, Claude or Grok plan, API keys or local models | | Apps and tools | MCP and app-connection adapters. A catalog listing is not a tested connection | 3,000+ apps and MCPs on its site; a cloud desktop, browser and terminal per coworker that you can watch and take over | | Uptime and speed | A public status page checked every minute; home page Lighthouse mobile performance 95 (our test, 2 Nov 2026) | No public status page found; home page Lighthouse mobile performance 40 (same test, same day) | | For AI agents | Markdown for every page, llms.txt, a REST API with an OpenAPI 3.1 spec and an MCP server | llms.txt and Markdown on its docs site; an MCP API on paid plans | | Devices | Web app on any browser, with phone alerts through Web Push | Web, an iOS app for its cloud, and a phone web app | | Price | Talk to us; set with you around the team you need | Pro 29 USD a month for 5 coworkers and 500 credits, unlimited seats; 5-day trial with a card; open source edition free | ## Deployment and feature differences - Self-hosting is how Koshra runs, set up and supported with you, where Rerun's self-hosted edition is documented but not supported - Koshra uses an Apache-2.0-licensed foundation. Koshra resale is a separate agreement, unlike Rerun's advertised AGPL-3.0 edition. Not an overall ranking. - Core data is stored on the selected server. That is not a formal residency guarantee. - A public status page, and a faster home page on the same Lighthouse test - Configured tool and CRM rules exist. Plays is limited to owner-staged email and Twenty company creation. Not a claim that every outbound path is covered. - Model provider choice and an API key are implemented. Free-tier availability is not guaranteed. ## Where the other product advertises more - Rerun is public with a published price and a self-serve trial; Koshra is in private preview with no self-serve sign-up - Each Rerun coworker has its own cloud computer you can watch and take over; Koshra's visible browser is coming soon - Rerun works with the ChatGPT, Claude and Grok plans people already pay for; plan sign-in for Koshra is coming soon - Rerun has an iOS app; Koshra is a web app only - Rerun publishes a GDPR data processing agreement; Koshra does not publish one yet and holds no certification - Rerun has a template library and shares agents by link ## Coming to Koshra Marked coming soon. None of this is counted as shipped. - Answers from the Brain that cite the notes they came from - Building a whole team from one chat - Simple model tiers, so you pick speed or depth instead of a model name - Plan sign-in for ChatGPT and Claude - A visible browser for each bot ## Questions ### Is Koshra an alternative to Rerun? Yes, for teams that want AI employees on a server they control. Koshra is self-hosted and supported, built on an Apache 2.0 open source base, and keeps data in the country you choose. Rerun is a hosted service with an AGPL-3.0 open source edition. ### Can an agency resell Koshra but not Rerun? Koshra's open source base is Apache 2.0, which allows commercial use and resale without publishing your changes; terms for Koshra are agreed with you. Rerun's open source edition is AGPL-3.0 and its trademark policy asks anyone hosting it for others to rebrand, so check both with your own counsel. ## Which to pick If you want a hosted coworker with its own cloud computer today, a published price and a self-serve trial, Rerun is further along. If you want AI employees on a server you control, in the country you choose, under a licence that lets an agency resell, with approvals on every outbound step, Koshra fits. ## Sources - [Rerun home](https://rerun.build) - [Rerun pricing](https://rerun.build/pricing) - [Rerun data processing agreement](https://rerun.build/dpa) - [Rerun docs: open source vs cloud](https://docs.rerun.build/self-host/open-source-vs-cloud.md) - [rerun-build/rerun on GitHub](https://github.com/rerun-build/rerun) - [Rerun licence (AGPL-3.0)](https://github.com/rerun-build/rerun/blob/main/LICENSE) - [Rerun trademark policy](https://github.com/rerun-build/rerun/blob/main/TRADEMARK.md) - [NVIDIA Nemotron 3 Ultra model card (open weights)](https://huggingface.co/nvidia/NVIDIA-Nemotron-3-Ultra-550B-A55B-Base-BF16) - [dots3-note preview model card (Apache 2.0)](https://huggingface.co/dots-studio/dots3-note-prev) --- # Koshra vs Lindy > A factual comparison of Koshra and Lindy, from Lindy's public pricing and security pages on 2 Nov 2026: hosting, data, approvals, models and price, including where Koshra is behind. Canonical: https://koshra.si/compare/lindy Last updated: 2026-11-07 Lindy is a hosted AI assistant for teams that works in Slack, email, meetings and messages, priced per active user with credits. Koshra is a team of AI employees with business roles that runs on a server you control. Both ask before sensitive steps. Deployment and feature differences, checked 2 November 2026. Competitor features are vendor-advertised, not independently tested. No overall winner. | Area | Koshra | Lindy | | --- | --- | --- | | What it is | An AI team with defined roles. In enabled spaces, a dispatcher can plan and assign work for review | An AI assistant per person, Slack-native, with meeting notes, inbox and scheduled work | | Where it runs | Server-hosted assisted preview. Core data stays on the selected server. Files and model providers may process data elsewhere. | Hosted cloud service; no self-hosting listed on its pricing or security pages | | Approvals | Configured tool rules and approval cards. Configured CRM rules block destructive operations and hold bulk changes. Not every outbound path is verified. | Approvals built in | | Models | Free open-weight models or your own key, per bot, with cost on every reply | Choice of model | | Apps and tools | MCP and app-connection adapters. A catalog listing is not a tested connection | 1,500+ integrations, MCP and computer use | | Security | Self-hosted, so chats, tasks and memory stay in your database; no certification today | SOC 2 Type II, GDPR and PIPEDA; HIPAA with a BAA on Enterprise | | Licence | Built on an Apache-2.0-licensed foundation. Koshra terms are separate. | Hosted service; no open source edition listed | | Price | Talk to us | Free start with 50 USD of credits for 7 days, no card; Team from 49.99 USD per active user a month with 5,000 credits; Enterprise custom | ## Deployment and feature differences - A server-hosted deployment can keep core data on the selected server. That is not a formal residency guarantee. - Koshra uses an Apache-2.0-licensed foundation. Client use needs a separate agreement. - A team of role bots with written jobs and limits, not one assistant per person - Model provider choice and an API key are implemented. Free-tier availability is not guaranteed. ## Where the other product advertises more - Lindy holds SOC 2 Type II and offers HIPAA; Koshra holds no certification - Lindy is public with a free start and published prices; Koshra is in private preview - Lindy joins meetings, works in iMessage and has computer use; Koshra's visible browser is coming soon - Lindy lists more integrations built in ## Coming to Koshra Marked coming soon. None of this is counted as shipped. - Answers from the Brain that cite the notes they came from - A visible browser for each bot - Event triggers from webhooks and app events ## Questions ### Is Koshra an alternative to Lindy? Yes, if you want AI employees on a server you control with data in the country you choose. Lindy is a hosted assistant with SOC 2 Type II and published per-user pricing. ## Which to pick If you want a hosted assistant in Slack and meetings today, with SOC 2 and a free start, Lindy is further along. If you want a team of AI employees on your own server, with data kept where you choose, Koshra fits. ## Sources - [Lindy pricing](https://www.lindy.ai/pricing) - [Lindy security](https://www.lindy.ai/security) - [NVIDIA Nemotron 3 Ultra model card (open weights)](https://huggingface.co/nvidia/NVIDIA-Nemotron-3-Ultra-550B-A55B-Base-BF16) - [dots3-note preview model card (Apache 2.0)](https://huggingface.co/dots-studio/dots3-note-prev) --- # Koshra vs Dust > A factual comparison of Koshra and Dust, from Dust's public pricing and security pages on 2 Nov 2026: hosting, data residency, approvals, models and price, including where Koshra is behind. Canonical: https://koshra.si/compare/dust Last updated: 2026-11-07 Dust is a hosted platform for building AI agents on top of your company's data, priced per seat with credits. Koshra is a team of AI employees with business roles that runs on a server you control. Both connect agents to your tools and many models. Deployment and feature differences, checked 2 November 2026. Competitor features are vendor-advertised, not independently tested. No overall winner. | Area | Koshra | Dust | | --- | --- | --- | | What it is | A ready team of AI employees with business roles and a dispatcher | A platform to build and share agents over your company data | | Where it runs | Server-hosted assisted preview. Core data stays on the selected server. Files and model providers may process data elsewhere. | Hosted, with US and EU data residency; single-tenant deployment on Enterprise | | Company knowledge | A shared Brain edited as text with versioned undo, plus memory per bot | Connectors to company data sources, searched by agents | | Approvals | Configured tool rules and approval cards. Configured CRM rules block destructive operations. Not every outbound path is verified. | Not covered on its pricing or security pages | | Models | Free open-weight models or your own key, per bot, with cost on every reply | 20+ models | | Security | Self-hosted; no certification today | SOC 2 Type II, GDPR, SSO and zero data retention; SCIM and audit logs on Enterprise | | Price | Talk to us | Seats on the Business plan: Free with 500 credits, Pro 24 EUR a seat a month billed yearly, Max 120 EUR billed yearly | ## Deployment and feature differences - Core data is stored on the selected server. That is not a formal residency guarantee. - Koshra uses an Apache-2.0-licensed foundation. Client use needs a separate agreement. - Configured tool rules exist. End-to-end coverage of every outbound path is not verified. - A ready team of role bots instead of agents you build one by one ## Where the other product advertises more - Dust holds SOC 2 Type II and offers SSO and SCIM; Koshra holds no certification - Dust searches across connected company data today; Koshra's cited answers from the Brain are coming - Dust is public with a free plan and published prices; Koshra is in private preview ## Coming to Koshra Marked coming soon. None of this is counted as shipped. - Answers from the Brain that cite the notes they came from - Plan sign-in for ChatGPT and Claude ## Questions ### Is Koshra an alternative to Dust? Yes, if you want a ready team of AI employees on your own server. Dust is a hosted agent platform with US and EU residency and SOC 2 Type II. ## Which to pick If you want hosted agents over your company data with SOC 2 and SSO today, Dust is further along. If you want a team of AI employees on a server you control, in the country you choose, Koshra fits. ## Sources - [Dust pricing](https://dust.tt/home/pricing) - [Dust security](https://dust.tt/home/security) - [NVIDIA Nemotron 3 Ultra model card (open weights)](https://huggingface.co/nvidia/NVIDIA-Nemotron-3-Ultra-550B-A55B-Base-BF16) - [dots3-note preview model card (Apache 2.0)](https://huggingface.co/dots-studio/dots3-note-prev) --- # Koshra vs n8n > A factual comparison of Koshra and n8n, from n8n's public pricing page and licence on 2 Nov 2026: self-hosting, licence for client work, approvals and price, including where Koshra is behind. Canonical: https://koshra.si/compare/n8n Last updated: 2026-11-07 n8n is a workflow automation tool with AI agent steps, offered as a hosted cloud or self-hosted. Koshra is a team of AI employees with business roles that runs on a server you control. Both can run on your own server and ask a person before a step runs. Deployment and feature differences, checked 2 November 2026. Competitor features are vendor-advertised, not independently tested. No overall winner. | Area | Koshra | n8n | | --- | --- | --- | | What it is | A ready team of AI employees with roles, a dispatcher and a shared Brain | A visual workflow builder, with an AI agent step among many nodes | | Where it runs | Server-hosted assisted preview. Core data stays on the selected server. Files and model providers may process data elsewhere. | Hosted cloud with data in Frankfurt, or self-hosted Community, Business and Enterprise editions | | Licence | Built on an Apache-2.0-licensed foundation. Koshra distribution and resale are separate agreed terms. | Sustainable Use License: use and change it for your own internal business or non-commercial purposes; enterprise features need a licence key | | Approvals | Configured tool rules and approval cards. Configured CRM rules block destructive operations. Not every outbound path is verified. | Human approval for tool calls | | Setup | Roles and routines ready, agreed with you | You design each workflow yourself | | Price | Talk to us | Cloud Starter 20 EUR and Pro 50 EUR a month billed yearly; self-hosted Business 667 EUR a month; Community Edition free | ## Deployment and feature differences - Koshra's foundation is Apache-2.0. Koshra resale is still a separate agreement. n8n's advertised licence is different. Not an overall ranking. - A ready team of role bots, so you do not build each workflow by hand - A shared Brain with versioned undo that every bot reads ## Where the other product advertises more - n8n has a large community, many nodes and years of use in production - n8n triggers workflows from webhooks and app events; Koshra's event triggers are coming soon - n8n is public with a free self-hosted edition and published prices; Koshra is in private preview ## Coming to Koshra Marked coming soon. None of this is counted as shipped. - Event triggers from webhooks and app events - Building a whole team from one chat ## Questions ### Can I use Koshra for client work where n8n's licence is limited? Koshra is built on an Apache 2.0 open source base, which allows commercial use and resale; terms for Koshra are agreed with you. n8n's Sustainable Use License allows use for your own internal business or non-commercial purposes, so check your case with n8n. ## Which to pick If you want to wire your own automations step by step, with a big community, n8n is further along. If you want a ready team of AI employees on your own server that you can also run for clients, Koshra fits. ## Sources - [n8n pricing](https://n8n.io/pricing) - [n8n licence (Sustainable Use License)](https://github.com/n8n-io/n8n/blob/master/LICENSE.md) --- # Koshra vs Turnstone > Deployment and feature differences between Koshra and Turnstone, checked 7 November 2026 against Turnstone's public facts and howto pages. Competitor features are advertised, not independently tested. No overall winner. Canonical: https://koshra.si/compare/turnstone Last updated: 2026-11-07 Checked 7 November 2026 against current public primary sources. Koshra's evidence combines installed-code inspection and bounded tests. Turnstone's capabilities below are vendor-advertised, not independently tested. These products have different deployment choices. We do not claim an overall winner. Deployment and feature differences, checked 7 November 2026. Competitor features are vendor-advertised, not independently tested. No overall winner. | Area | Koshra | Turnstone | | --- | --- | --- | | Where it runs | Server-hosted web app in assisted preview. Mac is an unreleased unsigned prototype. | Facts page: Mac app available; Cloud, web and iPhone listed as coming soon; local schedules need an awake Mac. Howto also describes Cloud schedules. That discrepancy is not a claim that Turnstone cannot run unattended anywhere. | | Team setup | Dispatcher with a plan card and countdown; one owner bot per task | A Chief of Staff agent sets up the team and hands work between agents; you approve each handoff | | Shared memory | Brain edited as text with versioned undo, plus memory per bot | Brain of Markdown files, shared and per agent, built from email and calendar; replies show which files were read | | Approvals | Configured tool rules and approval cards. Plays supports typed Twenty company creation only. | Four modes: Read Only, Ask First, Always Allow, Full Access; review cards | | Models | Per-bot model selection, mid-chat switching and fallback are implemented. Usage estimates depend on provider reporting. Free-tier availability is not guaranteed. | Bring your ChatGPT, Claude, Gemini, Grok or Cursor plan, OpenRouter, Ollama or API keys; switch mid-chat | | Apps and tools | MCP and app-connection adapters. A catalog listing is not a tested connection | 60+ built-in apps, a browser per agent, Mac apps including iMessage and WhatsApp | | Source | Server-hosted assisted preview, built on an Apache-2.0-licensed foundation. Koshra terms are separate. | Closed source, no self-hosting | ## Deployment and feature differences - Koshra Cloud is a server-hosted web app, so it is not tied to a laptop being awake. That is not a reliability or uptime guarantee. Turnstone's howto describes Cloud schedules while its facts page lists Cloud as coming soon. - Koshra Cloud is a server-hosted web app. Turnstone's facts page advertises a Mac app and lists Cloud as coming soon, while its howto also mentions Cloud schedules. Not an overall ranking. - Configured tool and CRM rules exist. Plays is limited to owner-staged email and Twenty company creation. Not a claim that every outbound path is covered. ## Where the other product advertises more - Turnstone advertises subscription sign-in; using an existing ChatGPT or Claude subscription in Koshra is coming soon - Turnstone advertises 60+ built-in apps and a browser per agent. Koshra's catalog is not a tested connection, and validated live viewing is coming soon - Turnstone advertises a released Mac app. Koshra for Mac is an unsigned prototype, not a released app - Koshra is in assisted preview, not a public self-serve download ## Which to pick If you want the Mac app Turnstone advertises, start with their facts page. If you want a server-hosted Koshra workspace that does not depend on a laptop, that is a deployment difference, not proof of better reliability. ## Sources - [Turnstone facts](https://myturnstone.ai/facts) - [Turnstone howto](https://myturnstone.ai/howto) - [Turnstone changelog](https://myturnstone.ai/changelog) - [Turnstone llms.txt](https://myturnstone.ai/llms.txt) --- # Koshra vs openbot > Deployment and feature differences between Koshra and openbot (openbot.run), checked 7 November 2026. Competitor features are advertised, not independently tested. No overall winner. Canonical: https://koshra.si/compare/openbot Last updated: 2026-11-07 Checked 7 November 2026 against openbot.run. OpenBot advertises desktop and phone clients, managed team servers and workflow approvals, so those are not unique Koshra advantages. Its home page also warns that agents can read and change files, run commands, use the network and use a browser without asking each time. That warning is a vendor statement, not an independent finding. We do not claim an overall winner. Deployment and feature differences, checked 7 November 2026. Competitor features are vendor-advertised, not independently tested. No overall winner. | Area | Koshra | openbot | | --- | --- | --- | | Where it runs | Server-hosted web app in assisted preview. Mac is an unreleased unsigned prototype. | Advertises macOS, Windows and Linux desktop apps, phone connection apps, and managed team servers | | Team setup | Dispatcher with a plan card and countdown; one owner bot per task | A channel lead routes work to one or many agents; Tasks page; plan card before long tasks; workflow canvas with GitHub triggers | | Shared memory | Brain edited as text with versioned undo, plus memory per bot | Memories per agent with background memory review | | Approvals | Configured tool rules and approval cards. Plays supports owner-staged email and typed Twenty company creation only. | Advertises workflow approval steps. The home page also warns that agents can act without asking each time. Not independently tested. | | Models | Per-bot model selection, mid-chat switching and fallback are implemented. Usage estimates depend on provider reporting. Free-tier availability is not guaranteed. | 12+ providers including Codex, Claude Code, Gemini, Grok, Cursor and local models; backup model on limits; usage bars and cost per turn | | Apps and tools | MCP and app-connection adapters. A catalog listing is not a tested connection | Marketplace of apps, agents and skills; agent browser, remote desktop, Slack, Discord, Telegram, GitHub | | Licence | Built on an Apache-2.0-licensed foundation. Koshra terms are separate. | PolyForm Noncommercial; commercial use needs a paid licence | ## Deployment and feature differences - A shared team Brain with versioned undo, alongside per-bot memory - Configured tool and CRM rules exist. Plays is limited to owner-staged email and Twenty company creation. Not a claim that every outbound path is covered. - Built for client work under commercial terms you agree with us ## Where the other product advertises more - OpenBot advertises desktop and phone clients. Koshra's native apps are coming soon, and Mac is an unreleased prototype - OpenBot advertises subscription and local model providers. Koshra subscription sign-in is coming soon - OpenBot advertises a marketplace and a built-in browser. Koshra's validated live viewing is coming soon - OpenBot is a public product with a commercial licence. Koshra is in assisted preview ## Which to pick OpenBot already advertises managed servers and approvals. Choose it when those advertised clients fit. Choose Koshra Cloud when you want this server-hosted workspace and accept that restart, reconnection and Mac release are unfinished. ## Sources - [openbot home](https://openbot.run) - [openbot llms.txt](https://openbot.run/llms.txt) - [openbot changelog](https://openbot.run/changelog) - [openbot pricing](https://openbot.run/pricing) - [nightly-labs/openbot on GitHub](https://github.com/nightly-labs/openbot) --- # Koshra vs Reason Machines > A factual comparison of Koshra and Reason from Reason Machines, from its public pages on 2 Nov 2026: where each is ahead and where Koshra is behind. Canonical: https://koshra.si/compare/reason_machines Last updated: 2026-11-07 Reason, from Reason Machines, is a hosted coding agent and always-on teammate with its own cloud computer per session. Koshra is a self-hosted web app that runs a team of AI employees with defined business roles. Both keep memory across work and ask before sensitive steps. Deployment and feature differences, checked 2 November 2026. Competitor features are vendor-advertised, not independently tested. No overall winner. | Area | Koshra | Reason Machines | | --- | --- | --- | | What it is | An AI team with defined roles for sales, support, research, recruiting and more | A frontier coding agent that is also an always-on teammate, working alongside other coding agents | | Where it runs | Server-hosted web app in assisted preview. Mac is an unreleased unsigned prototype. | Hosted cloud, with a cloud computer per session; web, Mac and iOS apps, a CLI and Slack | | Team setup | Dispatcher with a plan card and countdown; one owner bot per task; team chats per lead | Sessions with subagents; Reason Network lets your agents message each other | | Shared memory | Brain edited as text with versioned undo, plus memory per bot | Memory across sessions, in personal and team scopes | | Approvals | Configured tool rules and approval cards. Plays supports typed Twenty company creation only. | Email sends show a preview, workspace rules can require a yes, and code lands as pull requests | | Schedules | Routines on the server; every new schedule needs approval | Loops on a schedule, a webhook, GitHub events or Slack messages | | Models | Per-bot model selection, mid-chat switching and fallback are implemented. Usage estimates depend on provider reporting. Free-tier availability is not guaranteed. | Bring your ChatGPT, Claude, Grok or Copilot plan or API keys, with fallback to other accounts | | For AI agents | Markdown for every page, llms.txt, llms-full.txt, a REST API with an OpenAPI spec, an MCP server and an agent guide | Markdown for every page, llms.txt, llms-full.txt, a REST API and an MCP server | | Source and price | Server-hosted assisted preview. Pricing: contact us. Foundation licence is Apache-2.0; Koshra terms are separate. | Hosted and closed source, apart from the MIT and Apache 2.0 network engine; Pro 50 USD and Max 200 USD a month, no free plan | ## Deployment and feature differences - Built for business roles beyond code, with team use cases and a written job and limit for every role - Koshra Cloud is server-hosted. Reason advertises a hosted product. Not an overall ranking. - Model provider choice and an API key are implemented. Free-tier availability is not guaranteed.; Reason has no free plan - Configured tool rules, bulk review and schedule approval exist for the paths that are implemented. Not every outbound path is verified. - A shared Brain you edit as text with versioned undo ## Where the other product advertises more - Reason has web, Mac and iOS apps and a CLI; Koshra is a web app only - Reason works with the AI plans people already pay for; plan sign-in for Koshra is coming soon - Anyone who signs up can use Reason's REST API and MCP server; Koshra's need a key from a space admin, and spaces are set up with you during the private preview - Koshra's status page is checked every minute by an independent uptime monitor, but its history only starts in November 2026 - Reason is public with self-serve sign-up, a trial and published prices; Koshra is in private preview - Reason triggers work from webhooks, GitHub and Slack; Koshra's event triggers are coming soon ## Which to pick If your work is mostly code and you want a hosted agent across web, Mac, iOS and the command line, Reason is further along. If you want AI employees for sales, support, research and operations on a server you control, with approvals on every outbound step, Koshra fits. ## Sources - [Reason Machines home](https://reasonmachines.com) - [Reason Machines llms.txt](https://reasonmachines.com/llms.txt) - [Reason Machines: AI employees](https://reasonmachines.com/ai-employees) - [Introducing Reason 1.1](https://reasonmachines.com/blog/introducing-reason-agent-1-1) - [Reason Machines on Y Combinator](https://www.ycombinator.com/companies/reason-machines) - [reason-machines/reason-network on GitHub](https://github.com/reason-machines/reason-network) - [Reason Machines status](https://status.reasonmachines.com) - [NVIDIA Nemotron 3 Ultra model card (open weights)](https://huggingface.co/nvidia/NVIDIA-Nemotron-3-Ultra-550B-A55B-Base-BF16) - [dots3-note preview model card (Apache 2.0)](https://huggingface.co/dots-studio/dots3-note-prev) --- # Changelog > What changed in the Koshra app and on this site, by date. Canonical: https://koshra.si/changelog Last updated: 2026-11-07 ## 2026-11-07: Copy correction: no overall ranking (Site) - Home, docs, security, comparisons, llms and generated pages now mark Mac, dedicated computers, advanced Knowledge, complete Plays and OS sandboxing as coming soon - Turnstone and OpenBot pages checked 7 November 2026 against public primary sources. Competitor features are advertised, not independently tested - Older changelog entries below are kept as they were written ## 2026-11-03: Site v7: comparisons, catalog apps, licence and residency answers (Site) - Comparison pages for Rerun, Lindy, Dust and n8n, each dated and sourced, with where Koshra is behind and what is coming - Pages for apps in the Koshra app catalog, such as Salesforce, Zendesk, Jira and Microsoft Teams, with the roles that use each one - Use cases for agencies and for founders, built from the roles in our own workspace - Direct answers on reselling Koshra under its Apache 2.0 open source base, and on keeping data in India, the EU or wherever your server is - An RSS feed for this changelog ## 2026-11-02: Create a bot from a description, 48 role templates and bot icons (App) - Describe the bot you need in plain words and Koshra drafts it for you to review - Or start from one of 48 role templates - An icon picker with 78 icons and 12 colours, and every bot in a space now has an icon - New bots start on a free model, and you can change it per bot ## 2026-11-02: An independent uptime monitor behind the status page (Site) - The status page now reads an independent uptime monitor that checks the API, web app, website and integrations every minute - A public status page at status.lumenlab.tech, with the app's own status feed as a fallback - Each service shows its uptime for the last 24 hours ## 2026-11-02: Site v6.3: own your AI team (Site) - A new home page section: your server, your data, your agents and your tools, with nothing rented back to you - Self-hosted, built on an Apache 2.0 open source base, free open-weight models and no lock-in to one model, now on the home page, Security, the comparisons, the FAQ and the Markdown copies - Model calls still go to the provider you pick for each bot, and the site says so ## 2026-11-02: A REST API and an MCP server for other agents (App) - Space admins make scoped API keys in Koshra; the secret is shown once and only a hash is stored - REST endpoints for bots, the Tasks board and task status, with an OpenAPI 3.1 spec - An MCP server with list_bots, read_tasks_board, get_task_status and create_task - Work that needs approval never starts from a key - A public health check and status feed, checked every 5 minutes ## 2026-11-02: Site v6.2: Markdown for agents, use cases, integrations and a glossary (Site) - Every page is also served as Markdown, at its path plus .md or with Accept: text/markdown - llms.txt and llms-full.txt are now built from every page on the site - Use cases for nine teams and a page for each role, from the roles in our own Koshra workspace - An integrations directory, a glossary, five new docs pages and a page for each workflow - A clickable replica of the Koshra app with scripted data, and new illustrated motion - A comparison page for Reason Machines - A live status page for the API, web app and website, read from the Koshra app's status feed - Docs for the REST API and MCP server ## 2026-11-02: Site v6.1: docs, changelog, comparisons, security (Site) - Docs: getting started plus pages on AI employees, the dispatcher, approvals, memory, integrations, models and self-hosting - This changelog, a security page, a status placeholder and comparison pages for Turnstone and openbot - Colour contrast raised to WCAG AA across the site ## 2026-11-02: Site v6: the product is now Koshra (Site) - New name, Koshra, from the Sanskrit kosha, a treasury or store - New mark, favicon set and app icons - New line: Your AI team, and everything it knows ## 2026-11-01: Site v5.2: Ask AI in the footer (Site) - Ask ChatGPT, Claude, Google AI Mode, Perplexity or Grok about Koshra from the footer ## 2026-11-01: Site v5.1: answers for AI assistants (Site) - llms.txt and llms-full.txt, a sitemap and structured data - A visible FAQ ## 2026-11-01: Site v5: The floor (Site) - A new design built around an office floor of AI employees, with scroll-driven layers - Self-hosted fonts and full reduced-motion support ## 2026-11-01: Tasks board, plan card and guards (App) - Tasks board with one owner bot per task - Dispatcher plan card with a countdown you can stop - Continue and reassign, with guards on who may reassign - Branch from any message - Per-bot permission modes and looks - Reply time on every message and a configurable stuck threshold ## 2026-11-01: New app design (App) - Light, dark and system themes, with palettes and looks - Model and USD chips on replies - A stuck-run bar with cancel ## 2026-11-01: CRM guard rails (App) - CRM deletes and merges blocked - Bulk CRM changes and writes over 25 records need approval - Tasks added by hand get the same limits and policy checks as dispatched ones ## 2026-11-01: Phone alerts, Brain undo, templates (App) - Web Push alerts on your phone - Brain editing with versioned undo - Templates and writing voice - Model picker in the chat composer ## 2026-10-31: Model switch and cost per reply (App) - Switch a bot's model mid-chat - Model and cost shown on every reply - Runs waiting for input expire instead of hanging --- # Copy correction: no overall ranking > 2026-11-07, Site: Home, docs, security, comparisons, llms and generated pages now mark Mac, dedicated computers, advanced Knowledge, complete Plays and OS sandboxing as coming soon; Turnstone and OpenBot pages checked 7 November 2026 against public primary sources. Competitor features are advertised, not independently tested; Older changelog entries below are kept as they were written. Canonical: https://koshra.si/changelog/2026-11-07_copy_correction Last updated: 2026-11-07 Date: 2026-11-07 Area: Site - Home, docs, security, comparisons, llms and generated pages now mark Mac, dedicated computers, advanced Knowledge, complete Plays and OS sandboxing as coming soon - Turnstone and OpenBot pages checked 7 November 2026 against public primary sources. Competitor features are advertised, not independently tested - Older changelog entries below are kept as they were written --- # Site v7: comparisons, catalog apps, licence and residency answers > 2026-11-03, Site: Comparison pages for Rerun, Lindy, Dust and n8n, each dated and sourced, with where Koshra is behind and what is coming; Pages for apps in the Koshra app catalog, such as Salesforce, Zendesk, Jira and Microsoft Teams, with the roles that use each one; Use cases for agencies and for founders, built from the roles in our own workspace; Direct answers on reselling Koshra under its Apache 2.0 open source base, and on keeping data in India, the EU or wherever your server is; An RSS feed for this changelog. Canonical: https://koshra.si/changelog/2026-11-03_site_v7 Last updated: 2026-11-07 Date: 2026-11-03 Area: Site - Comparison pages for Rerun, Lindy, Dust and n8n, each dated and sourced, with where Koshra is behind and what is coming - Pages for apps in the Koshra app catalog, such as Salesforce, Zendesk, Jira and Microsoft Teams, with the roles that use each one - Use cases for agencies and for founders, built from the roles in our own workspace - Direct answers on reselling Koshra under its Apache 2.0 open source base, and on keeping data in India, the EU or wherever your server is - An RSS feed for this changelog --- # Create a bot from a description, 48 role templates and bot icons > 2026-11-02, App: Describe the bot you need in plain words and Koshra drafts it for you to review; Or start from one of 48 role templates; An icon picker with 78 icons and 12 colours, and every bot in a space now has an icon; New bots start on a free model, and you can change it per bot. Canonical: https://koshra.si/changelog/2026-11-02_create_a_bot_from_a_description_48_role_templates_and_bot_icons Last updated: 2026-11-07 Date: 2026-11-02 Area: App - Describe the bot you need in plain words and Koshra drafts it for you to review - Or start from one of 48 role templates - An icon picker with 78 icons and 12 colours, and every bot in a space now has an icon - New bots start on a free model, and you can change it per bot --- # An independent uptime monitor behind the status page > 2026-11-02, Site: The status page now reads an independent uptime monitor that checks the API, web app, website and integrations every minute; A public status page at status.lumenlab.tech, with the app's own status feed as a fallback; Each service shows its uptime for the last 24 hours. Canonical: https://koshra.si/changelog/2026-11-02_an_independent_uptime_monitor_behind_the_status_page Last updated: 2026-11-07 Date: 2026-11-02 Area: Site - The status page now reads an independent uptime monitor that checks the API, web app, website and integrations every minute - A public status page at status.lumenlab.tech, with the app's own status feed as a fallback - Each service shows its uptime for the last 24 hours --- # Site v6.3: own your AI team > 2026-11-02, Site: A new home page section: your server, your data, your agents and your tools, with nothing rented back to you; Self-hosted, built on an Apache 2.0 open source base, free open-weight models and no lock-in to one model, now on the home page, Security, the comparisons, the FAQ and the Markdown copies; Model calls still go to the provider you pick for each bot, and the site says so. Canonical: https://koshra.si/changelog/2026-11-02_site_v6_3 Last updated: 2026-11-07 Date: 2026-11-02 Area: Site - A new home page section: your server, your data, your agents and your tools, with nothing rented back to you - Self-hosted, built on an Apache 2.0 open source base, free open-weight models and no lock-in to one model, now on the home page, Security, the comparisons, the FAQ and the Markdown copies - Model calls still go to the provider you pick for each bot, and the site says so --- # A REST API and an MCP server for other agents > 2026-11-02, App: Space admins make scoped API keys in Koshra; the secret is shown once and only a hash is stored; REST endpoints for bots, the Tasks board and task status, with an OpenAPI 3.1 spec; An MCP server with list_bots, read_tasks_board, get_task_status and create_task; Work that needs approval never starts from a key; A public health check and status feed, checked every 5 minutes. Canonical: https://koshra.si/changelog/2026-11-02_a_rest_api_and_an_mcp_server_for_other_agents Last updated: 2026-11-07 Date: 2026-11-02 Area: App - Space admins make scoped API keys in Koshra; the secret is shown once and only a hash is stored - REST endpoints for bots, the Tasks board and task status, with an OpenAPI 3.1 spec - An MCP server with list_bots, read_tasks_board, get_task_status and create_task - Work that needs approval never starts from a key - A public health check and status feed, checked every 5 minutes --- # Site v6.2: Markdown for agents, use cases, integrations and a glossary > 2026-11-02, Site: Every page is also served as Markdown, at its path plus .md or with Accept: text/markdown; llms.txt and llms-full.txt are now built from every page on the site; Use cases for nine teams and a page for each role, from the roles in our own Koshra workspace; An integrations directory, a glossary, five new docs pages and a page for each workflow; A clickable replica of the Koshra app with scripted data, and new illustrated motion; A comparison page for Reason Machines; A live status page for the API, web app and website, read from the Koshra app's status feed; Docs for the REST API and MCP server. Canonical: https://koshra.si/changelog/2026-11-02_site_v6_2 Last updated: 2026-11-07 Date: 2026-11-02 Area: Site - Every page is also served as Markdown, at its path plus .md or with Accept: text/markdown - llms.txt and llms-full.txt are now built from every page on the site - Use cases for nine teams and a page for each role, from the roles in our own Koshra workspace - An integrations directory, a glossary, five new docs pages and a page for each workflow - A clickable replica of the Koshra app with scripted data, and new illustrated motion - A comparison page for Reason Machines - A live status page for the API, web app and website, read from the Koshra app's status feed - Docs for the REST API and MCP server --- # Site v6.1: docs, changelog, comparisons, security > 2026-11-02, Site: Docs: getting started plus pages on AI employees, the dispatcher, approvals, memory, integrations, models and self-hosting; This changelog, a security page, a status placeholder and comparison pages for Turnstone and openbot; Colour contrast raised to WCAG AA across the site. Canonical: https://koshra.si/changelog/2026-11-02_site_v6_1 Last updated: 2026-11-07 Date: 2026-11-02 Area: Site - Docs: getting started plus pages on AI employees, the dispatcher, approvals, memory, integrations, models and self-hosting - This changelog, a security page, a status placeholder and comparison pages for Turnstone and openbot - Colour contrast raised to WCAG AA across the site --- # Site v6: the product is now Koshra > 2026-11-02, Site: New name, Koshra, from the Sanskrit kosha, a treasury or store; New mark, favicon set and app icons; New line: Your AI team, and everything it knows. Canonical: https://koshra.si/changelog/2026-11-02_site_v6 Last updated: 2026-11-07 Date: 2026-11-02 Area: Site - New name, Koshra, from the Sanskrit kosha, a treasury or store - New mark, favicon set and app icons - New line: Your AI team, and everything it knows --- # Site v5.2: Ask AI in the footer > 2026-11-01, Site: Ask ChatGPT, Claude, Google AI Mode, Perplexity or Grok about Koshra from the footer. Canonical: https://koshra.si/changelog/2026-11-01_site_v5_2 Last updated: 2026-11-07 Date: 2026-11-01 Area: Site - Ask ChatGPT, Claude, Google AI Mode, Perplexity or Grok about Koshra from the footer --- # Site v5.1: answers for AI assistants > 2026-11-01, Site: llms.txt and llms-full.txt, a sitemap and structured data; A visible FAQ. Canonical: https://koshra.si/changelog/2026-11-01_site_v5_1 Last updated: 2026-11-07 Date: 2026-11-01 Area: Site - llms.txt and llms-full.txt, a sitemap and structured data - A visible FAQ --- # Site v5: The floor > 2026-11-01, Site: A new design built around an office floor of AI employees, with scroll-driven layers; Self-hosted fonts and full reduced-motion support. Canonical: https://koshra.si/changelog/2026-11-01_site_v5 Last updated: 2026-11-07 Date: 2026-11-01 Area: Site - A new design built around an office floor of AI employees, with scroll-driven layers - Self-hosted fonts and full reduced-motion support --- # Tasks board, plan card and guards > 2026-11-01, App: Tasks board with one owner bot per task; Dispatcher plan card with a countdown you can stop; Continue and reassign, with guards on who may reassign; Branch from any message; Per-bot permission modes and looks; Reply time on every message and a configurable stuck threshold. Canonical: https://koshra.si/changelog/2026-11-01_tasks_board_plan_card_and_guards Last updated: 2026-11-07 Date: 2026-11-01 Area: App - Tasks board with one owner bot per task - Dispatcher plan card with a countdown you can stop - Continue and reassign, with guards on who may reassign - Branch from any message - Per-bot permission modes and looks - Reply time on every message and a configurable stuck threshold --- # New app design > 2026-11-01, App: Light, dark and system themes, with palettes and looks; Model and USD chips on replies; A stuck-run bar with cancel. Canonical: https://koshra.si/changelog/2026-11-01_new_app_design Last updated: 2026-11-07 Date: 2026-11-01 Area: App - Light, dark and system themes, with palettes and looks - Model and USD chips on replies - A stuck-run bar with cancel --- # CRM guard rails > 2026-11-01, App: CRM deletes and merges blocked; Bulk CRM changes and writes over 25 records need approval; Tasks added by hand get the same limits and policy checks as dispatched ones. Canonical: https://koshra.si/changelog/2026-11-01_crm_guard_rails Last updated: 2026-11-07 Date: 2026-11-01 Area: App - CRM deletes and merges blocked - Bulk CRM changes and writes over 25 records need approval - Tasks added by hand get the same limits and policy checks as dispatched ones --- # Phone alerts, Brain undo, templates > 2026-11-01, App: Web Push alerts on your phone; Brain editing with versioned undo; Templates and writing voice; Model picker in the chat composer. Canonical: https://koshra.si/changelog/2026-11-01_phone_alerts_brain_undo_templates Last updated: 2026-11-07 Date: 2026-11-01 Area: App - Web Push alerts on your phone - Brain editing with versioned undo - Templates and writing voice - Model picker in the chat composer --- # Model switch and cost per reply > 2026-10-31, App: Switch a bot's model mid-chat; Model and cost shown on every reply; Runs waiting for input expire instead of hanging. Canonical: https://koshra.si/changelog/2026-10-31_model_switch_and_cost_per_reply Last updated: 2026-11-07 Date: 2026-10-31 Area: App - Switch a bot's model mid-chat - Model and cost shown on every reply - Runs waiting for input expire instead of hanging --- # Security > What Koshra configures today, and what is still unfinished: encryption, tenant controls, approvals, hosting and the absence of a security certification. Canonical: https://koshra.si/security Last updated: 2026-11-07 ## Assisted preview A server-hosted workspace, set up with you. Run a server-hosted Koshra deployment with assisted setup. Hosting, support and model-provider terms are agreed separately. - Cloud: Koshra Cloud is the server-hosted web app, in assisted preview. - Mac: Koshra for Mac is coming soon: an unsigned local prototype, not a released app. Optional linking between Cloud and Mac is not available yet. - Computers: Bots currently use shared cloud computers. Dedicated per-bot computers and fully validated live viewing are coming soon. - Your data: Core application data is stored on the selected server. Files, connected services and model providers may process data elsewhere. - Foundation licence: Built on an Apache-2.0-licensed foundation. Koshra-specific distribution, support and resale rights are governed by separate agreed terms. - Models: Choose supported model providers or bring an API key. Provider charges, quotas, availability and data policies apply. Some providers offer free-tier models; availability is not guaranteed. - Sign-in: Google and generic OIDC sign-in are coming soon: the implementation exists, but production credentials and end-to-end sign-in are not configured or validated. Using an existing ChatGPT or Claude subscription is also coming soon. - Plays: Plays is a preview catalog. Supported actions are limited to owner-staged email and Twenty company creation, with a separate explicit approval. - Isolation: Cloud computer isolation has passed bounded synthetic checks. Full supervisor restart and reconnection acceptance is unfinished. Mac OS-enforced sandboxing is coming soon. Review each configured provider before choosing a residency policy. No security certification, contractual uptime or overall product ranking is claimed. ## Licence, data residency and support ### Can an agency resell or white-label Koshra? Only under separate agreed terms. The Apache-2.0 licence covers the foundation, not every Koshra release asset or commercial right. ### Where is my data stored? Core application data is stored on the selected server. Files, connected services and model providers may process data elsewhere. Review each configured provider before choosing a residency policy. Koshra does not claim a formal residency certification. ### Is self-hosting supported? Assisted self-hosting is available by arrangement. Production changes should have a reviewed backup and rollback plan. That is not a contractual promise that every change already has one. ### What licence is the foundation under? Apache-2.0 for the foundation. It allows commercial use of that foundation under its own terms. Koshra-specific distribution, support and resale rights are governed by separate agreed terms. ### Does Koshra hold SOC 2 or ISO 27001? No. No security certification is claimed. Content encryption and an encrypted credential store are configured. Tenant-aware authorization and database isolation controls exist. Comprehensive security acceptance remains unfinished. ## Approval policy Review drafts before use. The limited Plays email action requires explicit owner approval. Ordinary connector actions follow configured tool rules. End-to-end coverage across all outbound paths is not yet verified. - Configured CRM rules block destructive operations and require review for bulk changes. - Plays currently supports only typed Twenty company creation. HubSpot and arbitrary CRM play writes are not supported. - Creating a bot or a schedule can require approval where that rule is configured. - Content encryption and an encrypted credential store are configured. Comprehensive security acceptance remains unfinished. ## Hosting Assisted self-hosting is available by arrangement. A deployment can include a web app, API, worker, supervisor and database. Protected routes refuse requests without a signed-in session where that check is configured. Google and OIDC production credentials are not configured. ## Data handling - Core application data is stored on the selected server. - Files, connected services and model providers may process data elsewhere. - Demo requests on this site are stored on our server for follow-up about Koshra. This page does not promise a retention period or that data is never shared. - Security-event logging and a default 90-day event pruner are implemented. Immutable off-host audit export, general retention and offsite disaster-recovery validation are coming soon. ## Operations Production changes should have a reviewed backup and rollback plan. Public status reports observed service health. No contractual uptime or high-availability guarantee is published. ## Certifications No security certification is claimed. If you need a security review, talk to us: https://cal.lumenlab.tech/rasul/30min --- # Status > Observed health of the Koshra API, web app and website. This is not a contractual uptime or high-availability guarantee. Canonical: https://koshra.si/status Last updated: 2026-11-07 Public status reports observed service health. No contractual uptime or high-availability guarantee is published. Current state: https://koshra.si/status.md Recent changes: https://koshra.si/changelog --- ## Contact - Book a demo: https://cal.lumenlab.tech/rasul/30min - Sign in: https://app.koshra.com - Koshra is a product of Xeme AI Lab.