Sign in to Claude Code with the same account you use on claude.ai, update to version 2.1.275 or later, and it will now sync Claude AI skills and plugins to Claude Code terminal sessions automatically — every skill and plugin enabled on your claude.ai account appears in your terminal without any manual copying, and two settings let you switch the behaviour off if you would rather keep the two environments separate. That single change removes one of the most annoying gaps in the Claude ecosystem: until now, a skill you had set up in the claude.ai web app simply did not exist as far as your terminal was concerned, and you had to maintain two parallel setups to get consistent behaviour across both.
📺 Watch: Free Claude Code is Absolutely INSANE!
🔥 Get the Agent OS as a free bonus: AI Profit Boardroom members get the full Agent OS zip, prompt libraries, daily tutorials and weekly live coaching calls. → Get inside · Want AI SEO help 1-on-1? Book a free SEO strategy session →
The feature shipped in Claude Code version 2.1.275, released on 17 September 2026, according to the official Claude Code changelog published by Anthropic. The changelog entry reads: "Added syncing of the skills and plugins enabled on your claude.ai account to terminal sessions signed in with it; opt out with syncClaudeAiSkills: false or syncClaudeAiPlugins: false." This guide walks through what that means in practice, how to get the sync working, how to opt out, and why it matters if you are building automation workflows on top of Claude Code — the same category of workflow covered in the learn Claude Code guide on this site.
Sync Claude AI Skills And Plugins To Claude Code Terminal: What Changed In 2.1.275
Before version 2.1.275, skills and plugins lived in silos. A skill you enabled on your claude.ai account worked in the web and desktop apps, while your terminal sessions relied on whatever you had installed locally — project-level skill files, plugin marketplaces added by hand, and configuration that had to be repeated on every machine. If you worked across a laptop, a desktop and a remote session, keeping those environments consistent was entirely your job.
Version 2.1.275 closes that gap in one direction: terminal sessions signed in with your claude.ai account now pull down the skills and plugins enabled on that account. In plain terms, your account becomes the source of truth. Enable a skill once on claude.ai and it follows you into every terminal session that uses the same sign-in. The sync is on by default, which is the right call for most people — the whole point of a skill is that it is available when the task shows up, not just on the machine where you happened to install it.
It is worth noting this rollout had groundwork. The changelog for version 2.1.273, released on 15 September 2026, includes a fix for "skills synced from claude.ai staying available after organization disables Skills" — which tells you Anthropic was already wiring account-level skill sync into the terminal before announcing it as a headline feature, and that organisation-level controls are respected: if your org turns Skills off, the synced skills go away rather than lingering.
How To Get The Sync Working
There is no special setup command. The requirements are simply the right version and the right sign-in:
- Update Claude Code to 2.1.275 or later. You can check your installed version by running claude --version in your terminal. If you are behind, update through your normal install method. Given that 2.1.276 shipped on 18 September 2026 with a fix for a proxy-related regression in 2.1.275, going straight to the newest version is the sensible move.
- Sign in with your claude.ai account. The sync applies to "terminal sessions signed in with it" — meaning the claude.ai account whose skills and plugins you want. If you use separate accounts for web and terminal, the sync follows the account the terminal is signed in with.
- Check your skills and plugins are enabled on claude.ai. The sync mirrors what is enabled on the account, so anything you have toggled off in the web app will not appear in the terminal either.
Once those conditions are met, your account-level skills and plugins are available in terminal sessions alongside anything you have installed locally. Your existing project-level setup does not go anywhere — this is additive.
If you want to turn Claude Code and agent skills into an actual income system rather than a stack of experiments, check out the AI Profit Boardroom → get the full automation playbook here. Prefer to talk your setup through first? Book a free SEO strategy session and map out where AI fits in your business.
How To Opt Out: syncClaudeAiSkills And syncClaudeAiPlugins
Not everyone wants their web-app configuration bleeding into their terminal. Maybe your claude.ai account carries personal skills and your terminal is for client work, or you keep terminal environments deliberately minimal so behaviour is reproducible. Anthropic shipped the escape hatch on day one: per the 2.1.275 changelog, you opt out with the settings syncClaudeAiSkills: false and syncClaudeAiPlugins: false.
The two settings are independent, which is a thoughtful touch. You can sync skills but not plugins, or plugins but not skills:
- syncClaudeAiSkills: false — terminal sessions stop pulling skills from your claude.ai account; only locally installed skills remain.
- syncClaudeAiPlugins: false — the same, but for plugins.
If you manage plugins manually, the same release also added a more precise install command — the changelog lists "/plugin install with a --marketplace flag" for specifying which marketplace source a plugin comes from, which matters once you have more than one marketplace configured. And if you want to test how well a skill actually performs before you rely on it, the Claude Code plugin eval guide covers the evaluation tooling built for exactly that.
📺 Watch: Building AI Agent Operating Systems with Claude
Why Account-Level Sync Matters For AI Automation
The practical win is consistency across surfaces, and consistency is what makes automation dependable. A skill is a packaged set of instructions — a house style, a review checklist, a repeatable workflow — and its value collapses the moment it is available in one environment but missing in another, because you can no longer predict what your agent will do from a given prompt. With account sync, the skill set travels with your identity instead of your hardware.
That matters most in three situations. First, multi-machine work: the same skills on your laptop, your desktop and any machine you sign in from. Second, remote and cloud sessions — if you run Claude Code in the cloud, pairing this with the setup in the Claude Code fast mode for remote sessions guide means a fresh cloud session comes up already knowing your workflows. Third, team standardisation: because the 2.1.273 fix confirms organisation-level Skills controls are enforced, an org can manage what is available centrally rather than auditing every developer's local folder.
If you are building towards a full agent operating system — a structured set of skills, prompts and workflows your agents share — this is one more piece of plumbing you no longer maintain by hand. The Agent OS guide covers that structured approach, and the Goldie Bench write-up covers how the different AI brains you might drive it with compare in hands-on tests. For a worked example of Claude Code driving a real revenue workflow end to end, the Claude Code AI SEO guide is the closest companion piece to this one.
📺 Watch: The NEW Claude + Agent OS is Crazy Good!
What Else Landed In Claude Code 2.1.275
The sync feature headlines the release, but the 17 September 2026 changelog lists other changes worth knowing about:
- A send-now key. Pressing ctrl+enter (or ctrl+x then ctrl+s) interrupts the current turn and sends all queued messages at once, with sent and queued messages shown in grey until the model receives them.
- Gateway sign-in confirmation. When a Claude apps gateway names the signed-in account, you confirm it before the credential is saved, and /status shows which account is in use.
- Security fix for plugin logs. Plugin and marketplace messages no longer show passwords or tokens embedded in URLs.
- Queued-message fix for cloud sessions. Resumed cloud sessions no longer leave unanswered questions open after queued messages superseded them — relevant if you steer sessions remotely, as covered in the remote control session guide.
One caution: 2.1.275 also introduced a regression for people routing requests through a proxy or LLM gateway via ANTHROPIC_BASE_URL — every request failed with a 400 error naming an unrecognised input tag. Anthropic fixed it in 2.1.276 on 18 September 2026, so if you sit behind a gateway, update past 2.1.275 rather than to it.
Common Questions About The Skills And Plugins Sync
Does the sync cost anything extra?
The changelog describes it as a built-in behaviour of version 2.1.275, not a paid add-on. Your normal Claude plan limits still apply to usage. If cost is the concern, the free Claude Code guide covers the low-cost ways in.
Can I sync skills but manage plugins locally?
Yes — the opt-outs are separate settings. Set syncClaudeAiPlugins: false and leave skills syncing, or the reverse.
Does this replace project-level skills?
No. Account-synced skills arrive alongside whatever your projects define. If you are building a structured agent stack, the agentic OS with Claude Code guide shows how project-level and account-level pieces fit together.
The bottom line: update to the latest version, sign in with the account that holds your skills, and your terminal finally behaves like the rest of your Claude setup — one account, one skill set, every surface.
If you want a library of proven agent skills, prompts and daily tutorials instead of building everything from scratch, check out the AI Profit Boardroom → join 3,000+ AI operators inside. And if you want 1-on-1 help applying this to your own site, book a free SEO strategy session — it costs nothing and you leave with a plan.
