Skip to content

feat: 7 Claude Code improvements + 5 CODEX.EXE engine subsystems - #144

Closed
raymondginger2018-sudo wants to merge 22 commits into
HKUDS:mainfrom
raymondginger2018-sudo:feat/claude-code-v2
Closed

feat: 7 Claude Code improvements + 5 CODEX.EXE engine subsystems#144
raymondginger2018-sudo wants to merge 22 commits into
HKUDS:mainfrom
raymondginger2018-sudo:feat/claude-code-v2

Conversation

@raymondginger2018-sudo

Copy link
Copy Markdown
Contributor

Overview

7 Claude Code-inspired improvements + 5 CODEX.EXE engine subsystems ported from reverse engineering analysis.

Features

  • Plugin Manager MCP
  • Settings Resolver
  • OTLP/Prometheus Telemetry
  • Effort Router
  • Permission Gate
  • Agent Thread Spawning
  • Internal App Server (Named Pipe IPC)
  • Starlark Script Engine
  • Multi-Provider Router

Files

See diff for full list.

@raymondginger2018-sudo

Copy link
Copy Markdown
Contributor Author

Hi @akaxlh @chaohuang-ai, this PR brings 7 quality-of-life improvements plus 5 engine subsystems (telemetry / hooks / agent threads / starlark rules / app-server). All content is clean, merged with latest main, no conflicts. Please review when you have time. Thanks!

@raymondginger2018-sudo

Copy link
Copy Markdown
Contributor Author

@Zongwei9888 The CI workflow (Linting and Formatting) for this PR is stuck in action_required -- GitHub requires a maintainer to approve running Actions on fork pull requests.

All code has been verified locally (npm run check / py_compile all pass, no conflicts). Could you please Approve and run workflows on this PR, or adjust repo Actions settings to allow fork PRs without approval?

Thanks!

1 similar comment
@raymondginger2018-sudo

Copy link
Copy Markdown
Contributor Author

@Zongwei9888 The CI workflow (Linting and Formatting) for this PR is stuck in action_required -- GitHub requires a maintainer to approve running Actions on fork pull requests.

All code has been verified locally (npm run check / py_compile all pass, no conflicts). Could you please Approve and run workflows on this PR, or adjust repo Actions settings to allow fork PRs without approval?

Thanks!

@raymondginger2018-sudo

Copy link
Copy Markdown
Contributor Author

Hi maintainers - just a friendly bump on this PR. It's been open a while without review; happy to rebase onto the latest main and adjust anything you'd like changed. Thanks for your time!

@raymondginger2018-sudo

Copy link
Copy Markdown
Contributor Author

Hi maintainers. This PR comes from a fork, so its GitHub Actions workflow runs are currently in action_required state, waiting for a maintainer to approve. Could you approve the runs when you get a chance so CI can verify the change? Thanks in advance.

@raymondginger2018-sudo

Copy link
Copy Markdown
Contributor Author

Closing as part of a stale-PR cleanup — open 3+ weeks, and this one bundles 12 subsystems in a single PR, which is exactly the shape that slows review down (per the maintainer's guidance on #181 to split large contributions).

The branch remains in the fork. If these ports are still worth landing, the right re-entry is a series of small independent PRs (one subsystem each, tests included), rebased on current main. Closing to keep the review queue honest — happy to re-propose piecewise later.

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