Skip to content

Implement question queue feature, improve session & branch switch, add /abort command, support codex/copilot CLI native sessions#26

Merged
daocha merged 3 commits into
mainfrom
feature-enhancements
Mar 27, 2026
Merged

Implement question queue feature, improve session & branch switch, add /abort command, support codex/copilot CLI native sessions#26
daocha merged 3 commits into
mainfrom
feature-enhancements

Conversation

@daocha
Copy link
Copy Markdown
Owner

@daocha daocha commented Mar 27, 2026

Improve session switching, branch recovery, abort handling, and queued message flow

Mix bot-managed and native Codex/Copilot CLI sessions in /switch, import native sessions into bot state, and refine session/provider/branch state handling for smoother cross-device continuation.

Harden branch preparation and fallback behavior by checking real remote branch existence, rolling back failed origin-based prep, and prompting users through branch discrepancy recovery instead of silently switching.

Add stronger runtime handling for busy projects: queue later text messages to disk, process queued question files after the active run, and prompt before continuing queued work when the previous run was aborted.

Tighten agent progress and abort behavior, keep /abort and /current usable while a project is busy, and expand README plus regression tests to cover queueing, switching, branch recovery, and abort flows.

…d message flow

Mix bot-managed and native Codex/Copilot sessions in /switch, import native sessions into bot state, and refine session/provider/branch state handling for smoother cross-device continuation.

Harden branch preparation and fallback behavior by checking real remote branch existence, rolling back failed origin-based prep, and prompting users through branch discrepancy recovery instead of silently switching.

Add stronger runtime handling for busy projects: queue later text messages to disk, process queued question files after the active run, and prompt before continuing queued work when the previous run was aborted.

Tighten agent progress and abort behavior, keep /abort and /current usable while a project is busy, and expand README plus regression tests to cover queueing, switching, branch recovery, and abort flows.
Move default state and log storage under ~/.coding-agent-telegram, remove STATE_FILE/STATE_BACKUP_FILE/LOG_DIR env configuration, and update startup, config loading, env template, CLI guidance, and README to match the simplified home-based layout with local state-file backward compatibility.

Refactor session_commands.py into focused mixins for provider selection, lifecycle handling, branch resolution, and session status while keeping the legacy session_commands wrapper path for compatibility.

Align Copilot behavior with the native CLI by stopping project-scoped COPILOT_HOME injection, discovering native Copilot sessions from ~/.copilot unless COPILOT_HOME is explicitly set, and using human-readable fallback labels when native session metadata lacks a summary or event history.

Remove the built-in agent prompt prefix, improve queued-question handoff prompting so the agent reads the queue file instead of answering about the path itself, and normalize abort messages so users consistently see 'Agent run aborted by /abort.' instead of sanitized path placeholders.

Expand regression coverage for config defaults, Copilot discovery, queue-file prompting, and abort-message sanitization.
@daocha daocha merged commit 9994491 into main Mar 27, 2026
1 check passed
@daocha daocha deleted the feature-enhancements branch March 27, 2026 22:43
dcha-agent added a commit that referenced this pull request Mar 28, 2026
…nd, support codex/copilot CLI native sessions (#26)

* Improve session switching, branch recovery, abort handling, and queued message flow

Mix bot-managed and native Codex/Copilot sessions in /switch, import native sessions into bot state, and refine session/provider/branch state handling for smoother cross-device continuation.

Harden branch preparation and fallback behavior by checking real remote branch existence, rolling back failed origin-based prep, and prompting users through branch discrepancy recovery instead of silently switching.

Add stronger runtime handling for busy projects: queue later text messages to disk, process queued question files after the active run, and prompt before continuing queued work when the previous run was aborted.

Tighten agent progress and abort behavior, keep /abort and /current usable while a project is busy, and expand README plus regression tests to cover queueing, switching, branch recovery, and abort flows.

* Move .coding_agent_telegram and .env_coding_agent_telegram to home folder

* Align Copilot state with native CLI and split session command logic

Move default state and log storage under ~/.coding-agent-telegram, remove STATE_FILE/STATE_BACKUP_FILE/LOG_DIR env configuration, and update startup, config loading, env template, CLI guidance, and README to match the simplified home-based layout with local state-file backward compatibility.

Refactor session_commands.py into focused mixins for provider selection, lifecycle handling, branch resolution, and session status while keeping the legacy session_commands wrapper path for compatibility.

Align Copilot behavior with the native CLI by stopping project-scoped COPILOT_HOME injection, discovering native Copilot sessions from ~/.copilot unless COPILOT_HOME is explicitly set, and using human-readable fallback labels when native session metadata lacks a summary or event history.

Remove the built-in agent prompt prefix, improve queued-question handoff prompting so the agent reads the queue file instead of answering about the path itself, and normalize abort messages so users consistently see 'Agent run aborted by /abort.' instead of sanitized path placeholders.

Expand regression coverage for config defaults, Copilot discovery, queue-file prompting, and abort-message sanitization.

---------

Co-authored-by: Dcha Agent <[email protected]>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants