Pre-release train — Contract-tested pre-1.0 platform infrastructure. APIs may change without notice. Not for production claims without app/runtime proof. See PRE_RELEASE.md.

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.

Live Demo with Flutter MCP Toolkit and Grok Build

Conceptual map: write one Dart intent, register it once, project it to useful surfaces, then people and agents use it.

Start here: How it works · Choose your path · Platform support · Roadmap

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
Contribute: guide · contributors · security

GitHub: Arenukvern/intentcall

Ecosystem

Repo	Role
IntentCall (this repo)	Platform layer — registry + adapters
mcp_flutter	Early consumer and product harness — mcp_toolkit, flutter-mcp-toolkit CLI
Skill Steward	Meta-layer — agent skills governance

Published Packages

Package	Pub.dev	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_apple		Apple manifest projection for App Intents / Shortcuts dispatch artifacts and first typed-entity/indexing direction
intentcall_android		Android manifest codegen for shortcut and deep-link artifacts
intentcall_platform		Native/web emitters, protocol fallback artifacts, and Flutter plugin
intentcall_codegen		Optional @AgentTool codegen
intentcall_testing		Contract / invoke test helpers

intentcall_gemma is example-only and intentionally unpublished. intentcall_cli is the workspace maintainer tool and is not part of the hosted package train.

Platform support is tiered during the current pre-1.0 train: current code covers contract-tested MCP adapters, Dart-first WebMCP emitter/bootstrap helpers, Apple App Intents dispatch wrappers plus explicit main-app Swift nativeInline handlers, typed primitive App Intents return generation for Apple inline runtimes, an experimental Apple dartExtensionInline scaffold, Android shortcut/deep-link artifacts, Windows protocol activation artifacts, and Linux x-scheme-handler artifacts. L3 adds an additive actions/entities/indexing direction: Dart owns snapshots and behavior, while Apple is the first projection that can read a durable native cache when Flutter is cold. Generated schemas, artifacts, native cache rows, and storage helpers are not live Spotlight, Siri, Shortcuts, donation, indexing, or product proof. Android AppFunctions, richer Android App Actions capability generation, Windows App Actions / Agent Launchers, and AAIF ecosystem alignment are roadmap targets unless documented otherwise. See Platform support for evidence levels and non-claims.

Agent Skills

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/).

Development

Human local setup:

dart pub get
just test
just analyze
just publish-dry-run   # pub.dev dry-run (all packages)

Agent/operator first run:

steward doctor --json
steward actions list --json
steward action inspect intentcall.validate --json
steward action inspect intentcall.adapter-contract-test --json
steward probe --json --profile quick
steward benchmark --scenario intentcall.adapter-contract --json

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.

Development Support

Need	Start here
Contribute code or docs	CONTRIBUTING.md
Add or credit contributors	Contributors guide · .all-contributorsrc
Report vulnerabilities	SECURITY.md
Validate local changes	steward probe --json --profile quick · steward benchmark --scenario intentcall.adapter-contract --json
Maintain releases	PUBLISHING.md · Release Please workflow
Build with the Flutter harness consumer	mcp_flutter

Git history

This repository starts with a fresh history (2026-05-28). IntentCall originated during early mcp_flutter proof work, and earlier package history remains in the mcp_flutter git log. The reusable registry, adapter, session, and platform-projection contracts are now owned here; mcp_flutter remains an early consumer and proof harness.

Flutter App Harness

Flutter app authors who want the packaged product harness should start with mcp_toolkit and the flutter-mcp-toolkit CLI. IntentCall packages are the reusable platform layer used by that harness and by other adapters, CLIs, servers, and platform bridges.

Contributing

See CONTRIBUTING.md. All PRs must pass just test && just analyze && just publish-dry-run.

Contributors ✨

Thanks to everyone helping shape IntentCall.

This roster is maintained with all-contributors. To add someone, update .all-contributorsrc and regenerate the README table, or use the all-contributors bot/CLI from a PR. More detail: docs/contributing/contributors.mdx.

Anton Malofeev 💻 📖 🚧 🚇

Publishing

See PUBLISHING.md. The normal path is Release Please merge -> tag-triggered GitHub Actions publish; manual publish commands are recovery-only.