[BUG] [v0.0.7] cortex resume --last shows redundant --last flag in Quick Start

[bluecatdev333]

Project

cortex

Description

In the Quick Start section of cortex --help, the command is displayed as:
cortex resume --last
However, cortex resume already defaults to resuming the most recent session, so the --last flag is redundant and unnecessary. This could confuse users or make the documentation look outdated.

Error Message

Debug Logs

System Information

OS: Ubuntu 22.04 (as shown in the screenshot)
Cortex version: 0.0.7

Screenshots

Steps to Reproduce

1. Run cortex --help.
2. Scroll to the Quick Start section.
3. Observe that the cortex resume --last command is listed.

Expected Behavior

The Quick Start should display cortex resume without the --last flag, since it is the default behavior.

Actual Behavior

The help shows cortex resume --last, which is redundant.

Additional Context

Removing --last will make the documentation clearer and prevent confusion for new users.

[echobt]

The bug report correctly identifies that cortex resume --last is shown in the Quick Start section of the help output, but the --last flag is redundant because cortex resume defaults to resuming the most recent session anyway.

I verified this in the codebase:

1. In src/cortex-cli/src/cli/styles.rs, the AFTER_HELP constant explicitly lists:

    <green,bold>cortex resume --last</>           Continue most recent session

2. In src/cortex-cli/src/cli/handlers.rs, the run_resume function handles the ResumeCommand. When no arguments are provided (None, false, false), it defaults to the most recent session:

        (None, false, false) => {
            let sessions = cortex_engine::list_sessions(&config.cortex_home)?;
            if sessions.is_empty() {
                print_info("No sessions found. Use 'cortex' to start a new session.");
                return Ok(());
            }
            sessions[0].id.clone()
        }

This confirms that cortex resume without any flags behaves exactly the same as cortex resume --last (which hits the (None, true, _) match arm and also returns sessions[0].id.clone()). Therefore, the --last flag in the Quick Start documentation is indeed redundant and could be confusing. The issue is valid.