"Micro-kernels" and "bridges"

[Keyrxng]

There exists one already kernel-telegram and there is going to be another.

• Perhaps it makes sense to standardize an approach for building these micro-kernels, maybe some docs too? Such as: If APP_PRIVATE_KEY is a useable org secret then the micro-kernel should be a worker first and dispatch it's own workflows, if both are required. (I'd advocate for that, prevents multi config entries, etc.)
• A few off-the-cuff suggestions have been made regarding possibilities: Gmail, Slack, etc...
• I doubt any are business priority right now but some ideas that come to mind for me are:

1. Discord
2. X
3. Medium (or some other blogging platform)

[EresDev]

Interesting points. My usual approach is to try with GitHub action/workflow first. If it is not possible then the worker can be considered. I feel we are going to talk to GitHub anyway, as the nature of our product, so why not host it here?

You should know that it is my first plugin, so I am not sure where will I get stuck as far as permissions are concerned.

If I write a worker, I assume I will have to ask the user who hosts the personal-agent plugin, to provide us with access tokens. But if it is a workflow, just adding the UbiquityOS to their personal-agent plugin may just do the job. These are just my ideas right now, I could be wrong. The work is in progress.

Moreover, the job of personal-agent-bridge is simple. Pass the comment to correct user's workflow. So, having a worker for this sounds like an overkill to me unless we hit some limitations.