You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
@@ -243,6 +244,7 @@ hotdata sessions <session_id> run <cmd> [args...]
243
244
-`list` shows all sessions with a `*` marker on the active one.
244
245
-`new` creates a session and sets it as active.
245
246
-`set` switches the active session. Omit the ID to clear the active session.
247
+
-`read` prints the markdown content of the current session.
246
248
-`update` modifies the name or markdown of a session (defaults to the active session).
247
249
-`run` runs a command with the hotdata CLI sandboxed in a session. Creates a new session unless a session ID is provided before `run`. Useful for launching an agent that can only access session data. Nesting sessions is not allowed.
@@ -295,6 +296,7 @@ hotdata sessions <session_id> run <cmd> [args...]
295
296
-`list` shows all sessions with a `*` marker on the active one.
296
297
-`new` creates a session and sets it as active. Blocked inside an existing session.
297
298
-`set` switches the active session. Omit the ID to clear. Blocked inside an existing session.
299
+
-`read` prints the markdown content of the current session. Use this to retrieve session state at the start of work or between steps.
298
300
-`update` modifies a session's name or markdown. Defaults to the active session if no ID is given. The `--markdown` field is for writing details about the work being done in the session — observations, intermediate findings, next steps, etc. This state persists for the life of the session and is the primary way to record context that should survive across commands or agent invocations within the session.
299
301
-`run` launches a command with `HOTDATA_SESSION` and `HOTDATA_WORKSPACE` set in the child process environment. Creates a new session unless a session ID is provided before `run`. Blocked inside an existing session.
300
302
- When inside a session (HOTDATA_SESSION is set), all API requests automatically include the session ID — no extra flags needed.
0 commit comments