Skip to content

[3613] Root interactive launcher sync#3614

Merged
njfio merged 5 commits intomasterfrom
3613-root-interactive-launcher
Mar 20, 2026
Merged

[3613] Root interactive launcher sync#3614
njfio merged 5 commits intomasterfrom
3613-root-interactive-launcher

Conversation

@njfio
Copy link
Owner

@njfio njfio commented Mar 20, 2026

Closes #3613

Spec: specs/3613-root-interactive-launcher.md

What changed:

  • default root tau-unified.sh tui path now launches tau-tui interactive
  • preserved explicit legacy --agent mode
  • updated launcher tests to assert interactive is the default root TUI mode

Test evidence:

  • bash scripts/run/test-tau-unified.sh
  • bash scripts/dev/test-root-just-launcher.sh
  • root PTY smoke reached tau-unified: launching tui (interactive) via just tui

Copilot AI review requested due to automatic review settings March 20, 2026 15:10
Copy link

@greptile-apps greptile-apps bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

njfio has reached the 50-review limit for trial accounts. To continue receiving code reviews, upgrade your plan.

@njfio njfio merged commit 48bbff5 into master Mar 20, 2026
7 checks passed
@njfio njfio deleted the 3613-root-interactive-launcher branch March 20, 2026 15:11
Copy link

Copilot AI left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Pull request overview

Updates the root repo “tui” launcher path so scripts/run/tau-unified.sh tui (and just tui) defaults to launching the graphical tau-tui interactive mode, while retaining the legacy --agent mode.

Changes:

  • Switch tau-unified.sh tui default mode from agent to interactive and add an explicit --interactive flag.
  • Update launcher tests to assert interactive is the default TUI mode and runner args reflect that.
  • Extend root justfile launcher contract test coverage for tui-fresh dry-run behavior.

Reviewed changes

Copilot reviewed 4 out of 4 changed files in this pull request and generated 3 comments.

File Description
specs/3613-root-interactive-launcher.md Adds a spec document for the change (currently not following repo spec layout conventions).
scripts/run/tau-unified.sh Changes default TUI mode to interactive, adds --interactive, and refactors TUI command selection.
scripts/run/test-tau-unified.sh Updates assertions so the default TUI marker/args are interactive.
scripts/dev/test-root-just-launcher.sh Adds tui-fresh dry-run assertions (session reset + tui invocation).

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

Comment on lines +437 to 440
local tui_mode="interactive"
local saw_iterations="false"
local saw_interval="false"
local bootstrap_runtime="${TAU_UNIFIED_TUI_BOOTSTRAP_RUNTIME:-}"
Copy link

Copilot AI Mar 20, 2026

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Since tui_mode now defaults to interactive, the later --iterations/--interval-ms require --live-shell guard no longer triggers for the default mode. This allows incompatible flags (e.g. tui --iterations 2) to be silently accepted/ignored, which contradicts the launcher contract to hard-fail on incompatible flags. Update the validation so --iterations/--interval-ms are rejected unless tui_mode is live-shell (regardless of agent vs interactive).

Copilot uses AI. Check for mistakes.
Comment on lines 172 to 180
tui_output="$(
TAU_UNIFIED_RUNNER="${runner}" \
TAU_UNIFIED_RUNNER_LOG="${runner_log}" \
TAU_UNIFIED_RUNNER_PID="${runner_pid}" \
TAU_UNIFIED_RUNTIME_DIR="${runtime_dir}" \
"${LAUNCHER_SCRIPT}" tui --no-color 2>&1 || true
)"
assert_contains "${tui_output}" "tau-unified: launching tui (agent)" "tui agent marker"
assert_contains "${tui_output}" "tau-unified: launching tui (interactive)" "tui interactive marker"
up_count_after_tui="$(grep -c '^runner_mode=up$' "${runner_log}" || true)"
Copy link

Copilot AI Mar 20, 2026

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The updated assertions validate the new default interactive mode, but there is no integration check that ./tau-unified.sh tui --agent still routes to the legacy agent mode (as promised in the PR description). Add a test invocation that passes --agent and asserts the (agent) launch marker and runner args include agent so the legacy path can’t regress.

Copilot uses AI. Check for mistakes.
Comment on lines +1 to +8
# 3613 Root Interactive Launcher

## Objective
Make the sanctioned root-path dev loop launch the graphical `tau-tui interactive` entrypoint instead of the legacy `tau-tui agent` shell path.

## Inputs/Outputs
- Input: `just tui`, `just tui-fresh`, or `./scripts/run/tau-unified.sh tui` from the root repo.
- Output: a command path that launches `cargo run -p tau-tui -- interactive --profile <profile> --model <model>` and preserves the validated root dev defaults for timeout and retry behavior where applicable.
Copy link

Copilot AI Mar 20, 2026

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This spec file doesn’t follow the repo’s spec contract: AGENTS.md specifies per-issue specs must live at specs/<issue-id>/spec.md and include a Status: line (Draft|Reviewed|Accepted|Implemented). As written (specs/3613-root-interactive-launcher.md) it likely won’t be picked up by spec tooling and is missing Status:. Consider moving it to specs/3613/spec.md (and adding Status:) to match the established structure.

Copilot uses AI. Check for mistakes.
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.

Root dev launcher starts agent shell instead of graphical interactive TUI

2 participants