Summary

Adds typingTtlSeconds to both agent-level and session-level config schemas, and passes it through to createTypingController() in get-reply.ts.

Problem

The typing indicator has a hardcoded 2-minute TTL (typingTtlMs = 2 * 60_000). For extended thinking models (e.g. Claude Opus 4.6 with effort:max), tool-heavy workflows, or complex multi-step replies, processing regularly exceeds 2 minutes — causing the typing indicator to disappear while the model is still actively working. This confuses users into thinking the bot has stalled.

typingIntervalSeconds is already configurable in the schema, but there is no config path for the TTL.

Change

5 files, 11 insertions:

Behavior

The 0 case works because createTypingController() already has the guard:

if (typingTtlMs <= 0) return; // skip TTL timer entirely

Config Example

# Disable TTL (typing stays active for full processing duration)
agents:
  defaults:
    typingTtlSeconds: 0

# Extend to 5 minutes
agents:
  defaults:
    typingTtlSeconds: 300

Design Decisions

• .nonnegative() not .positive() — because 0 is a valid value meaning "disabled"
• Seconds not milliseconds — matches existing typingIntervalSeconds convention
• Spread with undefined check — only passes typingTtlMs when explicitly configured, preserving the existing default for unset values
• Agent cascades to session — agentCfg?.typingTtlSeconds ?? sessionCfg?.typingTtlSeconds follows the same pattern as typingIntervalSeconds

Closes #13673

Greptile Summary

Adds configurable typingTtlSeconds to agent and session config schemas, allowing users to control how long the typing indicator stays active. The implementation follows the existing typingIntervalSeconds pattern and correctly:

• Adds schema validation with .nonnegative() (allowing 0 to disable TTL)
• Cascades from agent to session config
• Converts seconds to milliseconds before passing to createTypingController()
• Only passes the parameter when explicitly set (preserving the 2-minute default)
• Supports 0 value to disable TTL entirely (typing stays active until processing completes)

The change solves a real problem for extended thinking models and tool-heavy workflows where processing exceeds the hardcoded 2-minute TTL.

Confidence Score: 5/5

• This PR is safe to merge with minimal risk
• The implementation is straightforward, follows established patterns in the codebase (mirrors typingIntervalSeconds), and makes only additive changes. The type checking, schema validation, and conditional spreading ensure backward compatibility. The existing createTypingController() logic already handles all edge cases including 0 and negative values.
• No files require special attention

_{Last reviewed commit: 0514a1b}

_{(5/5) You can turn off certain types of comments like style here!}