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

feat(kugetsu): add local config file for user overrides #67

New Issue
Closed
opened 2026-04-01 08:37:03 +02:00 by shoko · 0 comments
shoko commented 2026-04-01 08:37:03 +02:00
Owner
Copy Link

Feature Request

Add a local config file (~/.kugetsu/config) that allows users to override default settings without modifying the codebase.

Motivation

Currently, to override MAX_CONCURRENT_AGENTS, users must either:

  1. Modify the source code (not ideal)
  2. Use environment variables (clunky UX)

A config file provides persistent, user-friendly overrides.

Design

Config File

Location: ~/.kugetsu/config
Format: Bash-compatible variables

Example:

MAX_CONCURRENT_AGENTS=5

Load Order

  1. kugetsu script loads hardcoded defaults (e.g., MAX_CONCURRENT_AGENTS="${MAX_CONCURRENT_AGENTS:-3}")
  2. If ~/.kugetsu/config exists, source it
  3. User config overrides the defaults

Behavior

  • Config is sourced on each command call, not just during init
  • Changes to config take effect immediately on next command
  • No re-init required
  • Config file is optional - defaults work if file doesn't exist

Implementation

Add near the top of kugetsu script (after defaults, before functions):

# Load user config overrides (~/.kugetsu/config)
if [ -f "$KUGETSU_DIR/config" ]; then
    source "$KUGETSU_DIR/config"
fi

Tasks

  1. Add config file sourcing to kugetsu script
  2. Create default config file at ~/.kugetsu/config (optional, can be created by user)
  3. Document the config file in README or help text
  4. Test: change config, run command, verify override takes effect

Acceptance Criteria

  • Config file is sourced on each command call
  • Changes to config take effect immediately (no re-init)
  • Default values work when config file doesn't exist
  • Config file format is simple and documented
## Feature Request Add a local config file (`~/.kugetsu/config`) that allows users to override default settings without modifying the codebase. ## Motivation Currently, to override `MAX_CONCURRENT_AGENTS`, users must either: 1. Modify the source code (not ideal) 2. Use environment variables (clunky UX) A config file provides persistent, user-friendly overrides. ## Design ### Config File Location: `~/.kugetsu/config` Format: Bash-compatible variables Example: ```bash MAX_CONCURRENT_AGENTS=5 ``` ### Load Order 1. kugetsu script loads hardcoded defaults (e.g., `MAX_CONCURRENT_AGENTS="${MAX_CONCURRENT_AGENTS:-3}"`) 2. If `~/.kugetsu/config` exists, source it 3. User config overrides the defaults ### Behavior - Config is sourced on **each command call**, not just during init - Changes to config take effect immediately on next command - No re-init required - Config file is optional - defaults work if file doesn't exist ### Implementation Add near the top of kugetsu script (after defaults, before functions): ```bash # Load user config overrides (~/.kugetsu/config) if [ -f "$KUGETSU_DIR/config" ]; then source "$KUGETSU_DIR/config" fi ``` ## Tasks 1. Add config file sourcing to kugetsu script 2. Create default config file at `~/.kugetsu/config` (optional, can be created by user) 3. Document the config file in README or help text 4. Test: change config, run command, verify override takes effect ## Acceptance Criteria - [ ] Config file is sourced on each command call - [ ] Changes to config take effect immediately (no re-init) - [ ] Default values work when config file doesn't exist - [ ] Config file format is simple and documented
shoko closed this issue 2026-04-02 00:14:06 +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#67
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?