Chatbot — Direct Mode
Direct AI chat, built to keep the thread intact.
Chatbot is Sparse Halo's fast path for work that should stay conversational. You can switch models mid-thread, keep the current exchange grounded in one live session, and avoid turning every useful interaction into a permanent cloud timeline by default.
Chatbot is the default workspace entry. Cabinet stays available when the prompt needs structured multi-agent pressure.
Default entry
Chatbot opens first
The main workspace starts in direct mode for the fastest path in.
Switching rule
Future replies only
Changing models updates what happens next, not what already happened.
Session model
Temporary by default
Keep the active thread in the tab, or save locally only when you choose.
Product Spotlight
The direct mode is designed around reply continuity, not theatrical process.
Chatbot should feel like a sharp instrument: quiet enough to stay inside the thought, flexible enough to shift models, and clear enough to show exactly what changes when you do.
GPT-5.4 Mini
Here is a cleaner version with less launch jargon, more control, and a steadier opening rhythm.
Earlier turns stay exactly as written. Only the next response changes voice and capability.
Claude 4.6 Sonnet
I tightened the cadence, preserved the confidence, and removed the parts that felt over-produced. Here is the revised version.
Model changes stay clean
Sparse Halo lets the thread keep its shape while the next answer changes voice or capability.
Privacy is the starting state
The thread is not treated as a permanent cloud archive. Local history stays opt-in and device-bound.
Cabinet stays one step away
When the prompt needs more pressure than a direct thread should carry, move into the structured mode deliberately.
Compare with CabinetWhy Chatbot Exists
Chatbot is not the lite version of Cabinet. It is the direct mode for work that should stay conversational.
Some prompts need pressure, multiple viewpoints, and formal synthesis. Others just need a clean thread, a fast answer, and the ability to steer the next reply without losing continuity.
That is the job Chatbot is built to do. It keeps the surface lighter than Cabinet on purpose, so the attention stays on the evolving exchange rather than on managing a process.
If the question outgrows that direct shape, Sparse Halo gives you a deliberate escalation path instead of blurring both modes into one confused interface.
Two modes, two jobs
Chatbot
Best for ongoing back-and-forth, quick reframing, edits, debugging, and direct iteration inside one thread.
Cabinet
Best for prompts with real tradeoffs, hidden assumptions, or execution complexity that benefit from structured challenge.
Key Capabilities
The direct mode stays simple on the surface, but it is deliberate underneath.
Continuity over reset
Chatbot is built for follow-ups, rewrites, debugging, and all the work that depends on staying inside one live thread.
Switch the next reply
Move between models mid-thread without flattening the conversation. Earlier turns stay intact while future replies take on the new model.
Temporary by default
The default session model is transience, not a growing permanent timeline tied to your account.
Local-only saving
When you decide something matters, you can keep it locally on your own device instead of treating persistence as an automatic product assumption.
Calm interface pressure
Chatbot keeps the surface flatter than Cabinet on purpose so reading, replying, and iteration stay visually quiet.
Multi-provider range
The direct mode still benefits from Sparse Halo's wider model bench, so switching perspective does not require leaving the thread.
Workflow Story
A product demo in four moves.
Chatbot is strongest when the interaction should stay fluid. The thread carries the work forward, and the system only adds more structure when the task actually earns it.
Ask directly
Start with the problem in its raw form. No panel setup, no staged orchestration, no extra ceremony before the first answer.
Tune the next reply
If you want a different style or capability, switch models for what comes next. The thread stays coherent because the earlier turns do not get rewritten.
Keep the thread alive
Follow up, edit, debug, and reframe without losing context. Chatbot is optimized for continuity, not theatrical process.
Escalate only when needed
When the task stops being a conversation problem and starts needing pressure, structure, or synthesis, move into Cabinet on purpose.
Deliberate escalation
When the prompt stops being a conversation problem, do not force Chatbot to become Cabinet. Move into the structured mode deliberately.
Open the workspace in its direct mode and stay inside the thread.
Chatbot is the fastest way into Sparse Halo: one live thread, deliberate model switching, temporary-by-default privacy, and a clear escalation path when the prompt needs more structure than direct conversation should carry.