create_agentic_app 0.2.0

Generates a working Flutter AI agent app: a chat screen, tools, human approval, a live trace panel, and an API key kept out of the source.

Changelog

0.2.0

• The template passes approvalHandler: to ToolCallingAgent directly, and its README explains isReadOnly after untrusted content and points to @ToolFunction, agentic_sqlite, RagStack and agentic_test.
• --framework-path also writes pubspec_overrides.yaml, pointing every sibling package at the same working tree. A path to agentic_flutter alone compiled it against the siblings on pub.dev, so a change spanning two packages failed in a generated project and nowhere else.

0.1.1

• Added example/, which the package had been missing. Most people meet this package as a command, so the library underneath went undocumented — and it is the half that matters for anyone scaffolding several projects, testing what the template emits, or generating from these files and then adding their own.
• Shortened the package description to the 60-180 character window search engines and pana both work in.

0.1.0

Initial release.

Added

• create_agentic_app <name> — generates a Flutter project built on the framework: a chat screen, an agent with three tools, human approval for the one that changes something, a live trace panel, and four tests that pass offline.
• Demo mode — the generated app runs against a scripted model before any key exists, so the first run shows an app rather than an error about credentials.
• Providers — --provider=openai|anthropic|gemini|ollama wires the right adapter, key name and settings copy.
• Name validation — hyphens, capitals, reserved words and a collision with the framework's own package names are refused before anything is written, with the closest legal name suggested. Each of those otherwise fails later, from pub, with a message about a pubspec the user did not write.
• --framework-path — depends on a local checkout rather than a published version, which is how CI generates a project and compiles it.
• Nothing is written unless everything can be — a half-generated project is worse than none, because flutter run then fails for a reason unrelated to the real problem.

Notes

The package has no dependencies. It writes files; it does not use the framework — which is what lets it be installed before the framework is published.

Platform folders are not generated. flutter create . produces them correctly, and a template carrying its own Gradle and Xcode boilerplate ships a stale toolchain to everyone who runs it.