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

Improve session logs format for human readability #252

New Issue
Closed
opened 2026-04-08 06:43:10 +02:00 by shoko · 0 comments
shoko commented 2026-04-08 06:43:10 +02:00
Owner
Copy Link

Problem

Currently the session logs format is difficult for humans to read. When running 'kugetsu logs' or examining session outputs, the format is not optimized for quick comprehension.

User Request

User wants:

  1. A 'kugetsu session list' command that shows all sessions ordered by their last updated time
  2. Better log formatting for human readability (not just raw dump)

Solution

1. Session List Command (kugetsu session list)

Create a new 'kugetsu session' subcommand with list action:

  • Show all sessions (base, pm-agent, and forked issue sessions)
  • Order sessions by last activity (most recent first)
  • Show key info: issue_ref, state, last_updated, session_id

Example output format:

2. Log Format Improvement

Improve 'kugetsu logs' command for better readability:

  • Cleaner timestamp formatting
  • Clearer separation between entries
  • Color-coded log levels (if terminal supports it)
  • Easier to scan for recent activity

Status

READY - No dependencies

Files

  • skills/kugetsu/scripts/kugetsu-session.sh (cmd_session function)
  • skills/kugetsu/scripts/kugetsu-log.sh (log formatting)

Related Issue

Parent: #235

## Problem Currently the session logs format is difficult for humans to read. When running 'kugetsu logs' or examining session outputs, the format is not optimized for quick comprehension. ## User Request User wants: 1. A 'kugetsu session list' command that shows all sessions ordered by their last updated time 2. Better log formatting for human readability (not just raw dump) ## Solution ### 1. Session List Command (kugetsu session list) Create a new 'kugetsu session' subcommand with list action: - Show all sessions (base, pm-agent, and forked issue sessions) - Order sessions by last activity (most recent first) - Show key info: issue_ref, state, last_updated, session_id Example output format: ### 2. Log Format Improvement Improve 'kugetsu logs' command for better readability: - Cleaner timestamp formatting - Clearer separation between entries - Color-coded log levels (if terminal supports it) - Easier to scan for recent activity ## Status **READY** - No dependencies ## Files - skills/kugetsu/scripts/kugetsu-session.sh (cmd_session function) - skills/kugetsu/scripts/kugetsu-log.sh (log formatting) ## Related Issue Parent: #235
shoko added the ready label 2026-04-08 06:43:16 +02:00
shoko closed this issue 2026-04-08 08:53:54 +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 ready
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#252
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?