Skip to content

Conversation

@cdreetz
Copy link

@cdreetz cdreetz commented Oct 10, 2025

PR Type

  • RL Environment PR - Complete Environment Snapshot & Zero-Training sections
  • Non-Environment PR - Complete Description, Related Issues & Type of Change sections

📝 General Information

Description

Related Issues

Type of Change

  • Bug fix (non-breaking change which fixes an issue)
  • New feature (non-breaking change which adds functionality)
  • Breaking change (fix or feature that would cause existing functionality to not work as expected)
  • This change requires a documentation update
  • Code refactor (no functional changes)
  • Build/CI/CD related changes
  • Other (please describe):

🔖 Environment Snapshot

Field Your Entry
Environment Name
Short Description
Category
Dataset Needed?
External Deps
Environmental Variables
Compute Footprint Estimate

🧪 Zero-Training Test Results

Details

W&B Link:

Examples of the Environment scoring a good example and a bad example:


✅ Developer & Reviewer Checklist

  • Code follows project style (black, isort, flake8 pass with pre-commit)
  • I have performed a self-review of my own code
  • I have commented my code, particularly in hard-to-understand areas
  • I have made corresponding changes to the documentation
  • My changes generate no new warnings
  • New and existing unit tests pass locally with my changes
  • Docstrings added for all new public classes / functions
  • If .env vars required, did you add it to the .env.example in repo root?

@teknium1
Copy link
Collaborator

Heya - is this work still active?

@erikqu erikqu mentioned this pull request Jan 9, 2026
7 tasks
@banga-agents
Copy link

Greetings! I am picking this up as per X post from @teknium1 I am Prolific mind/agichronicles
have a wonderful weekend!

@developerfred
Copy link

Checking comments

@teknium1
Copy link
Collaborator

Anyone looking for the bounty - I would like to inform you that the PR here: #305
By altglitch is currently locked as the likely winner, due to completeness and speed, so please be aware if you are continuing your own PR

@ob1-s
Copy link

ob1-s commented Jan 13, 2026

@teknium1 curious how speed and correctness are being evaluated. i believe my pr #313 had a working commit (4207eea) and demonstrated out-of-the-box full training before the others. totally understand if the decision is based on PR timeline. just wanted to clarify.

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.

6 participants