BeeTool.Dev - Essential Tools for developers

Stories.Tool Tabs VaultPersonal Documents
BeeTool.Dev

Essential tools, knowledge, and playgrounds for developers.

Explore

  • Stories
  • Personal Documents
  • Features
  • Beetool for Mac
  • Algorithms Playground

Tool Tabs

  • JSON Compare
  • SQL Formatter
  • Text Diff
  • All tools →

Learn

  • Sorting algorithms
  • Searching algorithms
  • Algorithm Race Mode
© 2024 – 2026 BeeTool.Dev
AboutContactPrivacy policyTerms
ContentsDocumentation home

Get started

  • What is Beetool
  • Install & first launch
  • Projects, workspaces & navigation
  • Keyboard shortcuts

AI

  • AI assistant
  • AI providers & models
  • Knowledge & project context
  • Agent teams
  • AI usage & run ledger
  • MCP server

Code & Git

  • Code editor
  • Run, test & debug
  • Terminal
  • Git
  • Merge requests
  • AI review & rule sets

Work

  • Beework tasks & board
  • Products
  • Docs & AI Docs

Tools

  • Database
  • Beequest — HTTP client
  • SSH, SFTP & Vault
  • Processes & network
  • Text files

Reference

  • Settings
  • Privacy & data

Get started

What is Beetool

One Mac app for the whole development flow — Git, code, review, terminal, database, API client and docs — with AI in every step.

Beetool's code workspace with the terminal and the AI panel

Beetool replaces the stack of windows you keep open while you work: the git client, the editor, the terminal, the database GUI, the HTTP client, the SSH client and the AI chat. They share one window, one project and one AI that knows that project.

#How it is organised

LevelWhat it isExamples
ProjectAny folder, usually a git repositoryacme-backend
WorkspaceFour per projectAI ⌘1, Code ⌘2, Docs ⌘3, Git ⌘4
ToolStandalone tabs next to projectsDatabase, Beequest, SSH, Terminal, Processes
ProductRepositories that belong togetherAPI + web app + infrastructure
Beework taskOne change across several repositoriesA ticket with a branch in each repo

#AI, your way

  • Your accounts. Beetool drives the coding CLIs you already use — Claude Code, Codex and Grok Build — with your sign-in or API key. See AI providers.
  • You approve every change. The assistant's edits arrive as diffs; agents work in private worktrees; AI review findings stay drafts until you submit them.
  • Local context. Knowledge documents, the repo map, product notes and rule sets are on your Mac and go into each AI run. See Knowledge & context.

#Where to go next

  1. Install Beetool and open your first project.
  2. Learn the workspaces and the command palette.
  3. Connect an AI provider and ask the assistant something about your code.
Next Install & first launch

On this page

  • How it is organised
  • AI, your way
  • Where to go next