https://github.com/hellowind777/hello2cc
Native-first Claude Code plugin for third-party models with silent Agent model injection and output styles.
https://github.com/hellowind777/hello2cc
Last synced: about 1 month ago
JSON representation
Native-first Claude Code plugin for third-party models with silent Agent model injection and output styles.
- Host: GitHub
- URL: https://github.com/hellowind777/hello2cc
- Owner: hellowind777
- License: apache-2.0
- Created: 2026-03-30T14:21:24.000Z (about 1 month ago)
- Default Branch: main
- Last Pushed: 2026-04-03T06:59:35.000Z (about 1 month ago)
- Last Synced: 2026-04-03T13:21:33.755Z (about 1 month ago)
- Language: JavaScript
- Size: 287 KB
- Stars: 357
- Watchers: 4
- Forks: 37
- Open Issues: 2
-
Metadata Files:
- Readme: README.md
- Changelog: CHANGELOG.md
- License: LICENSE
Awesome Lists containing this project
- awesome-claude-code - **hello2cc** - first Claude Code plugin for third-party models with silent Agent model injection and output styles. (đ Claude Plugins)
README
# hello2cc
[](https://www.npmjs.com/package/hello2cc)
[](./LICENSE)
[](https://github.com/hellowind777/hello2cc/actions/workflows/publish.yml)
Make third-party models work inside Claude Code as close to Opus as the plugin layer can drive them.
`hello2cc` does **not** replace your model gateway, provider mapping, or account permissions.
Its job is simpler:
> If you already connected GPT, Kimi, DeepSeek, Gemini, Qwen, or other third-party models to Claude Code, `hello2cc` keeps pushing them toward Opus-compatible Claude Code behavior: native capability priorities, tool and agent choice, team/task workflow use, failure recovery, and output style.
**Language:** English | [įŽäŊä¸æ](./README_CN.md)
---
## đ What changed in 0.4.9
Compared with `0.4.8`, this release keeps the current runtime behavior baseline stable:
| 0.4.9 note | What you should notice |
|---|---|
| Runtime routing baseline stays on `0.4.8` behavior | Team retry, task tracking, and current-info behavior continue without a new migration path |
| No extra config changes are required | Existing Claude Code, CCSwitch, and plugin settings can continue as-is |
| The current user-facing fixes remain the active baseline | Native-style team retry fallback and recent WebSearch shaping stay in effect |
| README is refreshed to the `0.4.9` baseline | Upgrade guidance now reflects the current release without changing normal usage |
---
## đ¯ Why use hello2cc?
| Common problem | What hello2cc improves |
|---|---|
| A matching skill or workflow already exists, but the model keeps rewriting the process | Encourages the model to continue with the surfaced or already-loaded workflow |
| The session already exposes MCP resources or tools, but the model still takes a detour | Nudges the model toward the most direct path first |
| Plain parallel workers get confused with team or teammate semantics | Reduces avoidable agent routing mistakes |
| The model can answer, but does not pick the right Claude Code capability | Pushes tool, agent, workflow, and MCP choice back toward native Claude Code priorities |
| The model depends too much on wording or keyword hints | Switches to language-agnostic semantic matching inside host-exposed candidate boundaries |
| The output style drifts away from native Opus | Forces a tighter Claude Code-native result style |
| The model drifts into verbose meta narration | Keeps responses closer to concise native Claude Code style |
---
## â
Best for / â Not for
### â
Best for
- You already use Claude Code with third-party models through **CCSwitch** or another mapping layer
- You want those models to behave more like a native Claude Code session
- You have skills, workflows, MCP servers, or plugins installed and want them to be used more reliably
- You want parallel agent work to choose a more appropriate path
### â Not for
- Setting up provider accounts, API keys, or gateway access
- Exposing tools that Claude Code did not expose in the first place
- Replacing **CCSwitch**
- Overriding higher-priority repository rules such as `CLAUDE.md`, `AGENTS.md`, or direct user instructions
---
## đ By the numbers
| Item | Value |
|---|---|
| Install flow | 3 steps |
| Extra command required after install | 0 |
| Common config profiles | 2 |
| Main goal | 1 â make third-party models behave more like native Claude Code / Opus sessions |
---
## ⨠What it helps with
### Skills & workflows
Better continuity when a workflow is already visible or already in progress.
### Tools & MCP
Stronger preference for capabilities that are already available in the session.
### Agents & teams
Keeps one-shot parallel work on ordinary agent paths, while sustained collaboration is more likely to use a real team + task-board flow.
### Cleaner interaction
Less unnecessary meta narration and fewer avoidable routing mistakes.
---
## đ Quick start
### 1) Clone this repository
```bash
git clone https://github.com/hellowind777/hello2cc.git
cd hello2cc
```
### 2) Add the local marketplace
```bash
claude plugins marketplace add ""
```
Replace `` with your local `hello2cc` repository path.
### 3) Install the plugin
```bash
claude plugins install hello2cc@hello2cc-local
```
Then reopen Claude Code or run `/reload-plugins`.
### Expected result
- No extra manual entry point is required
- Installing the plugin does not write `agent=hello2cc:native` into Claude Code settings
- Plugin enablement stays under Claude Code's own plugin state, not a plugin-shipped `settings.json`
- Third-party models are more likely to use session-visible capabilities directly
- Ordinary parallel agents are less likely to be misrouted
- Team/subagent sessions are less likely to suffer from oversized injected context
---
## đ§ Recommended configuration
### Option A â Keep the default strong alignment
Good when your model mapping is already handled by **CCSwitch** and you want hello2cc to stay on its default strong alignment path.
```json
{
"mirror_session_model": true
}
```
### Option B â Set a stable default agent slot
Good when you want most agents to use the same Claude slot.
```json
{
"mirror_session_model": true,
"default_agent_model": "opus"
}
```
If your real target model is mapped through **CCSwitch**, keep the actual mapping there.
In `hello2cc`, prefer stable Claude slot values such as `inherit`, `opus`, `sonnet`, or `haiku`.
### What 0.4.9 especially improves
- Keeps the `0.4.8` runtime behavior baseline intact
- Requires no new migration for existing Claude Code users
- Continues the native-style team retry fallback path
- Continues the recent current-info / WebSearch behavior improvements
---
## đ§ How it fits into your workflow
```mermaid
flowchart LR
A[Third-party model already connected in Claude Code] --> B[Open a normal Claude Code session]
B --> C[Session exposes tools, agents, skills, workflows, or MCP]
C --> D[hello2cc helps the model choose the path more naturally]
D --> E[Fewer detours and cleaner agent routing]
style A fill:#e3f2fd
style B fill:#e3f2fd
style C fill:#fff3e0
style D fill:#e8f5e9
style E fill:#4caf50,color:#fff
```
---
## đ ī¸ Reinstall / upgrade
If you changed the local repository or want a clean reinstall:
```bash
claude plugins uninstall --scope user hello2cc@hello2cc-local
claude plugins marketplace remove hello2cc-local
claude plugins marketplace add ""
claude plugins install hello2cc@hello2cc-local
```
Then reopen Claude Code or run `/reload-plugins`.
---
## đ ī¸ Troubleshooting
### The plugin seems inactive
Try these in order:
1. Reopen Claude Code or run `/reload-plugins`
2. Confirm the plugin is installed and enabled
3. If you upgraded from a local clone, reinstall it cleanly
### `hello2cc:native` still shows after disable or `/reload`
That banner can persist in the current or resumed session because Claude Code keeps session agent state separately from plugin enablement.
Current `hello2cc` no longer ships a plugin-side `settings.json` to force `agent=hello2cc:native`, so a clean reinstall or a fresh session stops new unintended agent injection.
### The model still ignores a skill, tool, or MCP resource
Check whether:
1. That capability is actually exposed in the current session
2. A higher-priority project rule or user instruction is restricting it
3. You are continuing the same workflow instead of starting a different one
### Multiple plugins feel noisy together
Current versions no longer provide `sanitize-only` or another lightweight fallback mode.
If several plugins are injecting guidance, keep one dominant behavior-alignment layer and disable or retune the conflicting plugins instead of weakening hello2cc into a thin shim.
### You still hit `summary is required when message is a string`
Update to the latest version, reload the session, and reinstall if needed.
Recent versions add a compatibility layer for plain-text `SendMessage`.
### Team retries show a hello2cc red deny after a missing or deleted team
Update to `0.4.9`, then reload the plugin cleanly.
Current versions remove the plugin-side pre-deny for explicit teammate retries, so missing-team handling falls back to Claude Code's native team error path instead.
### Current-info or compare tasks keep missing web results
Update to `0.4.6` or later, then reload the plugin cleanly.
Recent versions tighten short-query shaping and treat `Did 0 searches` as an empty search attempt instead of a successful result.
---
## â FAQ
Does hello2cc replace CCSwitch?
No. Keep model mapping in CCSwitch. hello2cc focuses on what happens after the model is already running inside Claude Code.
Does it enable tools that Claude Code did not expose?
No. It only helps the model use capabilities that are already available in the current session.
Do I need to switch an output style manually?
Usually no. After installation, it should work without an extra manual entry point.
Will installation force-select hello2cc:native for the current thread?
No. The plugin ships the native agent as an available option, but it no longer injects a default `agent` setting into Claude Code.
Will it block my existing skills, plugins, or MCP servers?
No. The goal is the opposite: make those existing capabilities easier for third-party models to discover and use.
Does every multi-agent task become a team?
No. One-shot parallel work can stay on ordinary agent paths. More sustained collaboration is more likely to use a team flow.
Do I need to set a default agent model?
Only if you want a stable default Claude slot for most agents. If your mapping is already managed well elsewhere, you can keep the config minimal.
Can I still switch hello2cc into a lightweight compatibility-only mode?
No. The current direction keeps hello2cc as a default strong alignment layer instead of falling back to a thin sanitize-only shim.
---
## đ Support
- Issues: https://github.com/hellowind777/hello2cc/issues
- Releases: https://github.com/hellowind777/hello2cc/releases
---
## đ License
Apache-2.0