alexzhang13

Activity

Stars and mentions · Last 30 days, Oct 6 – Nov 4

GitHub stars58
Mentions1
02468Oct 6Oct 20Nov 4
UTC days · repositories alexzhang13 owns1 repository

Top repositories

alexzhang13’s repositories ranked by new stars, as on trending.

Loading

Contributes to

Repositories outside alexzhang13’s account where alexzhang13 opened or reviewed pull requests in the past 365 days.

Who noticed alexzhang13

Everyone who starred or forked alexzhang13’s repositories since the archive began in 2011.

Notable accounts

Ordered by the stars their own repositories have received.

Biggest fans

Accounts that starred the most of these repositories.

Breakout weeks

Each repository’s best week of new stars, with the release published around it.

Mentions

1post
Nov 50 posts
  1. Reddit · · r/LocalLLaMA · u/AdventurousFly4909 · alexzhang13/rlm

    So were RLMs(Recursive Language Models) a fad or are they the bomb? alexzhang13/rlm A while ago there was hype around RLMs but now no one seems to be using it. When using opencode and seeing the context climb like crazy, I always think that it should use sub agents so that it doesn't compact as much. RLMs seem like a good solution to it, but I never seen it mentioned here in discussions and about harnesses, this makes me think it was all hype rather than a actual solution. To those who don't know what RLMs are: There is a main orchestrator and sub agents. The orchestrator and sub agents interact with a Python environment, where they can store data, execute code, and invoke other agents. The goal of the orchestrator is to assemble a answer with the least amount of tokens ending up in the orchestrator context. So the orchestrator will call sub agents and their answers will end up in variables since even the invocation of sub agents happen in python. The sub agents can also invoke new sub agents; that's where the recursive part comes from.

    3 points · 7 comments

Achievements

Awards earned by the repositories alexzhang13 owns. Select an award to embed its badge.

No awards yet

Repositories earn awards by reaching the top three in a completed trending day or week.

A repository earns an award for finishing first, second or third in a completed trending day or week, ranked by new stars, new forks or pull request authors. Awards follow a repository through renames and transfers and count toward its current owner. Weeks run Monday to Sunday, UTC.