Skip to content

When running cmd in headless mode, do not see (or cannot find) session jsonl info in global project directory for later review #391

@dthyresson

Description

@dthyresson

Summary

I am running cmd in headless "-p" mode, specifically with cmd --yolo --skip-onboarding -m deepseek-v4-flash --max-turns 100 -p and my prompt.

Because the -p mode will output the result to console, I can't read/review what it did.

Expected Behavior

I was hoping it would store like interactive sessions do in the ~/.commandcode/projects for the project in which the interactive session ran.

I could see in the -p case it may or may not be in a "project" per se, but in my case I am cwd into a project directory, so I do want it to think that it is running in that project.

Or - perhaps could provide an option to the -p mode to explicitly store sessions in a directory of choosing or an existing project.

Ultimately, my goal is to be able to log and review the session output of what the -- headless "session" did.

Actual Behavior

No session info stored in command code's project directory

Steps to reproduce the issue

Run cmd in -p mode. In an en existing project directory. Look for session jsonl files.

Command Code Version

0.26.23

Operating System

macOS

Terminal/IDE

ghostty

Shell

zsh

Additional context

No response

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No fields configured for Bug.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions