agentica-claude-proxy▌
parcadei/continuous-claude-v3 · updated Apr 8, 2026
MDX-style export adds YAML metadata + attribution linking explainx.ai and this canonical listing URL.
Use this skill when developing or debugging the Agentica-Claude proxy integration.
Agentica-Claude Code Proxy Integration
Use this skill when developing or debugging the Agentica-Claude proxy integration.
When to Use
- Setting up Agentica agents to use Claude Code tools
- Debugging agent hallucination issues
- Fixing permission errors in file operations
- Understanding the REPL response format
Architecture Overview
Agentica Agent → S_M_BASE_URL → Claude Proxy → claude -p → Claude CLI (with tools)
(localhost:2345) (localhost:8080)
Critical Requirements
1. --allowedTools Flag (REQUIRED)
Claude CLI in -p mode restricts file operations. You MUST add:
subprocess.run([
"claude", "-p", prompt,
"--append-system-prompt", system_prompt,
"--allowedTools", "Read", "Write", "Edit", "Bash", # REQUIRED
])
Without this, agents will report "permission denied" for Write/Edit operations.
2. SSE Streaming Format (REQUIRED)
Agentica expects SSE streaming, not plain JSON:
# Response format
yield f"data: {json.dumps(chunk)}\n\n"
yield "data: [DONE]\n\n"
3. REPL Response Format (REQUIRED)
Agents MUST return results as Python code blocks with a return statement:
return "your result here"
Agentica's REPL parser extracts code between ```python and ```.
Anti-Hallucination Prompt Engineering
Agents will hallucinate success without actually using tools unless you explicitly warn them:
## ANTI-HALLUCINATION WARNING
**STOP AND READ THIS CAREFULLY:**
You have access to these tools: Read, Write, Edit, Bash
When the task asks you to create/modify/run something:
1. FIRST: Actually invoke the tool (Read, Write, Edit, or Bash)
2. SECOND: Wait for the tool result
3. THIRD: Then return your answer based on what actually happened
**DO NOT** skip the tool invocation and just claim success!
If you didn't invoke a tool, you CANNOT claim the action succeeded.
Path Sandboxing
Both Claude Code and Agentica have sandboxes:
/tmp/paths are blocked by Claude Code- Files outside project directory blocked by Agentica
Solution: Use project-relative paths like workspace/ instead of /tmp/
Debugging
Check Agent Logs
cat logs/agent-<N>.log
Note: Logs only show final conversational response, not tool invocations.
Test Proxy Directly
curl -s http://localhost:8080/v1/chat/completions \
-H "Content-Type: application/json" \
-d '{"model": "claude", "messages": [{"role": "user", "content": "Create file at workspace/test.txt"}], "stream": false}'
Verify File Operations
# After agent claims to create file
ls -la workspace/test.txt
cat workspace/test.txt
Server Commands
Start Servers
# Terminal 1: Proxy
uv run python scripts/agentica/claude_proxy.py --port 8080
# Terminal 2: Agentica Server
cd workspace/agentica-research/agentica-server
INFERENCE_ENDPOINT_URL=http://localhost:8080/v1/chat/completions uv run agentica-server --port 2345
Use Swarm
S_M_BASE_URL=http://localhost:2345 uv run python your_script.py
Health Checks
curl http://localhost:8080/health # Proxy
curl http://localhost:2345/health # Agentica
Reference Files
- Proxy implementation:
scripts/agentica/claude_proxy.py - REPL_BASELINE prompt:
scripts/agentica/claude_proxy.py:49-155 - Comprehensive test:
workspace/test_swarm_all_tools.py - DependencySwarm:
scripts/agentica/dependency_swarm.py
Common Errors
| Error | Cause | Fix |
|---|---|---|
| "Permission denied" | Missing --allowedTools | Add --allowedTools Read Write Edit Bash |
| Agent claims success but file not created | Hallucination | Add anti-hallucination prompt section |
| "Cannot access /tmp/..." | Sandbox restriction | Use project-relative paths |
| "APIConnectionError" | Wrong response format | Use SSE streaming (data: {...}\n\n) |
| "NameError: view_file" | Agent using REPL functions | Add REPL_BASELINE with native tool examples |
How to use agentica-claude-proxy on Cursor
AI-first code editor with Composer
Prerequisites
Before installing skills in Cursor, ensure your development environment meets these requirements:
- ›Cursor installed and configured on your development machine
- ›Node.js version 16.0+ with npm package manager (verify with
node --version) - ›Active project directory or workspace where you want to add agentica-claude-proxy
Execute installation command
Execute the skills CLI command in your project's root directory to begin installation:
The skills CLI fetches agentica-claude-proxy from GitHub repository parcadei/continuous-claude-v3 and configures it for Cursor.
Select Cursor when prompted
The CLI will show a list of available agents. Use arrow keys to navigate and space to select Cursor:
Verify installation
Confirm successful installation by checking the skill directory location:
Reload or restart Cursor to activate agentica-claude-proxy. Access the skill through slash commands (e.g., /agentica-claude-proxy) or your agent's skill management interface.
Security & Verification Notice
We perform automated surface-level scans (Gen AI Scanner, Socket, Snyk) during installation. These checks detect common vulnerabilities but do not guarantee complete security. Always review skill source code and verify the publisher's reputation before production use.
Skills execute code in your development environment. Always verify the publisher's identity, review recent commits, and test in isolated environments before production deployment.
List & Monetize Your Skill
Submit your Claude Code skill and start earning
Use Cases▌
Task Automation & Efficiency
Automate repetitive workflows and reduce manual effort
Example
Generate reports, summarize documents, draft communications
Save 3-5 hours per week on routine tasks
Knowledge Enhancement
Learn new skills, understand complex topics, get expert guidance
Example
Explain concepts, provide examples, suggest learning resources
Accelerate learning and skill development by 2x
Quality Improvement
Enhance output quality through reviews, suggestions, and refinements
Example
Review drafts, suggest improvements, catch errors
Improve work quality by 30-40% with less effort
Implementation Guide▌
Prerequisites
- ›Claude Desktop or compatible AI client with skill support
- ›Clear understanding of task or problem to solve
- ›Willingness to iterate and refine outputs
Time Estimate
15-45 minutes depending on use case complexity
Installation Steps
- 1.Install skill using provided installation command
- 2.Test with simple use case relevant to your work
- 3.Evaluate output quality and relevance
- 4.Iterate on prompts to improve results
- 5.Integrate into regular workflow if valuable
Common Pitfalls
- ⚠Expecting perfect results without iteration
- ⚠Not providing enough context in prompts
- ⚠Using skill for tasks outside its intended scope
- ⚠Accepting outputs without review and validation
Best Practices▌
✓ Do
- +Start with clear, specific prompts
- +Provide relevant context and constraints
- +Review and refine all outputs before using
- +Iterate to improve output quality
- +Document successful prompt patterns
✗ Don't
- −Don't use without understanding skill limitations
- −Don't skip validation of outputs
- −Don't share sensitive information in prompts
- −Don't expect skill to replace human judgment
💡 Pro Tips
- ★Be specific about desired format and style
- ★Ask for multiple options to choose from
- ★Request explanations to understand reasoning
- ★Combine AI efficiency with human expertise
When to Use This▌
✓ Use When
Use when skill capabilities match your task, clear ROI on time saved, and you can validate outputs. Best for repetitive tasks, learning, and quality improvement.
✗ Avoid When
Avoid when task requires deep expertise you can't validate, involves sensitive decisions, or when learning process is more valuable than speed of completion.
Learning Path▌
- 1Familiarize yourself with skill capabilities and limitations
- 2Start with low-risk, non-critical tasks
- 3Progress to more complex and valuable use cases
- 4Build expertise through regular use and experimentation
Discussion
Product Hunt–style comments (not star reviews)- No comments yet — start the thread.
Ratings
4.4★★★★★65 reviews- ★★★★★Alexander Choi· Dec 24, 2024
Registry listing for agentica-claude-proxy matched our evaluation — installs cleanly and behaves as described in the markdown.
- ★★★★★Sophia Sharma· Dec 20, 2024
Useful defaults in agentica-claude-proxy — fewer surprises than typical one-off scripts, and it plays nicely with `npx skills` flows.
- ★★★★★Luis Iyer· Dec 20, 2024
Solid pick for teams standardizing on skills: agentica-claude-proxy is focused, and the summary matches what you get after install.
- ★★★★★Luis Kapoor· Dec 8, 2024
agentica-claude-proxy reduced setup friction for our internal harness; good balance of opinion and flexibility.
- ★★★★★Alexander Park· Dec 8, 2024
We added agentica-claude-proxy from the explainx registry; install was straightforward and the SKILL.md answered most questions upfront.
- ★★★★★Kofi Yang· Nov 27, 2024
agentica-claude-proxy fits our agent workflows well — practical, well scoped, and easy to wire into existing repos.
- ★★★★★Kofi Ndlovu· Nov 23, 2024
agentica-claude-proxy reduced setup friction for our internal harness; good balance of opinion and flexibility.
- ★★★★★Luis Huang· Nov 15, 2024
agentica-claude-proxy is among the better-maintained entries we tried; worth keeping pinned for repeat workflows.
- ★★★★★Ava Mensah· Nov 15, 2024
Solid pick for teams standardizing on skills: agentica-claude-proxy is focused, and the summary matches what you get after install.
- ★★★★★Ira Chawla· Nov 11, 2024
I recommend agentica-claude-proxy for anyone iterating fast on agent tooling; clear intent and a small, reviewable surface area.
showing 1-10 of 65