jackasda211233 commited on
Commit
1d53c17
·
verified ·
1 Parent(s): b532b08

Upload README.md with huggingface_hub

Browse files
Files changed (1) hide show
  1. README.md +3 -1
README.md CHANGED
@@ -42,7 +42,9 @@ Over the past several years, the author has observed a consistent trend of **inc
42
 
43
  ### The Original RYS Experience
44
 
45
- The original RYS-Qwen3.5-27B by [dnhkng](https://github.com/dnhkng) was exceptional as a coding agent. In the author's experience over 40+ hours of comparative usage against GPT-5.3 Codex on a complex multi-service project (a custom agent OS with a vault messaging app, webhook bridge, and multi-agent backend), dnhkng's RYS model identified and fixed deep architectural bugs that Codex missed entirely — such as silently misdirected conversation routing between the vault app and the backend, where messages were being sent to a dead webhook port while the actual agent bridge was running on a different service. The RYS model traced the full request chain across three services, found the disconnected bridge, and rewired the connection. This model attempts to retain that level of deep architectural reasoning while adding unrestricted instruction following.
 
 
46
 
47
  ### Previous Attempt & Lessons Learned
48
 
 
42
 
43
  ### The Original RYS Experience
44
 
45
+ The original RYS-Qwen3.5-27B by [dnhkng](https://github.com/dnhkng) was exceptional as a coding agent. In the author's experience over 40+ hours of comparative usage against GPT-5.3 Codex on a complex multi-service project (a custom agent OS with a vault messaging app, webhook bridge, and multi-agent backend), dnhkng's RYS model identified and fixed deep architectural bugs that Codex missed entirely — such as silently misdirected conversation routing between the vault app and the backend, where messages were being sent to a dead webhook port while the actual agent bridge was running on a different service. The RYS model traced the full request chain across three services, found the disconnected bridge, and rewired the connection. However, even the original (censored) RYS model and the standard Qwen3.5-27B exhibited a frustrating pattern: when asked to fix issues in existing infrastructure, the model would silently attempt to create an entirely new backend or service rather than modify the pre-existing one — effectively avoiding touching the original codebase. The author had to repeatedly, specifically instruct the model to work on the existing backend, not build a replacement. This avoidance behavior appeared to stem from the safety guardrails treating modifications to running services as potentially harmful. This model eliminates that friction it will work directly on your existing codebase and infrastructure without requiring constant re-prompting.
46
+
47
+ This model attempts to retain that level of deep architectural reasoning while adding unrestricted instruction following and direct, non-evasive engagement with existing codebases.
48
 
49
  ### Previous Attempt & Lessons Learned
50