We have always supported defining agents in YAML and writing tools in Python. Until now, setup and deployment still involved considerable manual work: uploading files, creating project structures, and discovering YAML typos after the fact. Today we're releasing the Composer SDK to change that.
What Was the Problem?
Building agents on Connic worked, but the developer experience had friction:
- ā¢Manual uploads: Every agent or tool change required another file upload
- ā¢No scaffolding: Developers had to create the folder structure and boilerplate files from scratch
- ā¢No local validation: YAML syntax errors or missing tools appeared only after uploading
- ā¢Slow iteration: The upload-test-fix cycle was tedious, especially for small changes
The SDK solves each of these with proper CLI tooling.
Agents stay in YAML, tools remain ordinary Python functions, and a push to Git starts deployment.
Try Connic freeWhat the SDK Does
Install it from PyPI:
$ pip install connic-composer-sdkThe package provides commands for the full workflow:
connic init - Project Scaffolding
No more setting up folders by hand. One command creates a complete project structure with example agents, tools, middleware, and a README explaining each piece.
$ connic init my-agents
ā Initialized Connic project in /Users/you/my-agents
Created files:
agents/assistant.yaml (LLM agent)
agents/invoice-processor.yaml (LLM agent with retry)
agents/tax-calculator.yaml (Tool agent)
agents/document-pipeline.yaml (Sequential agent)
agents/orchestrator.yaml (Orchestrator with trigger_agent)
agents/retrieval-agent.yaml (Retrieval agent with RAG)
tools/calculator.py
middleware/assistant.py
.gitignore
requirements.txt
README.mdThe generated examples cover all agent types (LLM, Tool, Sequential) plus patterns like orchestration and semantic retrieval. Unneeded examples can be deleted and the rest modified.
connic lint - Local Validation
Catch errors before uploading. The SDK loads all project agents and tools locally, validates the YAML, checks that referenced tools exist, and previews the deployment.
$ connic lint
Connic Composer SDK - Validation
Discovering tools...
Found 3 tools in 1 modules:
calculator: add, multiply, calculate_tax
Discovering middlewares...
Found middlewares for 1 agents:
assistant: before, after
Loading agents...
Found 3 agents:
āā assistant [LLM]
ā Description: A helpful assistant with calculator tools
ā Model: gemini/gemini-2.5-flash
ā Tools: calculator.add, calculator.multiply, calculator.calculate_tax
āā
āā tax-calculator [Tool]
ā Description: Calculates tax directly
ā Tool: calculator.calculate_tax
āā
āā document-pipeline [Sequential]
ā Description: Processes documents through extraction and validation
ā Chain: assistant ā invoice-processor
āā
ā Project validation completeA misspelled tool reference, invalid YAML, or missing middleware appears immediately instead of after uploading.
connic dev - Hot Reload Development
A development session syncs local files to an isolated cloud runner. After a file is changed and saved, it is live in 2-5 seconds without a manual upload.
$ connic dev
Watching for file changes...
Press Ctrl+C to stop
āāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāā
View and trigger your agents: https://connic.co/projects/...
āāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāā
[14:32:15] Detected change: assistant.yaml
[14:32:16] Files changed, uploading...
[14:32:17] Uploaded 2,847 bytesThe CLI watches agents/, tools/, middleware/, and requirements.txt. Connector tests in the dashboard reflect code changes within seconds.
connic deploy - CLI Deployment
Deploy from a terminal or CI/CD pipeline without going through the dashboard.
$ connic login # Save credentials
$ connic deploy # Deploy to default environment
$ connic deploy --env <id> # Deploy to specific environmentWith Git integration, a repository push deploys automatically. The normal workflow does not require the CLI.
New: Import Predefined Tools
Alongside the SDK, predefined tools can now be imported into custom tools. This supports building on top of capabilities like semantic retrieval, web search, or agent orchestration directly from Python code.
from connic.tools import retrieval_query, retrieval_store
async def lookup_and_summarize(query: str) -> str:
"""Search the retrieval and return a summary."""
# Use the predefined retrieval tool
results = await retrieval_query(
query=query,
namespace="documents",
top_k=5
)
# Process and return the results
if not results:
return "No relevant information found."
return "\n".join([r["content"] for r in results])Previously, predefined tools could only be used directly by agents. They can now be composed into richer tool logic: query retrieval, process the results, make decisions, return exactly the required output.
Get Started
The SDK is available now. Existing Connic YAML configurations and Python tools continue to work unchanged, with the new tooling around them.
$ pip install connic-composer-sdk
$ connic init my-agents # Or use with your existing project
$ cd my-agents
$ connic lint # Validate everything locally
$ connic dev # Start hot-reload developmentThe quickstart guide provides a complete walkthrough, and the SDK documentation contains the full reference.