Starweaver
Starweaver is a Rust agent SDK for local-first agent products. It combines a typed SDK facade, a deterministic runtime loop, provider-neutral model and tool contracts, structured output, durable session evidence, first-party environment tools, and a CLI surface.
Use it when you want application code to own the runtime contract instead of hiding the agent loop behind provider-specific request formats.
flowchart LR
app["Application or CLI"]
agent["starweaver-agent"]
runtime["starweaver-runtime"]
model["starweaver-model"]
tools["starweaver-tools"]
context["starweaver-context"]
ops["session, stream, storage"]
app --> agent
agent --> runtime
runtime --> model
runtime --> tools
runtime --> context
runtime --> ops
What you can build
- SDK agents with static and dynamic instructions.
- In-process Python agents and Python tool injection over the Rust runtime.
- Provider-neutral model integrations and deterministic test models.
- Typed function tools, toolsets, MCP-backed tools, and host-backed tools.
- Structured JSON output with typed parsing and validation retry.
- Multi-turn sessions with
AgentContext, usage, dependencies, notes, and resumable state. - Subagent registries for application-owned delegation.
- Durable runtimes with checkpoints, display streams, replay records, and SQLite adapters.
- Local CLI workflows with profiles, launcher dispatch, install/update, and display JSONL.
Learning path
- Install: install from release artifacts or run from source.
- Quickstart: build and run your first agent.
- Agent SDK: understand the SDK surface and crate boundaries.
- Python SDK: inject Python tools into the same runtime.
- Python Tools: add in-process Python tools and toolsets.
- Python Examples: run complete Python examples.
- Tools: add Rust typed function tools and toolsets.
- Structured Output: return JSON with schemas and typed parsing.
- Session and Stream Contracts: integrate durable product surfaces.
- Release: prepare and publish Starweaver releases.
Stability
The public surface focuses on SDK foundations, deterministic testing, tool/runtime contracts, local CLI workflows, and release automation. Some host integration surfaces are intentionally explicit: live external resources, product-specific service transports, and hosted platform adapters remain integration points rather than hidden defaults.