Buffaly Logo
Browse docs Menu

Start here

Docs home Install Buffaly Install on Windows Install on Linux Install on Mac Quickstart How-to library

Learn Buffaly

What Buffaly is User guide Core concepts Coming from other agents Memory and skills

Build and extend

Add a prompt skill Add a ProtoScript skill Add a C# DLL tool Add a model provider Skills, services, and tools ProtoScript services

Operate

Sessions and long-running work Session anatomy Plan, Scratch, and Tasks Session artifacts Session timeline Compaction

Reference

Ontology and ProtoScript Providers and authentication Web modules and UI Diagnostics & recovery Safety rules Secrets handling SmartPatch
Starter how-to

How to connect your first tool to Buffaly

Choose the first tool by the work you want Buffaly to help with, not by the longest setup checklist. One useful, verified connection is better than several half-configured integrations.

Choose based on your goal

Start withWhen your goal isFirst verification
GitHubRepositories, issues, pull requests, code context, and project memory.gh auth status and read-only repo view.
Google WorkspaceDocs, Sheets, Drive, Gmail drafts, Calendar, or workspace knowledge.Account appears, validates, and has refresh-token access.
Trusted device accessOpening a local Buffaly install from a phone or another trusted device.The correct instance loads and a known guide/action works.
CodexRepository inspection, source edits, validation, and commits.Small scoped edit validates and commits cleanly.

Keep the first pass small

  1. Pick one tool.
  2. Name one repository, account, document, device, or workflow.
  3. Ask Buffaly what information it needs.
  4. Run a read-only or harmless verification.
  5. Only then decide whether to remember aliases or enable write actions.

What “connected” should mean

A tool is not connected just because Buffaly knows its name. It should be observable and testable.

  • Buffaly can explain which tool or integration it will use.
  • Buffaly can perform a harmless read or status check.
  • Buffaly can identify which actions require approval.
  • You know where credentials or durable tokens are stored.
  • You can repeat the verification later.

After the first tool works

Ask Buffaly to remember the names and workflows you use, then ask for automation options that build on the verified connection.

Examples and next prompts

Choose the first tool by the work you actually want to do: GitHub for code and issues, Google Workspace for docs and sheets, Codex for repository edits, and trusted-device access when you need to use Buffaly away from the host machine.

Good first prompt

“Help me connect GitHub for one repository, verify read-only access, and remember the repository alias.”

After it works

Ask Buffaly to show what it can see, what actions are safe, and which write operations need confirmation.