Every run of Qoder CLI CN produces a session, recording the full history of that conversation — your inputs, Qoder's replies, and tool calls. Sessions can be continued, resumed, named, branched, and cleaned up, letting you switch flexibly between tasks and pick up where you left off after an interruption.Sessions are stored per project. Each session has a unique session id, and session records are kept in per-project directories under the user config directory (default ~/.qoder-cn/projects/<project>/<session-id>.jsonl).
Running qodercn in the project root starts a new session, with the session id generated automatically:
Copy
qodercn
In an interactive session, use /new to start a fresh session; /clear clears the conversation history and likewise starts a new session — the two are similar in effect.
Use -r (--resume) to resume a previous session by id:
Copy
qodercn -r <session-id>
Running qodercn --resume without an id opens the session browser, letting you pick the session to resume from a list. In an interactive session, the /resume command also opens the session browser; /continue continues the most recent session.
Use --fork-session to create a new branch from a resumed session instead of continuing on the original. This lets you explore a different direction from a historical point while leaving the original session untouched:
Copy
qodercn -r <session-id> --fork-session
In an interactive session, you can also branch from the current session with /branch.
The .jsonl file stores the conversation record, and state.json stores the session state. The user config directory defaults to ~/.qoder-cn and can be customized with the QODERCN_CONFIG_DIR environment variable.
