feat(conductor): Add CLI Aliases track
Browse files
conductor/tracks/cli_aliases_20260110/metadata.json
ADDED
|
@@ -0,0 +1,8 @@
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| 1 |
+
{
|
| 2 |
+
"track_id": "cli_aliases_20260110",
|
| 3 |
+
"type": "feature",
|
| 4 |
+
"status": "new",
|
| 5 |
+
"created_at": "2026-01-10T00:00:00Z",
|
| 6 |
+
"updated_at": "2026-01-10T00:00:00Z",
|
| 7 |
+
"description": "Develop a unified configuration script and shell aliases to enable simultaneous and seamless execution of Claude Code and OpenCode through the proxy."
|
| 8 |
+
}
|
conductor/tracks/cli_aliases_20260110/plan.md
ADDED
|
@@ -0,0 +1,12 @@
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| 1 |
+
# Plan: CLI Proxy Aliases
|
| 2 |
+
|
| 3 |
+
## Phase 1: Script Development
|
| 4 |
+
- [ ] Task: Create `examples/cli-config/proxy-tools.rc`.
|
| 5 |
+
- [ ] Task: Implement `p-claude` function with scoped environment variables.
|
| 6 |
+
- [ ] Task: Implement `p-code` function with scoped arguments/env vars.
|
| 7 |
+
- [ ] Task: Conductor - User Manual Verification 'Script Functionality' (Protocol in workflow.md)
|
| 8 |
+
|
| 9 |
+
## Phase 2: Documentation & Cleanup
|
| 10 |
+
- [ ] Task: Update `docs/CLI_INTEGRATION.md` to include a new "Quick Start with Aliases" section.
|
| 11 |
+
- [ ] Task: Create a `README.md` inside `examples/cli-config/` explaining the contents.
|
| 12 |
+
- [ ] Task: Conductor - User Manual Verification 'Documentation' (Protocol in workflow.md)
|
conductor/tracks/cli_aliases_20260110/spec.md
ADDED
|
@@ -0,0 +1,21 @@
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| 1 |
+
# Specification: CLI Proxy Aliases
|
| 2 |
+
|
| 3 |
+
## Context
|
| 4 |
+
Users currently need to manually export environment variables to route CLI tools through CLIProxyAPI Plus. To improve the user experience, we want to provide a "drop-in" script that adds shell aliases/functions. This allows users to run tools specifically through the proxy (e.g., `p-claude`, `p-code`) without permanently altering their global shell environment or constantly switching contexts.
|
| 5 |
+
|
| 6 |
+
## Goals
|
| 7 |
+
1. **Unified Script:** Create a shell script (`examples/cli-config/proxy-tools.rc`) meant to be sourced.
|
| 8 |
+
2. **Simultaneous Usage:** Ensure configurations for Claude Code and OpenCode do not conflict (they naturally don't, but the script should handle them cleanly).
|
| 9 |
+
3. **Convenience Aliases:**
|
| 10 |
+
* `p-claude`: Runs Claude Code targeted at the proxy.
|
| 11 |
+
* `p-code`: Runs Open Interpreter targeted at the proxy.
|
| 12 |
+
4. **Documentation:** Update the integration guide to explain this "Easy Mode".
|
| 13 |
+
|
| 14 |
+
## Non-Goals
|
| 15 |
+
* Binary wrapping (we are using shell functions/aliases).
|
| 16 |
+
* Automatic installation into user's `.bashrc` (we will provide the script and instructions, but not modify user files automatically).
|
| 17 |
+
|
| 18 |
+
## Success Metrics
|
| 19 |
+
* User can source the file and immediately run `p-claude` to hit localhost:7860.
|
| 20 |
+
* User can run `p-code` to hit localhost:7860.
|
| 21 |
+
* Standard `claude` and `interpreter` commands remain unaffected (optional, but good practice if using alias-scope env vars).
|