---
title: "Muse and Bluesky with Bolta"
description: "Use Muse with Bolta's Bluesky content workflow."
canonical_url: "https://bolta.ai/integrations/muse/bluesky"
markdown_url: "https://bolta.ai/integrations/muse/bluesky.md"
last_updated: "2026-11-21"
content_type: "integration"
publisher: "Bolta"
---

# Muse and Bluesky with Bolta

Source: https://bolta.ai/integrations/muse/bluesky
Last updated: 2026-11-21

Use Muse with Bolta's Bluesky content workflow.

## Summary

Queue social posts from Muse Code, Meta's terminal agent This page focuses on Bluesky.

## Who this is for

- Teams connecting Muse and Bluesky
- Muse users who publish to Bluesky
- Operators automating a review-first publishing workflow

## Core capabilities

- Turn a release note or changelog entry into a LinkedIn or X draft without leaving the terminal
- Have Muse Code read a README or docs page in your repo and draft posts that explain it
- Draft a week of posts in your brand voice, then review them in Bolta rather than in the shell
- Ask what is waiting for approval and have each draft read back before you decide
- Pull recent post results into the terminal before you plan the next batch
- Set up a weekly routine that drafts posts for your review, then close the terminal
- Supported content concepts: posts, threads, quote posts.

## Limitations and boundaries

- Current Bluesky support depends on its API and the connected account's permissions.
- Confirm the integration's current authentication and scope requirements before deployment.
- Muse must be connected to a Bolta workspace that already has a Bluesky account linked; the integration cannot create that connection on its own.
- Generated content can be incorrect and should be reviewed before publication.
- Availability depends on the current Bolta plan, connected network, account permissions, and integration coverage.
- Current prices and plan limits must be verified on the Bolta pricing page.

## How Muse reaches Bluesky

Muse does not talk to Bluesky directly. It calls Bolta, and Bolta holds the connected Bluesky account, its tokens, and its publishing rules. That means one connection is maintained in one place rather than per tool, and the same draft, review, schedule, and publish states apply whether the work started in Muse or in the Bolta app.

## Where approval sits

Requests that arrive from Muse are subject to the same workspace approval settings as anything else. A drafted Bluesky post lands in the review queue rather than going straight out, unless the workspace has explicitly been configured otherwise. Connecting a tool widens who can create work; it does not widen who can publish it.

## Relevant links

- [Related page: /integrations/muse](https://bolta.ai/integrations/muse)
- [Related page: /integrations](https://bolta.ai/integrations)
- [Bolta pricing](https://bolta.ai/pricing)
