Skip to content

Conversation

@lsvishaal
Copy link
Contributor

🚀 Describe your changes clearly

Adds a notification system for long-running tasks with:

  • long_running flag in MessageSendConfiguration to indicate tasks expected to run beyond typical timeouts
  • Global webhook fallback via global_webhook_url and global_webhook_token fields in AgentManifest
  • Persistent webhook configs that survive server restarts (stored in DB)
  • Artifact notifications so clients get webhook updates when new artifacts are produced
  • Alembic migration for the new webhook_configs table

The push notification manager now:

  1. Loads persisted configs on startup
  2. Falls back to global webhook when no task-specific one exists
  3. Supports artifact events alongside status updates

✅ Checklist

  • I've tested my changes thoroughly (18 new tests + full suite passes)
  • I've followed the project's style and linting rules
  • I've updated documentation (added .bindu/issues/69-long-running-notifications/README.md)

📌 Related issue

Closes #69

- Add long_running flag to MessageSendConfiguration
- Add global_webhook_url/token to AgentManifest for fallback
- Add webhook persistence to Storage interface (InMemory + Postgres)
- Create webhook_configs table with Alembic migration
- Enhance PushNotificationManager: persistence, global fallback, artifact notifications
- Add 18 unit tests covering all new functionality"
…task integration

- Implement artifact notification hooks in ManifestWorker
- Integrate long_running flag in MessageHandlers for persistent webhook registration
- Wire PushNotificationManager across TaskManager components
- Add integration tests for end-to-end notification pipeline
…th flexible configuration and comprehensive E2E tests and fixed

-discardation of push notifications by add_extension_to_capability() fn
-serialization of UUIDs by adding a helper function
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

[Feature]: Notification

1 participant