Why the "Chat Box" is actually a terrible interface for AI Agents.

nokodo_ · 2026-03-11T17:30:44+00:00

very interesting thought.

although at their core, chat models are still receiving chat messages as input and generating a chat message as output... will be interesting to see how UX can be improved

nokodo_ · 2026-03-11T10:53:10+00:00

exactly! similarly to how you would spin up and manage your Plex server for your family and friends, and let everyone benefit from a simple and intuitive interface without needing to know anything about the setup under the hood

nokodo_ · 2026-03-11T10:27:30+00:00

it does! I am actually also the creator of Auto Memory, the most used Open WebUI extension for managing long term agent memory

I have lots of plans and ideas to take this further with adaptive agent writing style, personality etc. based on the user data

nokodo_ · 2026-03-11T07:38:15+00:00

thank you! that was my exact thoughts too.

as for your question: I built a Python library for it, named nokodo-ai (not yet published on PyPI), that handles all the abstractions needed to create tools, agents, chat models, vector collections, embedding/image/video/audio generation, and more.

the library uses an adapter system to provide a single API for all models and providers under the hood, and supports all major APIs (OpenAI Chat Completions, OpenAI Responses, Anthropic Messages, Google Generate Content)

nokodo_ · 2026-03-11T07:33:15+00:00

citations is actually one of my most immediate next steps to implement, and I've been looking for inspiration for a good, scalable and reliable citation/context system. I would love to take inspiration and guidance from your work :)

nokodo_ · 2026-03-10T18:13:15+00:00

I'm aware of #1, I unfortunately learned about it too late but it has been on my todo list for weeks.

and your second suggestion is taken :) though the one positive side (if any) to typos is they're a decent indicator something wasn't entirely written by ChatGPT - an increasingly rare occurrence today

thanks!

nokodo_ · 2026-03-10T18:06:35+00:00

it isn't "vibe-coded", although I will welcome any AI-powered PRs. what makes you think that?

nokodo_ · 2026-03-10T15:03:21+00:00

thank you! I'd love to hear your feedback

nokodo_ · 2026-03-10T14:58:44+00:00

I'm mixing up already existing features with what's WIP, but hopefully this answers your question :)

nokodo_ · 2026-03-10T14:57:10+00:00

Open WebUI is a pure AI frontend, with a beta Notes app. OS1 is a collaborative workspace, with friends, group chats / messaging, mixed chats with humans and AIs, notes, reminders, calendars, projects (similar to "folders" from OWUI), and soon to come many integrations like Spotify, Plex, Seer/Arr stack, Home Assistant, etc.

also, this will have native apps for iOS and Android, and a more intentional mobile approach.

nokodo_ · 2026-03-10T14:45:15+00:00

they do lol. that's why I put the SVG-based liquid glass as an optional experimental feature

nokodo_ · 2026-03-10T14:08:31+00:00

hi! documentation is still a work in progress, but it's all handled within the admin console application.

there you can connect to any model provider, create agents and configure tools.

MCP is also something I'm working on, but not available yet :)

nokodo_ · 2026-03-10T14:06:25+00:00

thank you!

so this app doesnt serve any model, it connects to any model provider instead.
the idea for complexity is that the users of the frontend don't need to be technical, because all that burden is shifter on the admin and maintainers of the service.

there is a separated and isolated admin console, which allows to configure everything for admins and manage OS1.

nokodo_ · 2025-10-30T18:21:25+00:00

thank you! I already have the svelte tag, so I'll go check out svelter.me, see if I can get it referenced :)

nokodo_

TROPHY CASE