An Obsidian plugin that lets Claude Code directly operate on the current note, supporting one-click rewriting, splitting into entries, topic selection, and more.

https://t.co/7AYc76YF32 https://t.co/pK9v71NtCF

SIXIANGGUO/cc-note-ops

Source: https://github.com/SIXIANGGUO/cc-note-ops

CC Note Ops

Turn the current Obsidian note into a content workbench directly operable by Claude Code.

CC Note Ops is not just a pretty dashboard. It identifies the Markdown note you have open, displays source note information, provides one-click content operations, and writes results back to your Obsidian vault. You can also copy the source note path or rewrite prompt to the Claude Code terminal at the bottom of Obsidian for manual control.

Features

• Source note identification: Locks onto the current Markdown note, preventing the result page from taking over the target.
• Follow preview: The content preview in the ops panel scrolls along with the source note.
• One-click output: WeChat article rewrite, Xiaohongshu entry splitting, topic pool, summary signposts.
• One-click modification: Polish original text, add tags and bidirectional links, with automatic backup before modification.
• Writing style templates: Expressive buttons read the currently selected template, supporting saving your own account style.
• Claude Code integration: Executes tasks in the background via native claude -p.
• Terminal collaboration: Preserves the continuous Claude Code session in the Obsidian Terminal plugin.
• Localized content flow: Default scenarios target Chinese content platforms like WeChat Official Accounts, Xiaohongshu, WeChat Moments, and Jike.

Who It’s For

• Creators who use Obsidian to manage materials, notes, and topic ideas.
• People who already have Claude Code installed and want AI to process the current note directly.
• Anyone who wants to quickly turn a note into a WeChat article, Xiaohongshu content, topic pool, or knowledge base signpost.

Preview

The current version focuses on usability, supporting theme switching and centralizing common content actions into one workbench:

CC Note Ops Main Workbench

Theme switching is available directly within the workbench:

Theme Switching Demo

One-click operations and Claude Code takeover entry

• Top: displays current connection status.
• Middle: shows source note information and a scroll-following content preview.
• Bottom: provides one-click action cards.
• Extra: “Copy to Claude” entry for convenient manual takeover in any terminal panel.

Prerequisites

You will need:

1. Obsidian
   • Download: https://obsidian.md/download
2. Claude Code CLI
   • Official docs: https://docs.anthropic.com/en/docs/claude-code
   • After installation, ensure you can run in the terminal:

claude --help

3. Obsidian Terminal Plugin
   • In Obsidian, go to Settings -> Community plugins -> Browse and search for Terminal to install.
   • This plugin is not mandatory but strongly recommended. It keeps the Claude Code terminal docked at the bottom of Obsidian.

Installation

Clone the repository:

git clone https://github.com/SIXIANGGUO/cc-note-ops.git
cd cc-note-ops

Run the install script:

bash scripts/install.sh "/path/to/your/ObsidianVault"

Replace "/path/to/your/ObsidianVault" with your Obsidian vault path.

The install script copies:

Then restart Obsidian, go to Settings -> Community plugins and enable CC Command Center.

Usage

1. Open a Markdown note.
2. Open the command palette and run Open current note ops panel.
3. Click the desired button.

Output Buttons

Output buttons generate new files without modifying the original text:

Output location:

控制中心/运行结果/当前笔记/

Modification Buttons

Modification buttons first create a backup, then modify the source note:

Backup location:

控制中心/备份/

Xiaohongshu Image Prompts

The “Xiaohongshu entry split” outputs a copyable image generation prompt for each piece, defaulting to Chinese infographics:

• 3:4 vertical orientation
• Simplified Chinese
• Clear structure: title area, list area, conclusion area, etc.
• No fabricated data
• No replication of real brand logos or celebrity portraits

You can send the prompt directly to Gemini, ChatGPT, Jimeng, Doubao, or any other image generation model.

Writing Style Templates

The ops panel comes with 4 built-in writing style templates:

