deepseek-harness-genui

What it solves

• Complex relationships, multi-step choices, and interactive exploration are hard to express in plain text.
• Generative UI systems often rely on fixed component catalogs, limiting task-specific structures.
• User selections and inputs in generated interfaces do not naturally flow into the next Agent turn.

Who it’s for

• Developers and users of DeepSeek Harness.
• Scenarios that need temporary interactive interfaces (calendar selection, model exploration, code-path tracing, etc.).
• Automation flows that want frontend state to persist as task state for the next Agent turn.