Pre-release (
0.2.xtrain) — Highly experimental. APIs may change without notice. Not for production. See PRE_RELEASE.md.
Register intents. Call them everywhere.
Transport-agnostic agent intent platform for Dart/Flutter: define intent truth once in AgentRegistry, then project it into the strongest available surface: MCP/WebMCP, native action metadata where supported, assistant/shortcut fulfillment, and canonical deep-link fallback where native support is incomplete. Extracted from mcp_flutter.
Charter: docs/NORTH_STAR.mdx · Agent map: AGENTS.md · Docs site: docs.page/Arenukvern/intentcall
Why / how: docs/DESIGN_FAQ.mdx · docs/DX_FAQ.mdx · Decisions · CONTRIBUTING.md
GitHub: Arenukvern/intentcall
| Repo | Role |
|---|---|
| IntentCall (this repo) | Platform layer — registry + adapters |
| mcp_flutter | Product harness — mcp_toolkit, flutter-mcp-toolkit CLI |
| Skill Steward | Meta-layer — agent skills governance |
| Package | Role |
|---|---|
intentcall_schema |
Wire types, validation, AgentResult |
intentcall_core |
Registry, runtime, AgentCallEntry, and neutral tool/resource registration vocabulary |
intentcall_session |
Runtime session lifecycle, persisted session state, snapshots, and registry execution inside a session |
intentcall_mcp |
MCP publish adapter and MCP mapping (dart_mcp) |
intentcall_webmcp |
WebMCP hot-sync adapter |
intentcall_platform |
Native/web emitters, protocol fallback artifacts, and Flutter plugin |
intentcall_codegen |
Optional @AgentTool codegen |
intentcall_testing |
Contract / invoke test helpers |
intentcall_gemma / intentcall_apple / intentcall_android |
Optional experimental surface adapters |
Platform support is tiered during the 0.2.x train: current code covers MCP, Dart-first WebMCP registration, Apple App Intents dispatch wrappers, Android shortcuts/deep links, Windows protocol activation, and Linux x-scheme-handler. Apple App Intents currently launch/wake the app and dispatch an invocation envelope for Dart execution; they do not claim app-extension-hosted Dart execution or native background business logic. Android AppFunctions, Android App Actions capabilities, Windows App Actions / Agent Launchers, and AAIF ecosystem alignment are roadmap targets unless documented otherwise.
We provide custom agent skills to assist in developing with and extending IntentCall:
| Skill | Description | Install command |
|---|---|---|
| register-intents | Guide to manual and codegen intent registration. | npx skills add Arenukvern/intentcall --skill register-intents |
| write-adapter | Guide to implementing custom platform/transport adapters. | npx skills add Arenukvern/intentcall --skill write-adapter |
Repository management is guided by Skill Steward meta-skills (installed in .agents/skills/).
dart pub get
just test
just analyze
just publish-dry-run # pub.dev dry-run (all packages)Release maintainers use Release Please. Merging the release PR creates package tags; tag-triggered GitHub Actions publishes through pub.dev automated publishing.
See docs/DX_FAQ.mdx for detailed workflows.
This repository starts with a fresh history (2026-05-28). Packages were developed inside mcp_flutter until Phase 7 extract; git filter-repo / subtree split was deferred to avoid timebox risk. Use mcp_flutter git log before the extract commit for prior package history.
App authors should prefer mcp_toolkit + flutter-mcp-toolkit CLI. IntentCall packages are for platform work and advanced integration.
See CONTRIBUTING.md. All PRs must pass just test && just analyze && just publish-dry-run.
See PUBLISHING.md. The normal path is Release Please merge -> tag-triggered GitHub Actions publish; manual publish commands are recovery-only.