Welcome to the AionUi Community Discussions!

[IceyLiu]

Welcome to the AionUi Community Discussions!

Hello everyone,

I've just enabled GitHub Discussions for the AionUi project. From now on, this will be the central place for our community members to connect, ask questions, and share ideas.

I've set up this space for a few key purposes:

• Q&A: If you run into a problem or have a question, you can ask it here.
• Ideas: Have a suggestion for a new feature or an improvement? Please share it!
• Show and Tell: Have you built something cool with AionUi? We'd love to see it.
• General: For any other topics related to the project.

A great community is built by its members. Please feel free to start a new discussion or jump into an existing one.

Looking forward to connecting with all of you here!

[mesutde]

Hey team!

As we grow, I’ve been thinking about ways to make our discussions even more organized. What if we added two quick action buttons when starting a new post?

✨ Why this would help:

“Ask Question”: Automatically formats posts with a title, description, and tags (e.g., #bug, #feature-request). Perfect for troubleshooting!
“Share Code”: Adds syntax highlighting and a “Copy Code” button. Great for showing off implementations or debugging snippets.
This would reduce clutter and help newcomers find answers faster. What do you think? Should we prototype this in the next release?

💬 Let’s discuss:

Would you use these options regularly?
Any other actions you’d like to see (e.g., “Show & Tell”, “Idea Pitch”)?

[IceyLiu]

cool suggestion @mesutde. I'm still learning how to operate this section. Let's optimize it together to make it better

[2579463959]

Hi lceyLiu,

I’ve been using AionUI for the past few days, and I’m genuinely impressed—it's powerful and very pleasant to use. I wanted to share a few thoughts and suggestions that came up during real-world usage.

Overall experience

First of all, great work on AionUI. Compared with Moltbot (in my personal experience), AionUI feels easier to use and also more secure.

Ideas & suggestions

1. Multi-user support

Here’s a scenario I’ve been thinking about: if I deploy AionUI (and Codex, which I personally use a lot) on a server, I can access Codex through the WebUI, which is great. But what if I want other people to use the same instance as well?

CLI tools aren’t just for development—they can also be excellent cloud assistants, and they can handle a lot of what Moltbot does. If AionUI supported multiple users, one server deployment could serve multiple people concurrently.

Since the project already has a “workspace” concept, a natural extension might be adding a user layer under each workspace (for example, workspace/<username>/). That would give each user separate configuration and data by default, and make isolation straightforward.

2. Combining with MCP (Windows)

Now that the project supports MCP, I’m wondering: if I install windows-mcp, could Codex perform basic operations on the computer? If windows-mcp becomes more capable (or if you expose more information through it), it might even enable Codex to detect currently running/logged-in applications and help complete workflows that typically require manual actions.

3. n8n integration

If n8n and n8n-mcp are installed, creating and triggering automations becomes much easier. This could enable “scheduled tasks” similar to Moltbot’s automation features with minimal effort.

4. Skills management

It looks like the project may be missing a way to list installed skills. If you could also support one-click skill installation (and ideally updates), it would be extremely convenient. cc-Switch could be a good reference for the UX.

5. Assistant capabilities

The assistant feature is already very useful. We can customize rules and skills, and with MCP it’s like giving the AI a dedicated toolbelt. The only thing it doesn’t have is initiative; otherwise, it’s a very capable assistant.

6. Background mode

Right now, if the app (or terminal) is closed, AionUI exits completely. A background/daemon mode would reduce interruptions caused by accidental closes.

7. Restart / WebUI settings

After each restart, I need to re-open and reconfigure the WebUI settings, which is a bit inconvenient. Persisting these settings would improve the experience.

8. Sending files/images from other devices

When I’m on another computer or on my phone, I can’t send local files or images to Codex in the current setup, which can be limiting in real scenarios.

One possible approach: when a file is uploaded, automatically store it under a folder within the workspace, and show the saved path in AionUI. Since Codex can read files via paths, this might allow Codex (as a CLI tool) to access files sent from other devices. Combined with skills, it could also enable some basic remote collaboration.

9. Per-user memory (optional)

If you plan to add memory, it would be great if it were per-user. One idea is to pass the username to Codex (via assistant rules) and have it query memory-mcp for that user’s stored context.

Issues I ran into (possible bugs)

1. Permission prompts: when I ask Codex to perform actions, it repeatedly asks for permission. Even after clicking “Always allow”, it still prompts me step by step.
2. Mobile WebUI: on mobile web, I can’t see my own messages—only the assistant’s replies—so it’s hard to follow the conversation.

Closing

These are just the things I noticed over the past few days, so I may not have described everything perfectly, but I wanted to share them as soon as possible. If any of these ideas are feasible, I think they could be quite helpful. Thanks for reading, and thanks again for building AionUI.