⚠️ PR Title Format

Your PR title doesn't follow the conventional commit format, but this won't block your PR from being merged. We recommend using this format for better project organization.

Expected Format:

<type>[optional scope]: <description>

Examples:

• feat: add changelog generation support
• fix: resolve login redirect issue
• docs: update README with new instructions
• chore: update dependencies

Valid Types:

feat, fix, docs, style, refactor, perf, test, build, ci, chore, revert

This helps with:

• 📝 Automatic changelog generation
• 🚀 Automated semantic versioning
• 📊 Better project history tracking

This is a non-blocking warning - your PR can still be merged without fixing this.

✅ Review Complete

Code Review Summary

⚠️ AI review failed. Please check the Continue API key and configuration.

Troubleshooting

• Verify the CONTINUE_API_KEY secret is set correctly
• Check that the organization and config path are valid
• Ensure the Continue service is accessible

Documentation Review

I've reviewed this PR for documentation impacts. No documentation updates are needed because:

• This is an internal refactoring that improves metadata tracking for agent sessions
• The changes don't affect user-facing behavior or APIs
• The completion state and change detection happen automatically behind the scenes
• The existing Agents Overview monitoring section adequately describes what users see in Mission Control (summary, diff, logs) without needing to expose internal metadata implementation details

The isComplete and hasChanges flags are internal metadata that improve session tracking in the control plane, but users interact with the results through the Mission Control UI rather than needing to understand these fields directly.

CI Failure Analysis

The failing test on macos-latest, Node 18 is not related to this PR's changes:

Failed Test: TUIChat - User Input Tests > handles special characters in input without crashing [REMOTE MODE]

Error: Test expects special characters !@#$%^&*() to appear in the UI, but they're not being rendered.

Root Cause: This is a flaky/pre-existing test failure in the TUI chat component, completely unrelated to the metadata refactoring in extensions/cli/src/util/exit.ts and extensions/cli/src/commands/serve.ts.

Evidence:

• All other Node versions pass (18, 20, 22, 24 on ubuntu/windows, and 20, 22, 24 on macOS)
• Only macos-latest, Node 18 fails
• The PR only touches metadata collection code, not UI rendering
• This appears to be a timing/rendering issue in the test infrastructure

Recommendation: This is a flaky test that should be addressed separately. The PR changes are sound and all relevant tests pass.

🎉 This PR is included in version 1.38.0 🎉

The release is available on:

• npm package (@latest dist-tag)
• GitHub release

Your semantic-release bot 📦🚀

🎉 This PR is included in version 1.37.0 🎉

The release is available on:

• npm package (@latest dist-tag)
• GitHub release

Your semantic-release bot 📦🚀