Back to corpus
technical noteexperiment writeup candidatescore 28

cc-agent-ipc

This crate provides an async Rust interface to communicate with the `cc-agent-service` Python daemon over Unix sockets. It enables Rust applications (Tauri, CLI tools, backend services) to leverage multiple LLM providers:

Open full HTMLDownload HTMLCorpus JSONPaper schema

Full HTML reader

Read the full artifact

Open in new tab

Extracted abstract or opening context

This crate provides an async Rust interface to communicate with the `cc-agent-service` Python daemon over Unix sockets. It enables Rust applications (Tauri, CLI tools, backend services) to leverage multiple LLM providers: - **Claude** (claude-agent-sdk) - Extended thinking, subagents - **OpenAI** (openai-agents) - Handoffs, guardrails - **Auto** - Dynamic provider selection based on capabilities Available strategies: - `Fixed` - Always use specified provider - `RoundRobin` - Alternate between providers - `Capability` - Route based on task requirements - `Cost` - Minimize cost - `Latency` - Minimize latency - **cc-agent-sdk** - TypeScript SDK for Node.js/browser applications - **cc-agent-service** - Python daemon that orchestrates Claude/OpenAI agents

Promotion decision

What has to happen next

Attach run IDs, datasets, metrics, and reproduction commands.

Why this is not always a full paper yet

Corpus pages are public-safe readers for discovered workspace artifacts. They are not automatically final papers. A corpus item becomes a polished paper only after the editable source, evidence checkpoints, references, figures, render path, and release status are attached through the paper schema.