shoko/kugetsu
1
0
Fork 0
Code Issues 17 Pull Requests Actions Packages Projects Releases 3 Wiki Activity

feat(kugetsu): set GIT_EDITOR=cat in kugetsu init for non-interactive git operations #70

New Issue
Closed
opened 2026-04-01 10:46:45 +02:00 by shoko · 0 comments
shoko commented 2026-04-01 10:46:45 +02:00
Owner
Copy Link

Problem

When PM or dev agents run git rebase/conflict resolution in headless mode, git opens vim which requires TTY. This causes operations to hang waiting for input.

Example error:

Vim: Warning: Output is not to a terminal
Vim: Warning: Input is not from a terminal

Solution

In kugetsu init, set GIT_EDITOR=cat in the opencode session environment. This tells git to use cat as editor, which outputs to stdout and exits immediately instead of opening vim.

Implementation

In kugetsu init, when creating base session and pm-agent session, set environment:

export GIT_EDITOR=cat
export EDITOR=cat

This ensures all git operations (rebase, commit --amend, etc.) that might open an editor use cat instead.

Tasks

  1. Add GIT_EDITOR=cat and EDITOR=cat to kugetsu init
  2. Document that git operations will use non-interactive mode
  3. Verify rebase --continue works without TTY
## Problem When PM or dev agents run git rebase/conflict resolution in headless mode, git opens vim which requires TTY. This causes operations to hang waiting for input. Example error: ``` Vim: Warning: Output is not to a terminal Vim: Warning: Input is not from a terminal ``` ## Solution In kugetsu init, set `GIT_EDITOR=cat` in the opencode session environment. This tells git to use `cat` as editor, which outputs to stdout and exits immediately instead of opening vim. ## Implementation In kugetsu init, when creating base session and pm-agent session, set environment: ```bash export GIT_EDITOR=cat export EDITOR=cat ``` This ensures all git operations (rebase, commit --amend, etc.) that might open an editor use cat instead. ## Tasks 1. Add GIT_EDITOR=cat and EDITOR=cat to kugetsu init 2. Document that git operations will use non-interactive mode 3. Verify rebase --continue works without TTY
shoko closed this issue 2026-04-01 10:55:00 +02:00
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
0.2.x-only
Available only in 0.2.x, not backportable
 0.3.x-only
Available only in 0.3.x, not backportable
 backport
Backport compatible - can merge to 0.1.x
 blocked
Issue needs clarification/discussion before it can be worked on
 bug
Bug report
 critical
Critical - blocking parallel work
 feature
New feature
 foundation
Foundation work for 0.2.x
 high
High priority - workflow improvements
 meta
Meta issue tracking multiple issues
 need-review
PR needs review before merge
 parallelization
Issues related to parallelization
 ready
Issue is clear and ready to be implemented/delegated
 ready-to-merge
PR approved and ready to merge
 task-delegation
Issues related to task-delegation
No Label
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
shoko
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: shoko/kugetsu#70
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?