agent-config 0.3.2

# Cline

ID: `cline` — `agent_config::by_id("cline")`

Cline v3.36+ (January 2026) supports hooks via executable scripts. Earlier versions
support prompt-level rules only.

## Hooks

### User scope (`Scope::Global`)

Not supported in v0.1. Cline exposes a user-level hooks directory on some
platforms, but this crate only writes project-local hooks because the global
path is platform-specific and less stable.

### Project scope (`Scope::Local(<root>)`)

| | |
| --- | --- |
| Path | `.clinerules/hooks/` |
| Format | Executable shell scripts |
| Input/Output | JSON via stdin/stdout |

**Platform support:** macOS and Linux only (no Windows hooks).

### Hook types

Eight hook types supported (v3.36+):

- `TaskStart` — Hook fires at task start
- `TaskResume` — Hook fires when resuming a paused task
- `TaskCancel` — Hook fires when task is cancelled
- `TaskComplete` — Hook fires when task completes successfully
- `PreToolUse` — Hook fires before tool execution
- `PostToolUse` — Hook fires after tool execution
- `UserPromptSubmit` — Hook fires when user submits a prompt
- `PreCompact` — Hook fires before message compaction

### Return fields

Hooks may return JSON with:

```json
{
  "cancel": false,
  "contextModification": "additional context for the task",
  "errorMessage": "optional error message"
}
```

### Example hook script

```bash
#!/bin/bash
# Script receives JSON on stdin
read -r task_json

# Process and output response
echo '{"cancel": false}'
```

## Prompt instructions

### User scope (`Scope::Global`)

Not supported in v0.1. Cline reads global rules from a per-OS Cline Rules
directory (e.g., `~/Documents/Cline/Rules/`). Calling with `Scope::Global`
returns `AgentConfigError::UnsupportedScope`.

### Project scope (`Scope::Local(<root>)`)

| | |
| --- | --- |
| File | `<root>/.clinerules/<tag>.md` |
| Mechanism | One markdown file per consumer (the file is owned outright) |
| Format | Plain markdown (the body of `RulesBlock::content`, with a trailing newline) |

Uninstall removes the file and prunes empty parent directories.

> Cline still reads the legacy single-file `<root>/.clinerules`. The directory
> form `<root>/.clinerules/*.md` is preferred and what this integration
> writes. Rules can include YAML frontmatter for conditional activation;
> consumers may pass that as part of `RulesBlock::content`.

## Instructions

Standalone instruction files installed via `InstructionSurface`. Uses
`InstructionPlacement::StandaloneFile` because Cline already has a per-tag
rules directory; each instruction is one file in that directory, with no host
include needed.

| | |
| --- | --- |
| Instruction file | `<root>/.clinerules/<name>.md` |
| Mechanism | One file per instruction — no host file needed |
| Ledger | `<root>/.clinerules/.agent-config-instructions.json` |
| Placement | `InstructionPlacement::StandaloneFile` |

## MCP servers

### User scope (`Scope::Global`)

| | |
| --- | --- |
| File | `~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json` on macOS |
| Format | JSON |
| Key | `mcpServers` |

### Project scope (`Scope::Local(<root>)`)

Not supported. Cline's documented MCP settings file is global to the VS Code
extension.

### Configuration

```json
{
  "mcpServers": {
    "my-server": {
      "command": "npx",
      "args": ["-y", "@example/server"]
    }
  }
}
```

## Skills

| Scope | Path |
| --- | --- |
| User | `~/.cline/skills/<name>/` |
| Project | `.cline/skills/<name>/` |

Each skill is a directory containing `SKILL.md`. Cline also supports
`.clinerules/skills` and `.claude/skills` project locations, but `agent-config`
writes the native `.cline/skills` path.

## References

- <https://docs.cline.bot/customization/cline-rules>
- <https://docs.cline.bot/customization/hooks>
- <https://docs.cline.bot/customization/skills>
- <https://docs.cline.bot/mcp/adding-and-configuring-servers>
- <https://cline.bot/blog/cline-v3-36-hooks>