[Docs feedback]: Features
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 15/100
- Issue type
- Documentation
- Clarity
- Needs clarification
- Activity status
- Active
- Domain
- documentation
Research direction
The report concerns the Features page at https://docs.openwebui.com/features/, but the payload does not name the source file for that page. Before editing, a maintainer needs to decide which of the listed items are documented behaviour and which are product feature requests that do not belong in the docs. The issue has no comments or assignee, so confirm the scope with a maintainer first.
Written by the indexing model from the issue text.
Description
Page title
Features
Page URL
https://docs.openwebui.com/features/
What needs improvement?
Missing information
What went wrong?
Hello
Feature request regarding automation
- Lauch automation in existing chat
- Organize automation by folder or add fields to filter automation by catergoy in the UI
Feature request regardin subagents
- possibility to select another subagent than the main -> in order to distribute different works by agents capability
- preflignt check allowing main agent to verify tools, knowledges, skills atached to subagent and confirm readiness for a complex task
- possibility to recover chaid_ID and continue or review a subagent work with the same session (allowing continuity of context and batching token
- possibility to have an activity dashbord seeing active and finished session in the UI
Many thanks for your job, he tool is already amazing!
Open WebUI version (optional)
12.4
- Dominant language
- JavaScript
- Stars
- 916
- Forks
- 638
- Avg merge
- 17h 40m
- Merged PRs (30d)
- 19
Getting set up
- No Dockerfile or Docker Compose file
- Has a pull request template
- Read the contributing guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from open-webui/docs
-
documentation
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
open-webui/docs#1500 ·
Maintainers usually reply within 1 day
-
Docs: the backups page lists cache/ as data to back up - on a fresh instance it is 99.9% of the backupPossibly taken @spelingbee claimed this 64 days ago. Open
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
open-webui/docs#1378 · 1 comment ·
Maintainers usually reply within 1 day
-
Add Reference Architecture Diagrams & Component OverviewMay be free again @er-s-an claimed this 86 days ago, and no pull request is open. Open
Difficulty 5/5 Over a week Newbie friendliness 35/100
open-webui/docs#1194 · 1 comment ·
Maintainers usually reply within 1 day
-
Difficulty 4/5 3-5 days Newbie friendliness 35/100
open-webui/docs#868 ·
Maintainers usually reply within 1 day
-
Difficulty 4/5 3-5 days Newbie friendliness 35/100
open-webui/docs#867 ·
Maintainers usually reply within 1 day
Similar issues
-
Waiting for: Product Owner
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
getsentry/sentry-javascript#26203 · 1 comment ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
Maintainers usually reply within 1 day
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
bytedance/flowgram.ai#1235 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
Maintainers usually reply within 2 days
-
desktop v3 windows
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
esengine/DeepSeek-Reasonix#15016 · 1 comment ·
Maintainers usually reply within 1 day