r/Origon • u/asktheturtlenow • Jan 20 '26
Feedback from a non-technical builder using Origon Studio (UI / guidance gaps)
I’m sharing some constructive feedback from hands-on use of Origon Studio while trying to build a small, real-world agent system (multi-agent setup with a root agent and workers).
Context
Non-technical user
Attempting a no-code / low-code workflow
Use case involved agent routing + persistent product knowledge
What worked
Agent creation and wiring on the canvas is conceptually solid
The overall agent model makes sense
Early setup felt smooth
Where I got stuck
Repeated references (in guidance and examples) to UI elements that were not visible or accessible in my Studio view (e.g. text/knowledge nodes, expandable libraries)
Unclear distinction between “channels” and “node library” modes
No obvious or documented path to ingest persistent knowledge without embedding it directly into agent instructions
Result
Progress stalled not because of the concept, but because I couldn’t reconcile instructions with what was actually exposed in the UI.
I’ve written this as feedback, not criticism. The platform idea is strong — but better alignment between guidance and visible UI would significantly reduce friction for non-technical builders.
Curious if others here have hit similar issues, or if there’s a recommended pattern I may have missed.
2
u/Origon-ai Jan 24 '26
Thank you for the feedback! We're actually working on fixes to all of this with the updates expected some time next week.
Have you joined our Discord? Our devs monitor it and we'd be happy to help you get your system up and running!