Tasks and sessions

A session is not merely chat history. It is the container where a task keeps its goal, messages, tool activity, working directory, file results, and follow-up changes.

Start a new task when

• you move to another project or working directory;
• the new outcome is unrelated to the current material;
• you need another agent or runtime;
• an experiment should stay separate from long-running work.

Continue the current session when you are refining its files, asking more questions about the same sources, adding the next step, or relying on decisions already confirmed there.

Session types

NextClaw can host Native, Codex, Claude Code, Weixin, Feishu, and scheduled-task entry points. Their tools and interaction details differ, but each should begin with a clear outcome, working directory, and inspectable result.

Session list

Name work so it is recognizable later. Prefer names such as “July sales analysis” or “Release verification” over a list of sessions called “Hello” or “Test.”

Long context

Sessions keep multi-turn context and can compact long histories. Keep critical paths, final criteria, and non-editable boundaries explicit near the work that depends on them.

Inside a session you can open the workspace, create subtasks, add a scheduled job, or reference a Panel App or skill.