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

# Claude Code and Bluesky with Bolta

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

Use Claude Code with Bolta's Bluesky content workflow.

## Summary

Turn your repo's release notes into social drafts, from the terminal This page focuses on Bluesky.

## Who this is for

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

## Core capabilities

- Turn the newest CHANGELOG.md entry into a LinkedIn and an X draft
- Draft launch posts from a README section before you push a release
- Summarise what a merged pull request changed in plain words for customers
- Draft a week of build-in-public posts in your own voice between coding sessions
- Review what Bolta has queued without leaving the terminal
- Set up a weekly routine that drafts posts from your product updates for your review
- 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.
- Claude Code 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 Claude Code reaches Bluesky

Claude Code 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 Claude Code or in the Bolta app.

## Where approval sits

Requests that arrive from Claude Code 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/claude-code](https://bolta.ai/integrations/claude-code)
- [Related page: /integrations](https://bolta.ai/integrations)
- [Bolta pricing](https://bolta.ai/pricing)
