AgentWeave owns
- Agent turns and event protocols
- Permissions, approvals, and credential storage
- Skill and Connector lifecycles
- Desktop, Android, and Server Hosts
OPEN-SOURCE AGENT APP FRAMEWORK / 0.1.x
AgentWeave weaves conversations, model access, Skills, Connectors, approvals, credentials, persistence, and Hosts into reusable infrastructure. Your team defines the product instead of rebuilding the Agent loop.
THE DIVISION OF WORK
The framework supplies durable boundaries. An Agent App keeps its audience, persona, capability mix, and final interface. Neither has to pretend to be the other.
A SYSTEM, NOT A PERSONA
Compose prompts, packages, themes, languages, and policies through a versioned App Manifest. No core turn-loop fork required.
Declare identity, compatibility, capabilities, and policy in the Manifest.
Combine Foundation Skills, private packages, and providers into a product.
Cover approvals, retries, conflicts, and recovery with fake or local providers first.
Ship through Desktop, Android, or a custom Server Host.
DETERMINISTIC BOUNDARIES
A prompt is never a permission boundary. External side effects, credential access, and durable writes remain under deterministic Runtime and Host control.
High-impact work enters an explicit approval surface before execution.
The Host stores sensitive values and exposes only non-echoing handles.
Durable actions carry scope, version, and duplicate-execution protection.
GOOGLE AUTHORIZATION
AgentWeave Developer Tools by SecondLoop uses Google Desktop OAuth to help developers select or create a project and enable Firebase email login. Authorization tokens remain in local sensitive storage and are not uploaded to SecondLoop servers.
How OAuth data is handled and revokedHONEST STATUS
AgentWeave is still at 0.1.x. It fits prototypes, framework development, and controlled pilots; Manifest, Host API, and Foundation Skill contracts may still change.
Read the full project guide