Skip to content

parity(ux): Goose v1.34.0 — goose-tui binary, mergeable configs, revert client-side autocompaction #4023

@bug-ops

Description

@bug-ops

Description

Goose v1.34.0 shipped three features not tracked in existing parity issues (#3885, #3902):

1. goose-tui binary (PR #9089)

Separate TUI binary alongside the main agent. Goose now ships both goose (GUI/CLI) and goose-tui (terminal UI).

Zeph gap: Zeph's TUI is a feature flag (--tui), not a separate binary. A dedicated zeph-tui binary would improve packaging and let users install TUI without pulling full GUI dependencies.

2. Mergeable configs (PR #8378)

Configuration files can now declare merge semantics — layered config sources compose rather than override. Users can have a project-level config merged with a user-level config without full replacement.

Zeph gap: zeph-config uses last-write-wins; no merge semantics. Config layering (user → project → env) is common in agent frameworks.

3. Revert client-side autocompaction (PR #9055)

Goose reverted client-side automatic context compaction, indicating it caused quality regressions. Directly relevant to CI-799's zeph-context compaction scheduling changes.

Zeph implication: validate that zeph-context compaction guards (#3999, compaction_guards_and_consolidation_tests.rs +113 in CI-799) prevent the same class of regressions Goose hit with unconditional autocompaction.

Expected Behavior

Zeph has evaluated each of these patterns for applicability.

Environment

Metadata

Metadata

Assignees

No one assigned

    Labels

    P3Research — medium-high complexityresearchResearch-driven improvement

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions