Devotd Github
ReleaseCoding agents

yeachan-heo/oh-my-claudecode v5.7.26 — Memory path and workflow fixes

yeachan-heo/oh-my-claudecode v5.7.26 is a release that aligns the project memory path with the current working file and stops deprecated workflow names from being recommended or selected as an execution path.

Repositoryyeachan-heo/oh-my-claudecode ↗

yeachan-heo/oh-my-claudecode v5.7.26 is a release that aligns the project memory path with the current working file and stops deprecated workflow names from being recommended or selected as an execution path.

GitHub description: Teams-first Multi-agent orchestration for Claude Code

stars
★ 40.5K
Forks
3.6K
Language
TypeScript
License
MIT
Latest release
v5.7.26
Read original source ↗View on GitHub ↗

yeachan-heo/oh-my-claudecode v5.7.26 changed how the project memory path and deprecated workflow names are handled. The memory path now follows the current working file, and deprecated workflow names are no longer recommended or selected as an execution path. The changes are published in the v5.7.26 release record on GitHub. What this release covers is path consistency and blocking deprecated names from being recommended or selected.

This repository is a team-first multi-agent orchestration project for Claude Code. Orchestration is the way the work of several agents is coordinated, and the repository description presents a team-centered setup. This fix deals with making the project memory path follow the current working file in such an environment, and with keeping workflow names that are no longer used out of recommendations and execution paths. The provided release information alone does not reveal the specific places where these two changes apply, or how they behave in more detail.

The provided information contains no background on the change, no test results and no performance figures. So it is not possible to judge what impact the fix has in actual use, or how much it reduces errors. What can be confirmed is limited to two points: the memory path was aligned with the current working file, and deprecated workflow names are no longer recommended or selected as an execution path. There is no basis for evaluating this release beyond that scope of change.