Busabase for Pi

Connect Pi to Busabase

Minimal, extensible terminal agent harness with native Agent Skills discovery and shell tools.

Paste this into Pi

Read https://busabase.com/SETUP_SKILL.md and set up Busabase for me. Follow it through to the end, then confirm the connection works.

Busabase

Agent Skill

Give your agent this one instruction

You end up with more than a connector: the busabase skill carries the whole approval-first workflow, the CLI, and the full API — available in every future session without re-pasting anything.

Asks first

Busabase Cloud or Personal Desktop — your call, before anything happens.

Connects

Signs you in and stores the credential itself. No API key to copy by hand.

Seeds a Base

Creates and fills your first Base, so the workspace is not an empty screen.

Installs the skills

busabase and busabase-app-creator become permanent, for every session after this.

For this agent

Pi discovers ~/.agents/skills and project .agents/skills. It intentionally has no built-in sandbox or permission system, so run setup only in a trusted repository and account.

Other ways in

This agent has no MCP client, so there is no connector to add. These routes work instead.

At a glance

Vendor: Earendil Works
How it connects: Plugin / Skill · busabase-cli · REST API
Transport: No MCP support
Authentication: None

Run this

npm exec -y --package busabase-cli@latest -- busabase-cli login --device-code

Pi has no built-in MCP client, so use the Skill path. Ask Pi: Read https://busabase.com/SETUP_SKILL.md and set up Busabase for me. Pi has bash access and discovers Agent Skills from ~/.agents/skills and project .agents/skills.

For a manual fallback:

npm exec -y --package busabase-cli@latest -- busabase-cli login --device-code
npx busabase-cli bases list

Code-driven integrations can use the REST API at /api/v1.

Known gotchas

Pi does not ship a built-in MCP client. Its official package catalog lists third-party MCP adapters, but this row does not turn community extensions into a native compatibility claim.

These stepsFrom official docsNo check date recorded

Written from this agent's own documentation. We have not re-run every step on a real machine, so check the linked docs if a command has changed.

Where these steps come from Official site

Let your agent do the setup

One instruction, reviewed access, and every change it makes afterwards arrives as a proposal you approve.

Browse every agent

Paste this into Pi

Read https://busabase.com/SETUP_SKILL.md and set up Busabase for me. Follow it through to the end, then confirm the connection works.

All agents

Busabase for Pi

Connect Pi to Busabase

Minimal, extensible terminal agent harness with native Agent Skills discovery and shell tools.

Paste this into Pi

Read https://busabase.com/SETUP_SKILL.md and set up Busabase for me. Follow it through to the end, then confirm the connection works.

Busabase

Agent Skill

Give your agent this one instruction

You end up with more than a connector: the busabase skill carries the whole approval-first workflow, the CLI, and the full API — available in every future session without re-pasting anything.

Asks first

Busabase Cloud or Personal Desktop — your call, before anything happens.

Connects

Signs you in and stores the credential itself. No API key to copy by hand.

Seeds a Base

Creates and fills your first Base, so the workspace is not an empty screen.

Installs the skills

busabase and busabase-app-creator become permanent, for every session after this.

For this agent

Pi discovers ~/.agents/skills and project .agents/skills. It intentionally has no built-in sandbox or permission system, so run setup only in a trusted repository and account.

Other ways in

This agent has no MCP client, so there is no connector to add. These routes work instead.

At a glance

Vendor: Earendil Works
How it connects: Plugin / Skill · busabase-cli · REST API
Transport: No MCP support
Authentication: None

Run this

npm exec -y --package busabase-cli@latest -- busabase-cli login --device-code

For a manual fallback:

npm exec -y --package busabase-cli@latest -- busabase-cli login --device-code
npx busabase-cli bases list

Code-driven integrations can use the REST API at /api/v1.

Known gotchas

Pi does not ship a built-in MCP client. Its official package catalog lists third-party MCP adapters, but this row does not turn community extensions into a native compatibility claim.

These stepsFrom official docsNo check date recorded

Written from this agent's own documentation. We have not re-run every step on a real machine, so check the linked docs if a command has changed.

Where these steps come from Official site

Let your agent do the setup

One instruction, reviewed access, and every change it makes afterwards arrives as a proposal you approve.

Browse every agent

Paste this into Pi

Read https://busabase.com/SETUP_SKILL.md and set up Busabase for me. Follow it through to the end, then confirm the connection works.

All agents

Busabase for Pi

Connect Pi to Busabase

Minimal, extensible terminal agent harness with native Agent Skills discovery and shell tools.

Paste this into Pi

Read https://busabase.com/SETUP_SKILL.md and set up Busabase for me. Follow it through to the end, then confirm the connection works.

Busabase

Agent Skill

Give your agent this one instruction

You end up with more than a connector: the busabase skill carries the whole approval-first workflow, the CLI, and the full API — available in every future session without re-pasting anything.

Asks first

Busabase Cloud or Personal Desktop — your call, before anything happens.

Connects

Signs you in and stores the credential itself. No API key to copy by hand.

Seeds a Base

Creates and fills your first Base, so the workspace is not an empty screen.

Installs the skills

busabase and busabase-app-creator become permanent, for every session after this.

For this agent

Pi discovers ~/.agents/skills and project .agents/skills. It intentionally has no built-in sandbox or permission system, so run setup only in a trusted repository and account.

Other ways in

This agent has no MCP client, so there is no connector to add. These routes work instead.

At a glance

Vendor: Earendil Works
How it connects: Plugin / Skill · busabase-cli · REST API
Transport: No MCP support
Authentication: None

Run this

npm exec -y --package busabase-cli@latest -- busabase-cli login --device-code

For a manual fallback:

npm exec -y --package busabase-cli@latest -- busabase-cli login --device-code
npx busabase-cli bases list

Code-driven integrations can use the REST API at /api/v1.

Known gotchas

Pi does not ship a built-in MCP client. Its official package catalog lists third-party MCP adapters, but this row does not turn community extensions into a native compatibility claim.

These stepsFrom official docsNo check date recorded

Written from this agent's own documentation. We have not re-run every step on a real machine, so check the linked docs if a command has changed.

Where these steps come from Official site

Let your agent do the setup

One instruction, reviewed access, and every change it makes afterwards arrives as a proposal you approve.

Browse every agent

Paste this into Pi

Read https://busabase.com/SETUP_SKILL.md and set up Busabase for me. Follow it through to the end, then confirm the connection works.