Sessions

A session is the unit of execution in nebflow: one conversation between you (or a dispatcher) and an agent, with tools attached. One entry is enough — hand it a complex, long-running task and it carries the work through to a delivered result.

This page is a preview skeleton — detailed content is being expanded.

What a session is

• One agent, one conversation, one task
• The tool face is fixed by the engine, per role; plugins attach knowledge and resources, not tools
• Each session starts fresh: state lives in files and memory, not in the session itself

The single-delivery discipline

• A session owns its task end to end and finishes with a deliverable final message — not a handoff note
• The last message of a session is its result; callers consume it as the outcome

Long-running work

• Sessions keep working for hours on multi-step tasks without human intervention
• Long contexts are managed automatically, so work continues past the context window