Skip to main content

​
Sessions

Sessions represent individual interactions with Claude in the Chucky cloud. Every chucky prompt command and every job creates a session. Use the sessions command to view history, track usage, and access changes made during sessions.

​
List Sessions

chucky sessions [options]

​
Options

OptionDescriptionDefault
-l, --limit <number>Number of sessions to show20
--with-bundleOnly show sessions with git bundlesfalse
--jsonOutput raw JSON responsefalse

​
Examples

List recent sessions: 
chucky sessions
Show only sessions with changes: 
chucky sessions --with-bundle
JSON output for scripting: 
chucky sessions --json --limit 50

​
Output

The sessions list shows: 
abc12345 completed   3.2s   $0.0123 cli-user        [bundle]
def67890 completed   1.5s   $0.0045 cli-user
ghi11223 failed      0.8s   $0.0012 api-user
jkl44556 running     -      -       webhook-user    job:run_xyz789
ColumnDescription
IDFirst 8 characters of session ID
Statuscompleted, failed, or running
DurationTime taken to complete
CostTotal API cost in USD
User IDUser identifier from JWT token
[bundle]Indicates session has file changes
job:...Associated job ID (for background jobs)

​
Session Status

StatusDescription
runningSession is currently active
completedSession finished successfully
failedSession encountered an error

​
Accessing Session Changes

When a session modifies files (indicated by [bundle]), you can fetch and apply those changes: 
# Use the session ID (partial IDs work)
chucky fetch abc12345

# View what changed
chucky diff abc12345

# Apply changes
chucky apply abc12345

# Or do fetch + apply in one step
chucky pull abc12345
See Git Bundles for detailed documentation.

​
Filtering by Project

When run from a directory with a .chucky.json file, sessions are automatically filtered to that project. To see all sessions across projects, run the command from outside any Chucky project directory.

​
Next Steps

Git Bundles

Fetch and apply session changes

Jobs

Create background jobs