# Buff Development

> Buff is a company AI platform with three ways in. Development: describe a task and get a finished pull request that you review and approve; every step is under human control. Knowledge space: any department — support, sales, legal, HR, finance, marketing, management — asks questions and orders research across the company’s documents and systems, and each answer comes with a link to its source. Buff Code: a development environment for engineers on the organisation’s models. The connector is installed in the company network once; a system outside the ready-made catalog the company connects with its own tool.

Full text of every page: https://buff.systems/en/llms-full.txt
Every page is also available as clean markdown — add `.md` to its address (for example, /en/pricing.md or /en/docs/tasks.md).

## Product

- [Buff Development](https://buff.systems/en) ([md](https://buff.systems/en/index.md)): AI for the whole company: autonomous development, answers from documents for every department, Buff Code for engineers — a platform overview.
- [Features](https://buff.systems/en/product) ([md](https://buff.systems/en/product.md)): What Buff does: from setting a task to a finished pull request — and answers from documents for teams without code.
- [Use cases](https://buff.systems/en/use-cases) ([md](https://buff.systems/en/use-cases.md)): Use cases for development and for the company’s departments: support, sales, legal, HR, finance, marketing, management.
- [For business](https://buff.systems/en/business) ([md](https://buff.systems/en/business.md)): Buff for teams without developers: a no-code space where product questions are answered from the team’s documents — with a link to the source.
- [Buff Code](https://buff.systems/en/buff-code) ([md](https://buff.systems/en/buff-code.md)): A development environment for engineers who write their own code: the company’s models, references and trackers, shared by the team, billed to the organisation.
- [Mobile app](https://buff.systems/en/mobile) ([md](https://buff.systems/en/mobile.md)): Buff on iPhone and Android: approve a task, answer the agent, allow a Buff Code command — from your phone, with notifications and end-to-end encryption.
- [Buff Community Edition](https://buff.systems/en/community) ([md](https://buff.systems/en/community.md)): The free edition of Buff on your own machine: development by task, “Ask”, research and a knowledge base on your model. Installed with one command.
- [Mobile app licences](https://buff.systems/en/mobile/licenses) ([md](https://buff.systems/en/mobile/licenses.md)): Third-party components of the Buff mobile app: names, versions, licences and copyright holders.
- [Enterprise on-premise](https://buff.systems/en/enterprise) ([md](https://buff.systems/en/enterprise.md)): All of Buff on your infrastructure: your model, single sign-on through your IdP, an audit log, an air-gapped network, support under contract.
- [Security](https://buff.systems/en/security) ([md](https://buff.systems/en/security.md)): How access control and the protection of code and data work.
- [Pricing](https://buff.systems/en/pricing) ([md](https://buff.systems/en/pricing.md)): You pay for the AI’s work in roubles. The plan determines what it runs on and what the price is made of.
- [Demo workspace](https://buff.systems/en/demo) ([md](https://buff.systems/en/demo.md)): A working workspace where Buff has already completed tasks, answered questions from documents and carried out research. Opens without sign-up, view only.
- [Integration catalogue](https://buff.systems/en/marketplace) ([md](https://buff.systems/en/marketplace.md)): Integrations that install into a running connector without a rebuild. Each shows where it connects, what it asks for and which tools it gives the model.
- [Download the connector, Buff Code and the app](https://buff.systems/en/downloads) ([md](https://buff.systems/en/downloads.md)): The connector for your network (git without handing over tokens), Buff Code on your organisation’s models, the Buff app for iPhone and Android. Cosign-signed.
- [Feedback](https://buff.systems/en/contact) ([md](https://buff.systems/en/contact.md)): A form to contact the Buff team.
- [Task writing](https://buff.systems/en/product/tasks) ([md](https://buff.systems/en/product/tasks.md)): Describe the task in plain language — Buff clarifies the details and proposes a formulation that you approve yourself.
- [Autonomous pipeline](https://buff.systems/en/product/pipeline) ([md](https://buff.systems/en/product/pipeline.md)): A task is broken into atoms and built in dependency order — with a clear execution diagram and live progress.
- [Review and comments](https://buff.systems/en/product/review) ([md](https://buff.systems/en/product/review.md)): Changes go through review: diffs by module, discussion and comments from the model and from you — with an “approve” or “send back” decision.
- [Publishing upstream](https://buff.systems/en/product/publish) ([md](https://buff.systems/en/product/publish.md)): Once approved, Buff opens a pull request or merge request directly in your repository — on GitHub, GitLab, Bitbucket or Gitea.
- [Ask](https://buff.systems/en/product/ask) ([md](https://buff.systems/en/product/ask.md)): Questions about code, trackers and documents — read-only: Buff reads and answers without changing anything. Works for a repository and in a no-code space.
- [Deep research](https://buff.systems/en/product/research) ([md](https://buff.systems/en/product/research.md)): An analyst and a reviewer work through a question using the code, tracker tickets and team documents, and prepare a checked document with PDF export.
- [Audits](https://buff.systems/en/product/audits) ([md](https://buff.systems/en/product/audits.md)): An understanding of the codebase “as is”, section by section — the starting point for good autonomous development.
- [Project onboarding](https://buff.systems/en/product/onboarding) ([md](https://buff.systems/en/product/onboarding.md)): Connecting a repository, building the project and preparing the development tools — so the project gets a reproducible baseline.
- [Members and roles](https://buff.systems/en/product/teams) ([md](https://buff.systems/en/product/teams.md)): Organisations, member roles and repository access — teamwork under control.

## Use cases

- [Customer support](https://buff.systems/en/use-cases/support) ([md](https://buff.systems/en/use-cases/support.md)): Agents answer customers from the contract and the policy, not from memory — and see where documents disagree.
- [Sales](https://buff.systems/en/use-cases/sales) ([md](https://buff.systems/en/use-cases/sales.md)): Terms of past deals, the price list and the discount policy — in one question, with a link to the contract and the proposal.
- [Legal and contracts](https://buff.systems/en/use-cases/legal) ([md](https://buff.systems/en/use-cases/legal.md)): The number, term and conditions of any contract in the folder — in a minute; the difference between policy editions — as a table.
- [HR and onboarding newcomers](https://buff.systems/en/use-cases/hr) ([md](https://buff.systems/en/use-cases/hr.md)): A newcomer asks about leave, access and the first week right where they read the policy — and gets a link to the policy.
- [Finance and accounting](https://buff.systems/en/use-cases/finance) ([md](https://buff.systems/en/use-cases/finance.md)): The month’s contract payments, a budget line from the spreadsheet and a counterparty’s closing documents — with a link to the file and the sheet.
- [Marketing](https://buff.systems/en/use-cases/marketing) ([md](https://buff.systems/en/use-cases/marketing.md)): The brand book, positioning and presentations answer for themselves: what is allowed, what is not, and where a text departs from the document.
- [Head of department](https://buff.systems/en/use-cases/leadership) ([md](https://buff.systems/en/use-cases/leadership.md)): Decisions on a project over the quarter, open questions and discrepancies between department reports — from minutes and reports, not from memory.
- [Onboarding a legacy repository](https://buff.systems/en/use-cases/legacy-onboarding) ([md](https://buff.systems/en/use-cases/legacy-onboarding.md)): An unfamiliar service with no tests and no documentation stops being a black box — from “how does this even work” to the first safe change.
- [A feature end to end](https://buff.systems/en/use-cases/feature-delivery) ([md](https://buff.systems/en/use-cases/feature-delivery.md)): The full cycle of one task — from draft to pull request, under your control.
- [Working through the backlog](https://buff.systems/en/use-cases/backlog) ([md](https://buff.systems/en/use-cases/backlog.md)): A stream of small tasks goes into autonomous development — and you are called in only when needed.
- [Understanding someone else’s code](https://buff.systems/en/use-cases/understand-code) ([md](https://buff.systems/en/use-cases/understand-code.md)): Find your way around an unfamiliar project — from a quick question to a full audit, read-only.
- [Working a solution through](https://buff.systems/en/use-cases/deep-research) ([md](https://buff.systems/en/use-cases/deep-research.md)): You start a research — and get a verified document on your code and the team’s documents, exportable to PDF.
- [Teamwork](https://buff.systems/en/use-cases/teamwork) ([md](https://buff.systems/en/use-cases/teamwork.md)): Organisations, roles, repository access, access keys and connectors — under the owner’s control.
- [Product and analytics: requirements and decisions](https://buff.systems/en/use-cases/knowledge-hub) ([md](https://buff.systems/en/use-cases/knowledge-hub.md)): A space without code for product managers, analysts and stakeholders: one question, one answer from the team’s documents, with a link to the source.

## Integrations

- [Bitbucket Cloud — an integration for Buff](https://buff.systems/en/marketplace/bitbucket-cloud) ([md](https://buff.systems/en/marketplace/bitbucket-cloud.md)): Questions and answers right in bitbucket.org pull requests — where the review happens.
- [Bitbucket Data Center — an integration for Buff](https://buff.systems/en/marketplace/bitbucket-dc) ([md](https://buff.systems/en/marketplace/bitbucket-dc.md)): Questions and answers right in the pull requests of your Bitbucket Data Center or Server — where the review happens.
- [Confluence — an integration for Buff](https://buff.systems/en/marketplace/confluence) ([md](https://buff.systems/en/marketplace/confluence.md)): The team’s knowledge base as context for answers — and questions right in the page discussion. Data Center, Server and Cloud.
- [Figma — an integration for Buff](https://buff.systems/en/marketplace/figma) ([md](https://buff.systems/en/marketplace/figma.md)): Designs as context: parameters, tokens and screen structure for any model, the picture for one that can see. Questions in design comments.
- [Files on disk — an integration for Buff](https://buff.systems/en/marketplace/files) ([md](https://buff.systems/en/marketplace/files.md)): Folders on the server and SMB network folders as context: Word, Excel, PowerPoint — new and old formats — PDF and text. Read only, no index.
- [Gitea — an integration for Buff](https://buff.systems/en/marketplace/gitea) ([md](https://buff.systems/en/marketplace/gitea.md)): Questions and answers right in the issues and pull requests of your Gitea or Forgejo — where the team already discusses the code.
- [GitHub — an integration for Buff](https://buff.systems/en/marketplace/github) ([md](https://buff.systems/en/marketplace/github.md)): Questions and answers right in GitHub issues and pull requests — both in the github.com cloud and in Enterprise Server inside your network.
- [GitLab — an integration for Buff](https://buff.systems/en/marketplace/gitlab) ([md](https://buff.systems/en/marketplace/gitlab.md)): Questions and answers right in the issues and merge requests of your GitLab — your own installation or gitlab.com, either way.
- [Google Drive — an integration for Buff](https://buff.systems/en/marketplace/google-drive) ([md](https://buff.systems/en/marketplace/google-drive.md)): Google Docs, Sheets and Slides as context for answers, and questions right in comments. The research report comes back as a document in the same folder.
- [Jira — an integration for Buff](https://buff.systems/en/marketplace/jira) ([md](https://buff.systems/en/marketplace/jira.md)): Tasks, questions and answers right in Jira Data Center and self-hosted Server tickets — without leaving the tracker your team already works in.
- [Jira Cloud — an integration for Buff](https://buff.systems/en/marketplace/jira-cloud) ([md](https://buff.systems/en/marketplace/jira-cloud.md)): Tasks, questions and answers right in Jira Cloud tickets — without leaving the tracker your team already works in.
- [Notion — an integration for Buff](https://buff.systems/en/marketplace/notion) ([md](https://buff.systems/en/marketplace/notion.md)): Notion pages and databases as context for answers — and questions right in the page discussion. The research report comes back as a page.
- [Redmine — an integration for Buff](https://buff.systems/en/marketplace/redmine) ([md](https://buff.systems/en/marketplace/redmine.md)): Questions and answers right in Redmine issues — in the tracker you already have, which is not going anywhere.
- [Internet — an integration for Buff](https://buff.systems/en/marketplace/web) ([md](https://buff.systems/en/marketplace/web.md)): Search and read public pages from your perimeter, within the admin’s allow and block lists. DuckDuckGo without a key, your own SearXNG, Brave with a key.

## Documents

- [User agreement (public offer)](https://buff.systems/en/legal/terms) ([md](https://buff.systems/en/legal/terms.md)): Terms of use of the Buff Development service: registration, payment, rights to the results, liability.
- [Personal data processing policy](https://buff.systems/en/legal/privacy) ([md](https://buff.systems/en/legal/privacy.md)): Which personal data Buff Development processes, why, where it is stored and how to delete it.
- [Mobile app privacy](https://buff.systems/en/legal/mobile-privacy) ([md](https://buff.systems/en/legal/mobile-privacy.md)): What the Buff mobile app processes: what is stored on the phone, what the buff.systems gateway, Apple and Google see, and how to delete it all.
- [Payment and refund terms](https://buff.systems/en/legal/payment) ([md](https://buff.systems/en/legal/payment.md)): How the Buff Development balance is topped up, which documents you receive and how to get the unspent remainder back.

## Videos

- [Buff in two minutes — video](https://buff.systems/en/video/buff) ([md](https://buff.systems/en/video/buff.md)): What Buff is: autonomous development under human control, answers from documents and a knowledge base — in brief, with sound.
- [Development by task — video](https://buff.systems/en/video/development) ([md](https://buff.systems/en/video/development.md)): How a tracker task becomes a branch with tests: connecting a repository, the analyst’s questions, the sandbox, review, merge request.
- [Questions and the knowledge base — video](https://buff.systems/en/video/knowledge) ([md](https://buff.systems/en/video/knowledge.md)): “Ask” and the knowledge base: answers from company documents with sources — for any department.
- [Buff Code — video](https://buff.systems/en/video/buff-code) ([md](https://buff.systems/en/video/buff-code.md)): A terminal for engineers: the organisation’s models, references and knowledge base — from the command line.

## Documentation

- [Introduction](https://buff.systems/en/docs) ([md](https://buff.systems/en/docs.md)): What Buff is: one platform with three entry points — development, the knowledge space and Buff Code — and where each team should start.
- [Ask](https://buff.systems/en/docs/ask) ([md](https://buff.systems/en/docs/ask.md)): Questions about code or company documents, read-only: an answer with a link to the file, page or ticket.
- [Ask from a document or ticket](https://buff.systems/en/docs/ask-from-your-tools) ([md](https://buff.systems/en/docs/ask-from-your-tools.md)): How to address the AI agent in Notion, a Google Doc, Confluence, Figma or a tracker: forms of address, where the answer arrives, what the bot does not do.
- [Question or research?](https://buff.systems/en/docs/ask-vs-research) ([md](https://buff.systems/en/docs/ask-vs-research.md)): A quick answer with links, or a document checked by a second agent: attachments, delivery, export, time and cost.
- [How to ask a good question about documents](https://buff.systems/en/docs/asking-well) ([md](https://buff.systems/en/docs/asking-well.md)): Name the document, section and period; say what form the answer should take; attach a file; how to read an answer with a link, and what “not found” means.
- [Assistant](https://buff.systems/en/docs/assistant) ([md](https://buff.systems/en/docs/assistant.md)): A product chat assistant: on the site it explains what Buff can do, in the app it tells you what is happening with your tasks.
- [Audit log](https://buff.systems/en/docs/audit-log) ([md](https://buff.systems/en/docs/audit-log.md)): Who did what in the organisation, when and from where — refusals included. Viewing, filters, export and integrity checks.
- [Event catalogue](https://buff.systems/en/docs/audit-log/events) ([md](https://buff.systems/en/docs/audit-log/events.md)): All audit log events by category: the code, what is recorded, the operation class and the severity.
- [Export and integrity](https://buff.systems/en/docs/audit-log/export) ([md](https://buff.systems/en/docs/audit-log/export.md)): Exporting the log to CSV and JSON Lines by the current filter, the file format, and checking the hash chain with your own tools.
- [Audits](https://buff.systems/en/docs/audits) ([md](https://buff.systems/en/docs/audits.md)): Understanding the codebase “as is”.
- [Buff Code](https://buff.systems/en/docs/buff-code) ([md](https://buff.systems/en/docs/buff-code.md)): A development environment for engineers who write code themselves: a console and an app on your organisation’s models, knowledge and connections.
- [Commands](https://buff.systems/en/docs/buff-code/commands) ([md](https://buff.systems/en/docs/buff-code/commands.md)): Reference for the buff console and the commands inside Buff Code: context, modes, goal, side conversation, undo, Git, automations, workflows, extensions.
- [Developer gateway](https://buff.systems/en/docs/buff-code/gateway) ([md](https://buff.systems/en/docs/buff-code/gateway.md)): For the administrator: how to open Buff Code sign-in to the team through the company connector — configuration, certificate, who it admits, what is visible.
- [Installation](https://buff.systems/en/docs/buff-code/install) ([md](https://buff.systems/en/docs/buff-code/install.md)): The buff console with one command on Linux, macOS and Windows; the app as a package from the “Download” page. Signature check, updates and mass rollout.
- [Knowledge base](https://buff.systems/en/docs/buff-code/knowledge) ([md](https://buff.systems/en/docs/buff-code/knowledge.md)): How the model in Buff Code reads the organisation’s and project’s knowledge base, proposes a new entry, and why an entry appears only after you confirm it.
- [Models and usage](https://buff.systems/en/docs/buff-code/models) ([md](https://buff.systems/en/docs/buff-code/models.md)): Which model Buff Code gets, who chooses it, how usage is counted and where the organisation’s billing shows it — per developer device.
- [Own providers and local models](https://buff.systems/en/docs/buff-code/own-providers) ([md](https://buff.systems/en/docs/buff-code/own-providers.md)): Your own provider in Buff Code: OpenRouter, Anthropic, OpenAI, LiteLLM, Ollama, LM Studio. What goes to Buff and what stays on the machine.
- [Project repositories](https://buff.systems/en/docs/buff-code/repositories) ([md](https://buff.systems/en/docs/buff-code/repositories.md)): The model in Buff Code searches and reads the project’s code in Buff without a clone on the machine: file search, content search and reading on any branch.
- [Development sessions](https://buff.systems/en/docs/buff-code/sessions) ([md](https://buff.systems/en/docs/buff-code/sessions.md)): The record of a developer’s work with the model in Buff Code: who needs it, what it consists of, what is recorded and what is not, who sees it, where to look.
- [What exactly the agent did](https://buff.systems/en/docs/buff-code/sessions/action) ([md](https://buff.systems/en/docs/buff-code/sessions/action.md)): The action inspector in a development session: kinds of actions and what each shows, statuses, “Raw call and result”, the “Files” tab.
- [Ask about sessions](https://buff.systems/en/docs/buff-code/sessions/ask) ([md](https://buff.systems/en/docs/buff-code/sessions/ask.md)): Asking the model about development session records: three ways, examples by role, what the model gets, how to read the answer, who sees it, usage and log.
- [Audit log and Buff Code](https://buff.systems/en/docs/buff-code/sessions/audit) ([md](https://buff.systems/en/docs/buff-code/sessions/audit.md)): What around Buff Code goes into the audit log: device sign-in and revocation, viewing others’ sessions, exports, questions, knowledge — with severity.
- [Export](https://buff.systems/en/docs/buff-code/sessions/export) ([md](https://buff.systems/en/docs/buff-code/sessions/export.md)): Exporting a development session: Markdown for reading and JSON with all messages; what the file contains, an example, what is left out, how it is audited.
- [Find a session](https://buff.systems/en/docs/buff-code/sessions/list) ([md](https://buff.systems/en/docs/buff-code/sessions/list.md)): The development session list: filters by period, developer and project, “Total for the selection”, how a row reads, empty states, “Ask about the selection”.
- [Read a session](https://buff.systems/en/docs/buff-code/sessions/view) ([md](https://buff.systems/en/docs/buff-code/sessions/view.md)): An open development session: header and metrics, the session timeline with coloured marks, the feed of messages and actions, service calls, “Follow”, phones.
- [Sign-in and working context](https://buff.systems/en/docs/buff-code/sign-in) ([md](https://buff.systems/en/docs/buff-code/sign-in.md)): Buff Code’s first launch: the connector address and the sign-in code confirmed in the workspace; organisation, project, spaces; per-folder memory; devices.
- [Connection tools](https://buff.systems/en/docs/buff-code/tools) ([md](https://buff.systems/en/docs/buff-code/tools.md)): What the connector gives the model in Buff Code: trackers, documents, the web, your own MCP servers; why writing tools are included; where calls show.
- [If something does not work](https://buff.systems/en/docs/buff-code/troubleshooting) ([md](https://buff.systems/en/docs/buff-code/troubleshooting.md)): Buff Code, workspace and connector messages during installation, sign-in, context choice, model and tool calls: what they mean and what to do.
- [Working in Buff Code](https://buff.systems/en/docs/buff-code/work) ([md](https://buff.systems/en/docs/buff-code/work.md)): Everyday work in Buff Code: a session with the agent, changes and undo, plan and goal, side conversation, Git, automations, workflows, extensions.
- [Automations](https://buff.systems/en/docs/buff-code/work/automations) ([md](https://buff.systems/en/docs/buff-code/work/automations.md)): Scheduled tasks for the agent: schedules, run permissions, manual runs, pause, history. A service on the machine runs them — even with the window closed.
- [Changes and undo](https://buff.systems/en/docs/buff-code/work/changes) ([md](https://buff.systems/en/docs/buff-code/work/changes.md)): What the agent changed in a turn and how to take it back: the summary under the answer, the diff, a safe rewind that checks for other edits, the file tree.
- [Extensions: MCP, skills, hooks](https://buff.systems/en/docs/buff-code/work/extensions) ([md](https://buff.systems/en/docs/buff-code/work/extensions.md)): Your own MCP servers, skills, commands, subagents, AGENTS.md memory and hooks — from the window and console settings. Trust in project hooks and commands.
- [Git in the window](https://buff.systems/en/docs/buff-code/work/git) ([md](https://buff.systems/en/docs/buff-code/work/git.md)): The Git window in Buff Code: what changed, a commit with a message from the agent, push, branches, history. The branch chip shows the state and opens it.
- [Plan, to-do list and goal](https://buff.systems/en/docs/buff-code/work/plan-goal) ([md](https://buff.systems/en/docs/buff-code/work/plan-goal.md)): A large task in Buff Code: a plan with approval, the agent’s to-do list and a /goal — the agent takes turns until a check confirms the result.
- [Session: input field, modes, questions](https://buff.systems/en/docs/buff-code/work/session) ([md](https://buff.systems/en/docs/buff-code/work/session.md)): Talking to the agent: the input field, permission modes, permission requests with an edit preview, the agent’s questions, attachments, background work, usage.
- [Settings and first launch](https://buff.systems/en/docs/buff-code/work/settings) ([md](https://buff.systems/en/docs/buff-code/work/settings.md)): The introduction on Buff Code’s first launch, language and theme, font size, tabs, keyboard shortcuts, proxy and the organisation certificate, notifications.
- [Side conversation](https://buff.systems/en/docs/buff-code/work/side) ([md](https://buff.systems/en/docs/buff-code/work/side.md)): A side conversation: ask something along the way without derailing the main task. It sees the main session, which does not see it; selections go as quotes.
- [The window and the session list](https://buff.systems/en/docs/buff-code/work/window) ([md](https://buff.systems/en/docs/buff-code/work/window.md)): How the Buff Code window is laid out: Home, the session column with pinning, groups and archive, the session state in a word, search by title and conversation.
- [Workflows](https://buff.systems/en/docs/buff-code/work/workflows) ([md](https://buff.systems/en/docs/buff-code/work/workflows.md)): Workflows: subagents work in phases with checks and a result. How to ask the agent, follow a run, save it and run it again with arguments.
- [What’s new](https://buff.systems/en/docs/changelog) ([md](https://buff.systems/en/docs/changelog.md)): A history of notable product changes.
- [Core concepts](https://buff.systems/en/docs/concepts) ([md](https://buff.systems/en/docs/concepts.md)): Organisation, project and space, repository and knowledge sources, task, subtasks, review.
- [Connector](https://buff.systems/en/docs/connector) ([md](https://buff.systems/en/docs/connector.md)): An agent in your network: a git bridge and an integration host. Tokens, keys and network access stay with you.
- [Setup through the terminal](https://buff.systems/en/docs/connector/cli-setup) ([md](https://buff.systems/en/docs/connector/cli-setup.md)): The wizard and the full command reference: the same as on the local page, but scriptable.
- [Custom MCP servers](https://buff.systems/en/docs/connector/custom-mcp) ([md](https://buff.systems/en/docs/connector/custom-mcp.md)): An MCP server from an archive, a GitHub repository or by address: what will run, your consent, and only read-only tools — as you mark them.
- [Files on disk](https://buff.systems/en/docs/connector/files) ([md](https://buff.systems/en/docs/connector/files.md)): Server folders and SMB network folders as context: Word, Excel, PowerPoint (2007+ and 97–2003), PDF and text — the glob, grep and read tools; read-only.
- [Google Drive](https://buff.systems/en/docs/connector/google-drive) ([md](https://buff.systems/en/docs/connector/google-drive.md)): Google documents, spreadsheets and presentations as context: reading, questions in comments, the report as a document, scope, sign-in options.
- [Installation](https://buff.systems/en/docs/connector/install) ([md](https://buff.systems/en/docs/connector/install.md)): The binary or the image, signature check, the privileges integrations need and the environment they run in.
- [Isolation and access boundaries](https://buff.systems/en/docs/connector/isolation) ([md](https://buff.systems/en/docs/connector/isolation.md)): What an integration can do, what it cannot, and what ensures it: the OS user, directories, addresses, credentials.
- [Jira](https://buff.systems/en/docs/connector/jira) ([md](https://buff.systems/en/docs/connector/jira.md)): Data Center, Server and Cloud: two integrations, their access, webhooks and specifics.
- [Knowledge sources](https://buff.systems/en/docs/connector/knowledge) ([md](https://buff.systems/en/docs/connector/knowledge.md)): Confluence, Figma, Notion and Google Drive as context for answers: read tools, requests on a page and on a mock-up, scope, parameters instead of pictures.
- [Management and removal](https://buff.systems/en/docs/connector/manage) ([md](https://buff.systems/en/docs/connector/manage.md)): Status, connectivity check, log, version updates, turning off, revocation and removal.
- [Catalogue and integration installation](https://buff.systems/en/docs/connector/marketplace) ([md](https://buff.systems/en/docs/connector/marketplace.md)): What is visible before installation, how the signature is checked, how versions are chosen and what revocation means.
- [Notion](https://buff.systems/en/docs/connector/notion) ([md](https://buff.systems/en/docs/connector/notion.md)): Notion pages and databases as context for answers: reading, questions in comments, the research report as a page, scope, webhook and polling.
- [Tools and the model](https://buff.systems/en/docs/connector/tools) ([md](https://buff.systems/en/docs/connector/tools.md)): How an integration’s tools reach the model, why writing ones never do and where this is visible.
- [Tracker integrations](https://buff.systems/en/docs/connector/trackers) ([md](https://buff.systems/en/docs/connector/trackers.md)): How the team works with the bot in its own tracker: requests, commands, visibility scope, the pull request branch, events.
- [The web for the model](https://buff.systems/en/docs/connector/web) ([md](https://buff.systems/en/docs/connector/web.md)): Searching and reading public pages from inside your perimeter: engines, allow and block lists, content types, stop words — and what cannot be configured.
- [Local setup page](https://buff.systems/en/docs/connector/web-setup) ([md](https://buff.systems/en/docs/connector/web-setup.md)): The six sections of the agent’s page: overview, connection, repositories, catalogue, integrations, your own MCP.
- [Config by hand (YAML)](https://buff.systems/en/docs/connector/yaml) ([md](https://buff.systems/en/docs/connector/yaml.md)): The full reference of the settings file: providers, the event receiver and integration connections.
- [What a question costs](https://buff.systems/en/docs/cost-of-a-question) ([md](https://buff.systems/en/docs/cost-of-a-question.md)): What makes up the price of a question and a research, where to see it, tokens in plain words, the three kinds of work in a plan, and adding people for free.
- [FAQ and troubleshooting](https://buff.systems/en/docs/faq) ([md](https://buff.systems/en/docs/faq.md)): Frequently asked questions and what to do if something goes wrong.
- [What to ask your administrator for](https://buff.systems/en/docs/for-admin) ([md](https://buff.systems/en/docs/for-admin.md)): A checklist for IT: the connector, the document connection, the space as the workplace, sections and folders, the connection test; systems not in the catalogue.
- [Glossary](https://buff.systems/en/docs/glossary) ([md](https://buff.systems/en/docs/glossary.md)): The product’s terms in one list.
- [Interface and usability](https://buff.systems/en/docs/interface) ([md](https://buff.systems/en/docs/interface.md)): The application shell: sidebar, header, themes, mobile version.
- [Knowledge base](https://buff.systems/en/docs/knowledge) ([md](https://buff.systems/en/docs/knowledge.md)): A shared knowledge store for people and AI: working rules, project facts and environment pitfalls. It reaches the model at every stage.
- [AI entries](https://buff.systems/en/docs/knowledge/ai-entries) ([md](https://buff.systems/en/docs/knowledge/ai-entries.md)): What the model writes itself, what it never writes, how to tell its entries from yours, and what it cannot touch.
- [Archive](https://buff.systems/en/docs/knowledge/archive) ([md](https://buff.systems/en/docs/knowledge/archive.md)): The knowledge base has no deletion: an entry goes to the archive with a reason, stays visible to readers and comes back with one click.
- [Entry](https://buff.systems/en/docs/knowledge/entry) ([md](https://buff.systems/en/docs/knowledge/entry.md)): What a piece of knowledge consists of: title, one-line description, type, scope, body and two flags. How to write it so the model uses it.
- [Passes after finished work](https://buff.systems/en/docs/knowledge/passes) ([md](https://buff.systems/en/docs/knowledge/passes.md)): When the AI reads finished work and adds to the base, what it does along the way, and how to turn this on, off or run it by hand.
- [Permissions](https://buff.systems/en/docs/knowledge/permissions) ([md](https://buff.systems/en/docs/knowledge/permissions.md)): Who sees the knowledge base, who changes it, and how to grant a member the permission.
- [How it reaches the model](https://buff.systems/en/docs/knowledge/prompt) ([md](https://buff.systems/en/docs/knowledge/prompt.md)): What the model gets in every task, what it opens when needed, and what the “show to the model upfront” flag costs.
- [Recipes](https://buff.systems/en/docs/knowledge/recipes) ([md](https://buff.systems/en/docs/knowledge/recipes.md)): Where to start a knowledge base, what to write for a legacy project, what never to write, and how to tell an entry is bad.
- [Organisation, project, task](https://buff.systems/en/docs/knowledge/scopes) ([md](https://buff.systems/en/docs/knowledge/scopes.md)): Knowledge of the whole organisation, one project or one task: what goes where, who sees it, and what happens to a task’s entries when it closes.
- [Entry types](https://buff.systems/en/docs/knowledge/types) ([md](https://buff.systems/en/docs/knowledge/types.md)): Rule, fact, pitfall: three kinds of knowledge, told apart by what each one changes for whoever reads it.
- [Mobile app](https://buff.systems/en/docs/mobile) ([md](https://buff.systems/en/docs/mobile.md)): Buff on your phone: tasks, review, answers, research and Buff Code sessions with notifications. For buff.systems, Buff Community, Enterprise and Buff Code.
- [Several installations](https://buff.systems/en/docs/mobile/installs) ([md](https://buff.systems/en/docs/mobile/installs.md)): How the app holds several installations at once, what their statuses mean, and what happens when an installation or the network is unavailable.
- [If your phone is lost](https://buff.systems/en/docs/mobile/lost-phone) ([md](https://buff.systems/en/docs/mobile/lost-phone.md)): How to disconnect a lost or stolen phone from the workspace, Buff Code and your company’s installation, and what happens to the data on it.
- [Notifications](https://buff.systems/en/docs/mobile/notifications) ([md](https://buff.systems/en/docs/mobile/notifications.md)): Which notifications reach the phone, how to choose types, what Apple and Google see, and what if push is off or buff.systems is unreachable.
- [Pairing with Buff Code](https://buff.systems/en/docs/mobile/pair-buff-code) ([md](https://buff.systems/en/docs/mobile/pair-buff-code.md)): How to pair a phone with Buff Code on your machine: in the window and in the console, with or without Buff sign-in, the Buff Code service, what the phone shows.
- [Pairing with the workspace](https://buff.systems/en/docs/mobile/pair-cabinet) ([md](https://buff.systems/en/docs/mobile/pair-cabinet.md)): Pairing a phone with an organisation on buff.systems or a Buff Community or Enterprise installation: QR or link and code, code check, what the phone gets.
- [Access policy](https://buff.systems/en/docs/mobile/policy) ([md](https://buff.systems/en/docs/mobile/policy.md)): Who can pair phones: a ban in an organisation on buff.systems, the “Mobile app” section of the admin panel, disconnecting phones, push and the log.
- [What buff.systems sees](https://buff.systems/en/docs/mobile/trust) ([md](https://buff.systems/en/docs/mobile/trust.md)): The app’s trust model in plain words: end-to-end encryption, what passes through the buff.systems gateway, Apple and Google, what is stored on the phone.
- [Buff without a repository: where to start](https://buff.systems/en/docs/no-code) ([md](https://buff.systems/en/docs/no-code.md)): The track for a department without code: account and organisation, a space, your documents, the first question, research and the first knowledge entry.
- [Notifications](https://buff.systems/en/docs/notifications) ([md](https://buff.systems/en/docs/notifications.md)): The event centre and the bell.
- [Autonomous development](https://buff.systems/en/docs/pipeline) ([md](https://buff.systems/en/docs/pipeline.md)): How a task turns into code.
- [Decomposition and atoms](https://buff.systems/en/docs/pipeline/decomposition) ([md](https://buff.systems/en/docs/pipeline/decomposition.md)): Splitting a task into independent subtasks.
- [Execution scheme](https://buff.systems/en/docs/pipeline/execution-scheme) ([md](https://buff.systems/en/docs/pipeline/execution-scheme.md)): The graph of a task’s atoms and execution waves.
- [Task lifecycle](https://buff.systems/en/docs/pipeline/lifecycle) ([md](https://buff.systems/en/docs/pipeline/lifecycle.md)): Six stages from request to merge.
- [Metrics and tokens](https://buff.systems/en/docs/pipeline/metrics) ([md](https://buff.systems/en/docs/pipeline/metrics.md)): Model usage and the amount of work for every run.
- [Run control](https://buff.systems/en/docs/pipeline/run-control) ([md](https://buff.systems/en/docs/pipeline/run-control.md)): Stopping, resuming and closing a task.
- [Quick start](https://buff.systems/en/docs/quickstart) ([md](https://buff.systems/en/docs/quickstart.md)): Two tracks: with a repository — up to the first task and pull request; without code — up to the first question about your department’s documents.
- [Connecting a repository](https://buff.systems/en/docs/quickstart/add-repository) ([md](https://buff.systems/en/docs/quickstart/add-repository.md)): Importing an external git repository as a mirror.
- [Audits](https://buff.systems/en/docs/quickstart/audits) ([md](https://buff.systems/en/docs/quickstart/audits.md)): Understanding the codebase before development.
- [Development project](https://buff.systems/en/docs/quickstart/dev-project) ([md](https://buff.systems/en/docs/quickstart/dev-project.md)): Assembling a project from source repositories.
- [Preparing development tools](https://buff.systems/en/docs/quickstart/devprep) ([md](https://buff.systems/en/docs/quickstart/devprep.md)): Development tools: the build and the tests as the project’s baseline.
- [Your first task](https://buff.systems/en/docs/quickstart/first-task) ([md](https://buff.systems/en/docs/quickstart/first-task.md)): The end-to-end path from a draft to a pull request.
- [Organisations](https://buff.systems/en/docs/quickstart/organizations) ([md](https://buff.systems/en/docs/quickstart/organizations.md)): Choosing, creating and switching organisations.
- [Registration and sign-in](https://buff.systems/en/docs/quickstart/registration) ([md](https://buff.systems/en/docs/quickstart/registration.md)): Account, sign-in with an email code (2FA), sign-in through corporate SSO, password recovery.
- [A space without code](https://buff.systems/en/docs/quickstart/space) ([md](https://buff.systems/en/docs/quickstart/space.md)): A workspace for teams without a repository: questions, research and a knowledge base over the team’s documents — Notion, Confluence, Google Drive, Figma, files.
- [Dedicated capacity](https://buff.systems/en/docs/rental) ([md](https://buff.systems/en/docs/rental.md)): A separate machine for your organisation: modes, preparation, shutdown and the balance reserve.
- [Repositories and sync](https://buff.systems/en/docs/repositories) ([md](https://buff.systems/en/docs/repositories.md)): The state of the mirrors relative to upstream, and syncing.
- [Deep research](https://buff.systems/en/docs/research) ([md](https://buff.systems/en/docs/research.md)): Two agents prepare a verified document from code or company documents: the analyst writes, the reviewer checks every claim against the sources.
- [Review and publishing](https://buff.systems/en/docs/review) ([md](https://buff.systems/en/docs/review.md)): Checking the changes and opening a pull request.
- [Changes](https://buff.systems/en/docs/review/changes) ([md](https://buff.systems/en/docs/review/changes.md)): A task’s diffs, grouped by repository.
- [Review decision](https://buff.systems/en/docs/review/decision) ([md](https://buff.systems/en/docs/review/decision.md)): Approve or send back for rework.
- [Review findings](https://buff.systems/en/docs/review/findings) ([md](https://buff.systems/en/docs/review/findings.md)): Review comments from the model and from you.
- [Publishing upstream](https://buff.systems/en/docs/review/publish) ([md](https://buff.systems/en/docs/review/publish.md)): Opening a pull request / merge request in the source repository.
- [Recipes by role](https://buff.systems/en/docs/roles) ([md](https://buff.systems/en/docs/roles.md)): What to connect, what to ask, what to put in the knowledge base and which role to grant — for eight departments without code.
- [Security and privacy](https://buff.systems/en/docs/security) ([md](https://buff.systems/en/docs/security.md)): Isolation, access, publishing, and what integrations in your network add.
- [Editions](https://buff.systems/en/docs/self-hosted) ([md](https://buff.systems/en/docs/self-hosted.md)): Three ways to get Buff: the buff.systems cloud, the free Community Edition on your own machine, and Enterprise on-premise under contract. How they differ.
- [Installing Community Edition](https://buff.systems/en/docs/self-hosted/community) ([md](https://buff.systems/en/docs/self-hosted/community.md)): A step-by-step guide to the free edition of Buff on your own machine: one-command install, first sign-in, licence, connector, updates.
- [Enterprise on-premise edition](https://buff.systems/en/docs/self-hosted/enterprise) ([md](https://buff.systems/en/docs/self-hosted/enterprise.md)): The full edition of Buff on your infrastructure: what it includes, a certificate licence, SSO, air-gapped installs, support. How to get it.
- [Community Edition licence](https://buff.systems/en/docs/self-hosted/license) ([md](https://buff.systems/en/docs/self-hosted/license.md)): The terms of the free edition: internal use by one organisation, what is forbidden, and what is sent when the licence is checked.
- [Settings](https://buff.systems/en/docs/settings) ([md](https://buff.systems/en/docs/settings.md)): Profile, security, members, repository tokens, billing, the audit log and single sign-on.
- [Single sign-on (SSO)](https://buff.systems/en/docs/sso) ([md](https://buff.systems/en/docs/sso.md)): Employees sign in through the corporate provider (Keycloak, AD FS, Entra ID and others) over OIDC or SAML 2.0; accounts are created on first sign-in.
- [Company domains](https://buff.systems/en/docs/sso/domains) ([md](https://buff.systems/en/docs/sso/domains.md)): A verified email domain routes an employee to your provider by work email and lets existing accounts be linked. Verification is a DNS TXT record.
- [Members and “SSO only” mode](https://buff.systems/en/docs/sso/policy) ([md](https://buff.systems/en/docs/sso/policy.md)): Accounts created on first sign-in, the default role, linking existing accounts, no password sign-in for members, and the owner’s fallback sign-in.
- [Setting up single sign-on](https://buff.systems/en/docs/sso/setup) ([md](https://buff.systems/en/docs/sso/setup.md)): The “Single sign-on” section: OIDC or SAML 2.0, values for the provider, SP metadata, a test sign-in. Examples for Keycloak, AD FS and Entra ID.
- [Troubleshooting](https://buff.systems/en/docs/sso/troubleshooting) ([md](https://buff.systems/en/docs/sso/troubleshooting.md)): What single sign-on error messages mean and how to fix them: provider setup, redirect URI, signature, certificate, clock, email.
- [Plans](https://buff.systems/en/docs/tariffs) ([md](https://buff.systems/en/docs/tariffs.md)): How the plans differ from each other, how to change plan and what makes up the price.
- [Setting tasks](https://buff.systems/en/docs/tasks) ([md](https://buff.systems/en/docs/tasks.md)): How to set a task so that it gets done right.
- [Attachments](https://buff.systems/en/docs/tasks/attachments) ([md](https://buff.systems/en/docs/tasks/attachments.md)): Files for a task, a clarification, a finding and conversations.
- [Clarifications](https://buff.systems/en/docs/tasks/clarifications) ([md](https://buff.systems/en/docs/tasks/clarifications.md)): Answering the analyst’s clarifying questions.
- [Drafts](https://buff.systems/en/docs/tasks/drafts) ([md](https://buff.systems/en/docs/tasks/drafts.md)): Creating, editing and sending a task for refinement.
- [Approving the formulation](https://buff.systems/en/docs/tasks/gate) ([md](https://buff.systems/en/docs/tasks/gate.md)): The decision on a finished formulation: approve, rework, reject.
- [Project screen](https://buff.systems/en/docs/tasks/project-home) ([md](https://buff.systems/en/docs/tasks/project-home.md)): The project state, what awaits your decision, and the task list.
- [How to phrase a task](https://buff.systems/en/docs/tasks/writing-good-tasks) ([md](https://buff.systems/en/docs/tasks/writing-good-tasks.md)): Good and bad task statements, and a short cheat sheet.
- [Members and permissions](https://buff.systems/en/docs/teams) ([md](https://buff.systems/en/docs/teams.md)): Who can do what in the organisation: the owner, the Contributor and Maintainer roles, scopes and fine-grained permissions.
- [Managing members](https://buff.systems/en/docs/teams/manage) ([md](https://buff.systems/en/docs/teams/manage.md)): Inviting, setting permissions, changing a role, making someone an owner, removing — and how quickly changes take effect.
- [Permissions reference](https://buff.systems/en/docs/teams/permissions) ([md](https://buff.systems/en/docs/teams/permissions.md)): Every atomic permission: what it allows, where it shows in the interface, and what the role gives by default.
- [Scenarios for teams](https://buff.systems/en/docs/teams/recipes) ([md](https://buff.systems/en/docs/teams/recipes.md)): Ready-made permission setups: a small team, several projects, contractors, reviewers, customers, observers.
- [Roles](https://buff.systems/en/docs/teams/roles) ([md](https://buff.systems/en/docs/teams/roles.md)): Owner, Maintainer and Contributor: what each can do and when to choose which role.
- [Scopes](https://buff.systems/en/docs/teams/scopes) ([md](https://buff.systems/en/docs/teams/scopes.md)): The whole organisation, a development project or a repository: where a member’s role applies and what happens where scopes overlap.
- [What a member sees](https://buff.systems/en/docs/teams/what-members-see) ([md](https://buff.systems/en/docs/teams/what-members-see.md)): How the interface changes with permissions: what is hidden, what is shown read-only, and which hints appear.
- [Tests](https://buff.systems/en/docs/tests) ([md](https://buff.systems/en/docs/tests.md)): How a project sees its tests and what the “Test settings” section shows.
- [Failing tests and the task decision](https://buff.systems/en/docs/tests/per-task) ([md](https://buff.systems/en/docs/tests/per-task.md)): What happens to tests that were failing before the task started, and how you decide their fate.
- [What data we collect](https://buff.systems/en/docs/usage-data) ([md](https://buff.systems/en/docs/usage-data.md)): Exactly what Buff records about how the product is used, what it does not record, and where to see it.