• Balanced Clarity
• Opinion-Driven Style (No Subject-Slipping)
• On-Camera Script
• Professional Tutorial

Template files are located at:

.cc-command-center/profiles/

You can edit these Markdown files directly to save your own WeChat article style, Xiaohongshu style, or on-camera script style.

Writing style only affects expressive tasks:

Structural tasks do not interact with writing style because they are more about organizing, archiving, and knowledge base maintenance.

Proxy Environment

Obsidian is a GUI app, and when it launches background commands, it may not inherit the proxy environment from your system terminal.

If you need buttons that call Claude Code in the background to explicitly use a proxy, create:

.cc-command-center/proxy.env

Example:

HTTP_PROXY=http://127.0.0.1:7890
HTTPS_PROXY=http://127.0.0.1:7890
ALL_PROXY=socks5://127.0.0.1:7890
NO_PROXY=localhost,127.0.0.1

This file only passes standard proxy environment variables to the background claude command. It does not guarantee account security or bypass any terms of service. Use it according to your own network environment and service rules.

Relationship with the Terminal Plugin

Button tasks call Claude Code independently in the background:

claude -p "..."

Therefore, the bottom terminal will not scroll or display the button task process.

The Terminal plugin is better suited for continuous conversations. It is recommended to enter the vault root directory in the terminal and run:

claude

If you want the Claude Code in the Terminal to manually process a note, click on the ops panel:

• Copy relative path
• Copy full path
• Copy rewrite prompt

Then paste them into the Claude Code session in the Terminal.

Custom Buttons

Default button configuration is at:

plugin/cc-command-center/data.json

Prompt templates for each button are at:

vault/.cc-command-center/actions/

Each button calls a hidden script:

vault/.cc-command-center/scripts/note-action.sh

After installation into the vault, the corresponding paths are:

.obsidian/plugins/cc-command-center/data.json
.cc-command-center/actions/
.cc-command-center/scripts/note-action.sh

In most cases, you only need to edit the Markdown templates in .cc-command-center/actions/, not the scripts.

Uninstallation

Keep the results in 控制中心/ and remove only the plugin and hidden scripts:

bash scripts/uninstall.sh "/path/to/your/ObsidianVault"

If you also want to delete 控制中心/:

bash scripts/uninstall.sh "/path/to/your/ObsidianVault" --remove-content

Restart Obsidian after uninstalling.

Security Notes

This project executes shell scripts on your local machine and invokes the local Claude Code CLI. Before enabling, please read:

• plugin/cc-command-center/main.js
• plugin/cc-command-center/data.json
• vault/.cc-command-center/scripts/note-action.sh

The default design is intentionally conservative:

• Output tasks only write to 控制中心/运行结果/当前笔记/.
• Modification tasks create a backup of the original text first.
• No network credentials are read.
• Your notes are not uploaded to the project author’s server.
• The optional proxy only reads standard proxy variables from .cc-command-center/proxy.env and does not execute arbitrary shell code.

However, Claude Code itself works according to your Claude Code configuration. Please ensure you understand how Claude Code operates before using it.

Project Structure

.
├── docs/
│   └── quickstart.md
├── plugin/
│   └── cc-command-center/
│       ├── data.json
│       ├── main.js
│       ├── manifest.json
│       └── styles.css
├── scripts/
│   ├── install.sh
│   └── uninstall.sh
└── vault/
    ├── .cc-command-center/
    │   ├── actions/
    │   ├── profiles/
    │   ├── proxy.env.example
    │   └── scripts/
    │       └── note-action.sh
    └── 控制中心/

Development

This project is a hand-written Obsidian plugin and does not require a build step.

After modification, you can directly reinstall to a test vault:

bash scripts/install.sh "/path/to/test-vault"

Minimal checks:

node --check plugin/cc-command-center/main.js
jq empty plugin/cc-command-center/manifest.json plugin/cc-command-center/data.json
bash -n scripts/install.sh
bash -n scripts/uninstall.sh
bash -n vault/.cc-command-center/scripts/note-action.sh

License

MIT