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 (fixes #67) #69

Closed
shoko wants to merge 0 commits from fix/issue-67-config-file into main
pull from: fix/issue-67-config-file
merge into: shoko:main
Conversation 4 Commits - Files Changed -
shoko commented 2026-04-01 09:12:09 +02:00
Owner
Copy Link

Summary

Add ~/.kugetsu/config file that sources on each command call for persistent user overrides.

Implementation

After line 11 in kugetsu script (after MAX_CONCURRENT_AGENTS default):

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

Usage

Users can create ~/.kugetsu/config:

MAX_CONCURRENT_AGENTS=5

Benefits

  • Config sourced on each command call (immediate effect, no re-init)
  • No environment variables needed
  • Persistent across sessions
  • Simple bash-compatible format

Fixes #67

## Summary Add `~/.kugetsu/config` file that sources on each command call for persistent user overrides. ## Implementation After line 11 in kugetsu script (after MAX_CONCURRENT_AGENTS default): ```bash # Load user config overrides (~/.kugetsu/config) if [ -f "$KUGETSU_DIR/config" ]; then source "$KUGETSU_DIR/config" fi ``` ## Usage Users can create `~/.kugetsu/config`: ```bash MAX_CONCURRENT_AGENTS=5 ``` ## Benefits - Config sourced on each command call (immediate effect, no re-init) - No environment variables needed - Persistent across sessions - Simple bash-compatible format Fixes #67
shoko added 1 commit 2026-04-01 09:12:09 +02:00
feat: add local config file for user overrides ebc2f99320 
Add ~/.kugetsu/config file that sources on each command call for
persistent user overrides like MAX_CONCURRENT_AGENTS.

Fixes #67
han commented 2026-04-01 09:20:06 +02:00
First-time contributor
Copy Link

I think we should include in kugetsu initialize that it will write config file. so basically its easier for user to modify it rather than figuring out which config key is it. we initialized the config file exactly as the default value. also add the SKILL.md to mention about the ability to change the config

I think we should include in kugetsu initialize that it will write config file. so basically its easier for user to modify it rather than figuring out which config key is it. we initialized the config file exactly as the default value. also add the SKILL.md to mention about the ability to change the config
shoko force-pushed fix/issue-67-config-file from ebc2f99320 to 4d3205de86 2026-04-01 10:02:25 +02:00 Compare
shoko added 1 commit 2026-04-01 10:21:06 +02:00
feat(kugetsu): add local config file for user overrides a195d68b2a 
- Source ~/.kugetsu/config on each command call
- Allows user to override defaults (e.g., MAX_CONCURRENT_AGENTS)
- Changes take effect immediately, no re-init needed

Fixes #67
shoko commented 2026-04-01 11:36:44 +02:00
Author
Owner
Copy Link

Thanks han! I will address both requests: 1) Add config file initialization to kugetsu init, 2) Document config override in SKILL.md. Let me know if anything else is needed.

Thanks han! I will address both requests: 1) Add config file initialization to kugetsu init, 2) Document config override in SKILL.md. Let me know if anything else is needed.
shoko commented 2026-04-01 11:49:19 +02:00
Author
Owner
Copy Link

Thanks han! I will address both requests: 1) Add config file initialization to kugetsu init, 2) Document config override in SKILL.md. Let me know if anything else is needed.

Thanks han! I will address both requests: 1) Add config file initialization to kugetsu init, 2) Document config override in SKILL.md. Let me know if anything else is needed.
shoko added 1 commit 2026-04-02 00:12:33 +02:00
feat(kugetsu): add config file initialization and documentation 5e968b6c4a 
- Initialize default ~/.kugetsu/config during kugetsu init
- Document config override options in SKILL.md
- Addresses han's review feedback
han approved these changes 2026-04-02 00:13:49 +02:00
han left a comment
First-time contributor
Copy Link

lgtm

lgtm
shoko closed this pull request 2026-04-02 00:14:12 +02:00
shoko deleted branch fix/issue-67-config-file 2026-04-02 00:14:12 +02:00

Pull request closed

This pull request cannot be reopened because the branch was deleted.
Sign in to join this conversation.
Reviewers
No Reviewers
han
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
2 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: shoko/kugetsu#69
Delete Branch "fix/issue-67-config-file"

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?