seisei_flutter_intents

Flutter runtime bridge for Seisei app actions and generated App Intents.

This package keeps the runtime bridge optional. seisei_intents remains the pure Dart contract, generated Swift App Intent source still lives in host-owned native targets, and this package only supplies the Flutter method-channel surface used when a running Flutter engine should handle those native calls.

final runtime = SeiseiFlutterIntentsRuntime(
  actions: const [
    AppActionDefinition(
      id: 'open_note',
      title: 'Open Note',
      description: 'Open a note in the host app.',
    ),
  ],
  handlers: {
    'open_note': (invocation) async {
      return AppActionResult(value: {'opened': invocation.arguments['note']});
    },
  },
  entityQueryHandlers: {
    'note': (query) async {
      return const [
        AppEntityResolution(id: 'note-1', title: 'Roadmap'),
      ];
    },
  },
);

await runtime.attach();

The default runtime capabilities are toolCalling and systemIntentDiscovery. Add AppActionCapability.backgroundExecution only when the host has explicitly provided the app or extension lifecycle needed for background App Intents execution.

Native Apple code should invoke the channel dev.jha.seisei/seisei_flutter_intents with:

• capabilities
• listActions
• invokeAction
• resolveEntityQuery

On iOS and macOS, native hosts that include Flutter can use SeiseiFlutterIntentsEngineHost to start and retain a headless Flutter engine before forwarding App Intents calls. On iOS, the helper uses the public FlutterEngine headless execution APIs; on macOS, it uses the matching FlutterMacOS APIs.

import FlutterPluginRegistrant
import SeiseiAppleIntents
import seisei_flutter_intents

let host = SeiseiFlutterIntentsEngineHost(
  pluginRegistrant: { registry in
    RegisterGeneratedPlugins(registry: registry)
  }
)

SeiseiFlutterIntentsDependencies.configure { method, arguments in
  try await host.invokeMethod(method, arguments: arguments)
}

Use a custom entrypoint only when the Dart function is annotated with @pragma('vm:entry-point'). iOS hosts can also pass libraryURI, initialRoute, and dartEntrypointArguments when their app architecture needs them. Host apps and extensions are still responsible for including the Flutter assets, generated plugin registrant, entitlements, and background execution policy required by their target.

This package does not dynamically register App Intents and does not guarantee that a Flutter engine is available from every App Intents execution context. Host apps still own their Swift AppIntent source and foreground/background execution policy.