Skip to main content

Welcome to Fibonacci

Fibonacci does two jobs:
  1. Runs workflows. Describe a task in plain English. Claude turns it into a workflow (a graph of tool calls and LLM steps), and a durable worker runs it across GitHub, Jira, Trello, Google, Slack, Discord, Notion and Zoom.
  2. Governs agents. Every tool call is checked against your organization’s rules before it runs, for Fibonacci’s own workflows and for agents it doesn’t run, such as Claude Code or any MCP client. A call is allowed, blocked, or held for a human to approve, and every decision is written to a tamper-evident audit log.
Get issue 23 from GitHub in the abc repo, find the key issues and make a fix.md, send it to xyz, set a one-on-one with xyz, and update the work in Trello.
That sentence is a complete workflow. Fibonacci reads the issue, has Claude write fix.md, emails it to xyz as an attachment, books a 1:1 with a Meet link, and moves the Trello card with a note. See how →

Quickstart

Up and running in five minutes

Connect your tools

GitHub, Jira, Trello, Google, Slack and more

Developer workflows

Issues, code, CI, tickets and boards

Governance

Rules, approvals, receipts and audit

Why Fibonacci?

The generator knows every tool, what it returns, and how people refer to things: a repository by its name, an issue as #23, a sheet by its link. It asks for what it can’t know (like someone’s email) as an input instead of guessing.
Read GitHub issues, files, commits, pull requests and CI checks; create, update, move and comment on Jira issues and Trello cards; send files, book meetings, and message people where they’ll see it. All tools →
Labels follow data through a workflow, so a rule can hold a Slack post because it mixes a confidential sheet with web content, not just because it’s a Slack post. Held steps pause the run and resume when approved.
A Claude Code hook and an MCP gateway apply the same rules to developers’ coding agents, with a kill switch per session. External agents →
Build workflows in Python with the SDK, or in YAML, and version them like any other code.

Quick example (SDK)

What’s new

The platform changed a lot since these docs were last updated. The changelog lists everything.

Getting help

Discord Community

Questions and discussion

API reference

Every REST endpoint