# Future Directions

Extensions are very much in beta, and still lack a fair number of things to have full potential. Things to be added include:

* Full Stable Bidirectionality and Multimedia: letting an extension request to prompt for image/video/TTS of its own accord rather than being response-only
* Scheduling: Letting an extension exist outside of a chat with some concept of either cronlike scheduling or an activation threshold equation
* Multi-platform: An extension written works on web and mobile out of the box, but it would be better if it could also work across different messaging apps, in VR, etc.
* Other languages/frameworks: React was chosen due to its forgiving learning curve and mass adoption/familiarity to the most people, but it is not some strictly optimal choice. Libraries can trivially be written to support e.g. use with compiled languages through wasm.

Any other thoughts or ideas are very welcome.

Email: <lore@chub.ai>

Telegram: <https://t.me/lore500ng>

Discord: lloorree

Reddit: The [subreddit](https://reddit.com/r/Chub_AI) or /u/Lore\_CH


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.chub.ai/docs/stages/developing-a-stage/future-directions.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
