Skip to content

[Feature] A CLI test harness to better test nonInteractiveMode #130

@namar0x0309

Description

@namar0x0309

Description

"A CLI test harness using execa or child_process.spawn would let us test:

Exit codes for non-interactive mode
Timeout/hang detection
Signal handling (SIGINT/SIGTERM)
Piped stdin scenarios" @will-lamerton

Use Case

Describe the problem this feature would solve or the use case it would enable

Proposed Solution

How you envision this feature working

Alternatives Considered

Any alternative solutions or features you've considered

Additional Context

  • I have searched existing issues to ensure this is not a duplicate
  • This feature aligns with the project's goals (local-first AI assistance)

Implementation Notes (optional)

If you have thoughts on how this could be implemented, share them here

Metadata

Metadata

Assignees

No one assigned

    Labels

    enhancementNew feature or request

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions