# Codebuddy Ide Vs Codebuddy Code Hook Integration

> |

- **Type:** Skill
- **Install:** `agentstack add skill-ccppvv-agent-skills-codebuddy-ide-vs-codebuddy-code-hook-integration`
- **Verified:** Yes — security-reviewed for prompt injection and unsafe behavior
- **Seller:** [ccppvv](https://agentstack.voostack.com/s/ccppvv)
- **Installs:** 0
- **Category:** [Agent Skills](https://agentstack.voostack.com/c/agent-skills)
- **Latest version:** 0.1.0
- **License:** MIT
- **Upstream author:** [ccppvv](https://github.com/ccppvv)
- **Source:** https://github.com/ccppvv/agent-skills/tree/main/codebuddy-ide-vs-codebuddy-code-hook-integration

## Install

```sh
agentstack add skill-ccppvv-agent-skills-codebuddy-ide-vs-codebuddy-code-hook-integration
```

Requires the [AgentStack CLI](https://agentstack.voostack.com/docs/cli). Works with Claude Code, Cursor, and any MCP-compatible agent.

## About

# CodeBuddy IDE vs CodeBuddy Code Hook Integration

## Problem
A desktop companion, status widget, or automation reacts correctly to `CodeBuddy Code` sessions, but does nothing when only `CodeBuddy IDE` is open or actively being used.

## Context / Trigger Conditions
Use this skill when all or most of the following are true:

- The project registers hooks into `~/.codebuddy/settings.json`
- Runtime status changes are driven by hook scripts or log polling
- The local app receives updates through an HTTP endpoint such as `/state`
- CodeBuddy CLI / Code events work, but IDE-only activity does not
- Repository searches show `CodeBuddy Code` support, but no `ACP`, IDE event API, or IDE-specific hook integration

Typical symptoms:

- `~/.codebuddy/settings.json` already contains hook commands, but the app stays idle when only CodeBuddy IDE is used
- The project distinguishes editors only as `code` / `cursor`, not `codebuddy`
- There is no fallback telemetry except hook events or log polling

## Solution

1. **Separate CodeBuddy Code from CodeBuddy IDE mentally first**
   - `~/.codebuddy/settings.json` belongs to the **CodeBuddy Code / CLI configuration layer**.
   - Do not assume it provides **IDE work-status events**.

2. **Verify the existing integration path**
   - Check whether the repository writes hooks to `~/.codebuddy/settings.json`
   - Check whether hook scripts post `{ state, session_id, event, agent_id }` to a local server
   - Confirm whether the status server only updates on incoming hook/log events

3. **Search for IDE-native support**
   Look for any of the following:
   - `ACP` / `acp`
   - IDE plugin or extension code that emits work-state events
   - CodeBuddy IDE-specific config files or APIs
   - `editor === "codebuddy"` or similar editor normalization

   If none exist, the project likely supports **CodeBuddy Code only**, not IDE-native activity.

4. **Check whether hooks are actually installed**
   - If `~/.codebuddy/settings.json` contains the hook commands, then installation is likely fine
   - If the app still does not react to IDE-only activity, the missing piece is **event source support**, not hook registration

5. **Check backup detection paths**
   Some projects have a backup “process is running” detection path for startup recovery.
   - If that path only checks processes like `claude`, `codex`, `copilot`, `gemini`, it will not help CodeBuddy IDE
   - Even if a registry contains `codebuddy-code`, a separate hardcoded startup detector may still omit it

6. **Conclude the root cause explicitly**
   The root cause is usually:
   - The project is integrated with **CodeBuddy Code hooks**, not **CodeBuddy IDE work-state events**
   - Therefore opening the IDE alone produces **no state events** for the app to consume

7. **Pick the correct fix direction**
   Choose one of these depending on product intent:

   - **If only CodeBuddy Code support is intended**:
     update docs/UI text to make that distinction explicit
   - **If CodeBuddy IDE should also drive status**:
     add a real IDE event source, such as:
     - IDE-specific hook integration
     - IDE extension/plugin bridge
     - ACP/session bridge if the IDE exposes one
     - a polling mechanism over an IDE-owned state/log source

## Verification

A diagnosis is confirmed when:

- `~/.codebuddy/settings.json` already has the expected hook commands
- Repository search shows support for `CodeBuddy Code` but not IDE-native integration
- The local status server updates only through hook/log inputs
- Using CodeBuddy IDE alone does not generate any incoming status events

## Example

A pet app posts all agent activity through `/state` and installs hooks into `~/.codebuddy/settings.json`. The repo contains:

- a `codebuddy-code` agent definition
- hook registration for target `codebuddy`
- a hook script that detects `codebuddy` / `codebuddy-code`
- no `ACP` references
- no `editor: "codebuddy"` normalization

Result: `CodeBuddy Code` sessions animate the pet, but opening `CodeBuddy IDE` alone does not. The issue is not broken hook installation; it is that the project has **no CodeBuddy IDE event bridge**.

## Notes

- A project may partially support CodeBuddy via CLI hooks while still lacking IDE support
- Backup startup detection is often misleading because it can be hardcoded separately from the main agent registry
- If docs say “supports CodeBuddy” without saying “CodeBuddy Code”, users will often assume IDE-native support exists

## References

- `https://www.codebuddy.ai/docs/zh/cli/settings` — confirms `.codebuddy/settings.json` is part of CodeBuddy Code / CLI configuration

## Source & license

This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.

- **Author:** [ccppvv](https://github.com/ccppvv)
- **Source:** [ccppvv/agent-skills](https://github.com/ccppvv/agent-skills)
- **License:** MIT

Install and usage instructions live in the source repository linked above.

## Pricing

- **Free** — Free

## Security capabilities

Automated source analysis of v0.1.0 — what this tool can access:

- **Network access:** no
- **Filesystem access:** no
- **Shell / process execution:** no
- **Environment & secrets:** no
- **Dynamic code execution:** no

*"Yes" means the capability is present in the source — more access means more to trust, not that it is unsafe.*


## Versions

- **0.1.0** — security scan: passed — Imported from the upstream source.

## Links

- Listing page: https://agentstack.voostack.com/l/skill-ccppvv-agent-skills-codebuddy-ide-vs-codebuddy-code-hook-integration
- Seller: https://agentstack.voostack.com/s/ccppvv
- Browse the marketplace: https://agentstack.voostack.com/browse

---
Listed on AgentStack — the marketplace for AI agent skills and MCP servers. Every listing is security-reviewed. Creators keep 70%.