V1 features

[Keyrxng]

• Implement /ask #34
• Implement /newtask #32

/ask

Requires embeddings access to enable org-awareness. Should replicate the official plugin as close as possible.

/newtask

Should allow the creation of a new task via Telegram

[0x4007]

I think much more powerful to support inline task creation as well as context aware q&a (command-ask)

Here's a sophisticated inline bot example that generates custom animations.

I think pretty much everything else can be scrapped. It seems like a lot of artifacts from when we had less infrastructure and less clarity on direction.

[Keyrxng]

right so the only feature that needs ported over directly is:

• task creation: processing every comment without admin interaction, is that what you mean? I may misunderstand, the little autocomplete part in the image is the inline part. By directly replying to a message the reply fills that spot. The server update contains both senders etc. Otherwise typing / would fill that spot with commands. Am I to replicate that screenshot, you @ the bot and it offers options/commands that an admin would select?

new features:

• command-ask:

1. context aware as-in, pretty much development right now so global awareness via embeddings at all times?
2. Or if it's a repo forum it should know all about just that repo? Same for workrooms, it should be aware of just that repo and task?
3. When used in big public chats, what's the conversation depth we want to fetch from the chat? The last 20 messages prior to the query or the last 50?

• audio > whisper > task:

1. I will keep it in mind as I build command-ask but needs it's own task, learning curve involved with docs etc.

[0x4007]

I don't think anything will be ported. Inline message seems quite different.

Try and invoke the command-ask as close as possible as it is currently without making much custom adjustments for telegram client. This already can answer org aware questions which is useful. We can focus later on adjusting the prompt to be more useful specifically in telegram context. So for now, no chat context. Just the user's query only.

[Keyrxng]

I don't think anything will be ported. Inline message seems quite different.

I will implement as I first suggested and you can see how it looks and we'll take it from there re: creating new chats from user comments.

Try and invoke the command-ask as close as possible as it is currently without making much custom adjustments for telegram client. This already can answer org aware questions which is useful. We can focus later on adjusting the prompt to be more useful specifically in telegram context. So for now, no chat context. Just the user's query only.

Got it, minimal changes to current structure and the context window is the sysMsg + embeddings search + query.

[ubiquity-os-beta]

A new workroom has been created for this task. Join chat

[rndquu]

I don't understand the long-term vision for this plugin.

Right now it supports sending telegram notifications on:

• permit generated (issue_comment.created)
• inactivity reminder (issue_comment.created)
• forced unassignment (issue_comment.created)
• PR review requested (pull_request.review_requested)

Basically it just duplicates the github functionality, so in addition to github email notifications one will also receive telegram notifications. What's so special about this plugin that can't be achieved via github directly?

[0x4007]

For context, the future vision of UbiquityOS is to span across all major productivity platforms, including but not limited to: GitHub, telegram, google drive, notion.

This is our first step into capturing, processing, and recognizing events that occur on telegram in order to have a more wholistic understanding of how team members are contributing to getting projects done.

Most organizations are not as strict about their communication policy being mainly under the GitHub issue for example. We should try and make UbiquityOS as seamless as possible to add in the background and 1. collect org intelligence and 2. Compensate the top contributors the most.

As you can imagine, traditional organizations have more varied communication channels including the likes of email, slack, zoom, in person. Ideally UbiquityOS should be context aware and understand what projects they are working on, and credit them accordingly for their productive communications related to completing that project.

---

I think the initial setup is the biggest immediate goal here. Then we can start looking into "telegram kernel plugins" to extend its capabilities.

Off hand, I think that it makes sense to:

1. Generate vector embeddings to make the system more intelligent for any command-ask
2. Allow instant task creation in conversation
3. Have a private interface to be able to interact with the system (like setting wallet, queries, label permissions, q&a)

[Keyrxng]

Try and invoke the command-ask as close as possible as it is currently without making much custom adjustments for telegram client. This already can answer org aware questions which is useful.

1. I need the database of embeddings to replicate /ask.
2. Obviously we have no issue context unless it's used within a workroom, so in general groups the only context it'll have is the embeddings.
3. I can build without the embeddings but I'd just be integrating GPT into our TG chats, it's not gonna be like /ask at all.
4. I actually use the /ask plugin; requires changes to it's logic to enable that.

Opened this issue as it's a blocker for implementing the /ask feature.

I'll work on task creation until that is resolved.

[Keyrxng]

PRs for both features ready for review

[ubiquity-os-beta]

Passed the deadline and no activity is detected, removing assignees: @Keyrxng.