---
title: "VS Code and Threads with Bolta"
description: "Use VS Code with Bolta's Threads content workflow."
canonical_url: "https://bolta.ai/integrations/vscode/threads"
markdown_url: "https://bolta.ai/integrations/vscode/threads.md"
last_updated: "2026-11-21"
content_type: "integration"
publisher: "Bolta"
---

# VS Code and Threads with Bolta

Source: https://bolta.ai/integrations/vscode/threads
Last updated: 2026-11-21

Use VS Code with Bolta's Threads content workflow.

## Summary

Draft and queue social posts from VS Code's AI chat This page focuses on Threads.

## Who this is for

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

## Core capabilities

- Turn a release or changelog entry into a LinkedIn or X draft
- Explain a technical change to customers in plain words
- Draft a week of developer-focused posts in your brand voice
- Review and approve what Bolta has queued without leaving the editor
- Check how recent posts performed before you plan the next one
- Supported content concepts: text posts, image posts, polls.

## Limitations and boundaries

- Current Threads support depends on its API and the connected account's permissions.
- Confirm the integration's current authentication and scope requirements before deployment.
- VS Code must be connected to a Bolta workspace that already has a Threads 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 VS Code reaches Threads

VS Code does not talk to Threads directly. It calls Bolta, and Bolta holds the connected Threads 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 VS Code or in the Bolta app.

## Where approval sits

Requests that arrive from VS Code are subject to the same workspace approval settings as anything else. A drafted Threads 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/vscode](https://bolta.ai/integrations/vscode)
- [Related page: /integrations](https://bolta.ai/integrations)
- [Bolta pricing](https://bolta.ai/pricing)
