Skip to content

feat: support oh-my-openagent*.json alongside oh-my-opencode*.json#1

Open
hrohrweck wants to merge 1 commit into
windysky:mainfrom
hrohrweck:feat/support-oh-my-openagent
Open

feat: support oh-my-openagent*.json alongside oh-my-opencode*.json#1
hrohrweck wants to merge 1 commit into
windysky:mainfrom
hrohrweck:feat/support-oh-my-openagent

Conversation

@hrohrweck

Copy link
Copy Markdown

Summary

Adds support for the new oh-my-openagent*.json naming convention while maintaining backward compatibility with the legacy oh-my-opencode*.json files.

Changes

switch_oh-my-opencode_config.py

  • Dual-name discovery: Scans for both oh-my-openagent*.json and oh-my-opencode*.json configuration files
  • Auto-detection of active config: Prefers oh-my-openagent.json (new name) over oh-my-opencode.json (deprecated) when determining the current active configuration
  • Smart backup logic: Creates backups with the appropriate naming convention matching the active config
  • Updated error messages: Now mentions both naming patterns to help users understand what files are expected
  • Version bump: 1.1.01.2.0

README.md

  • Updated all examples and documentation to reflect dual-name support
  • Added version history entry for v1.2.0
  • File tree example now shows both naming conventions

Testing

Verified locally that:

  • oh-my-openagent.json is correctly detected as the active config
  • Variant files like oh-my-openagent-variant.json are discovered and listed
  • The active config is always shown first in the menu with the (current) label

Backward Compatibility

Fully backward compatible — existing oh-my-opencode*.json files continue to work exactly as before. The change is purely additive.

- Add dual-name support for configuration file discovery
- Auto-detect active config (prefers oh-my-openagent.json over legacy oh-my-opencode.json)
- Update backup logic to match active config naming
- Update all user-facing messages to reflect both naming conventions
- Bump version to 1.2.0
- Update README documentation for dual-name support
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant