feat(runtime): add opt-in start on first prompt

Taha commented

2026-10-21 16:16:04 +00:00

Contributor

Opening the TUI created a session immediately, so every launch that ended
without a message left an empty row behind. The new start_on_first_prompt
setting holds the launch on the startup surface until the user submits a
prompt, then creates the session and sends that text, so the runtime and its
sandbox start from the first message instead of from opening the UI.

The gate defers only the create path; --continue, --resume, --fork, and
session new still bind or create their session at once. Ctrl+D on the empty
startup editor now exits before any session exists. The home-manager module
exposes the setting as settings.startOnFirstPrompt and writes it as
start_on_first_prompt.

Opening the TUI created a session immediately, so every launch that ended without a message left an empty row behind. The new start_on_first_prompt setting holds the launch on the startup surface until the user submits a prompt, then creates the session and sends that text, so the runtime and its sandbox start from the first message instead of from opening the UI. The gate defers only the create path; --continue, --resume, --fork, and `session new` still bind or create their session at once. Ctrl+D on the empty startup editor now exits before any session exists. The home-manager module exposes the setting as settings.startOnFirstPrompt and writes it as start_on_first_prompt.

Taha force-pushed taha/tmux-keys-lazy-start from c0eb5b211c to acf756c318

2026-10-21 16:49:18 +00:00

Compare

Taha force-pushed taha/tmux-keys-lazy-start from acf756c318 to 1ea5f30b34

2026-10-21 16:56:58 +00:00

Compare

Taha referenced this pull request

2026-10-21 18:03:06 +00:00

Shift+Enter (veya Ctrl+Shift+Enter) Kisayolunun Calismamasi #13

Taha referenced this pull request

2026-10-21 18:03:50 +00:00

Acilista Bos Session Olusmasi #9