redhat-et / redhat-et/code-agent
[Guiding Goal]
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 1
- Forks
- 4
- PR merge metrics
- No merged PRs in 30d
Description
The goal of this phase of the project is to fill in the two tables below. Note the goal doesn't include building a central framework for evals or training, performance tuning, scaling beyond a reasonable amount.
Pure evaluation:
| Model | Benchmark | Performance |
| ... | ... | ... |
| ... | ... | ... |
RL training:
| Model | Benchmark | Performance |
| ... | ... | ... |
| ... | ... | ... |
where choices are listed (and can be appended to) here:
Some other constraints for the first phase:
- Multi-step, single-submission rollouts. See implementation.
- Verification hierarchy fixed: AST syntax checking -> Linter -> Type Checker -> Benchmark provided tests
- Simple RL algorithm e.g. GRPO.
In the second stage, we'll discuss the results from this phase and explore at least three branches. For now, hold off on these.
- RL approaches e.g. DAgger like approaches, RLIF, PPO vs GRPO, potentially custom developments.
- Performance tuning: container startup times (and the splitting of verifiers across containers), scaling bottlenecks, custom GPU kernels or handwritten-optimized backward passes (unsloth).
- Richer static analysis (control flow, data flow), dynamic tracing etc. to augment context.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the linked minimal/agent_func_complete.py implementation, then review issues #1 and #5 for the available models and benchmarks. The phase is done when the Pure evaluation and RL training tables contain model, benchmark, and performance results under the stated rollout, verification, and simple-RL constraints.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- ai, machine-learning
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100