‹ BackHN Continuity

Thread

Context Language Models

176 points · 51 comments · emersonmacro

  1. bob1029 · · focus · HN ↗
    I would be concerned with context management consuming limited attention resources.

    Do you want your agent solving its own memory crisis, or do you want it solving the actual task? It can probably do both at the same time, but I suspect there is a non trivial cost associated with this.

    A separate hypervisor agent that manages the main agent's context would be much better in my experience. You can run it on a different schedule and the main agent has to spend zero tokens thinking about it. This also makes it a lot easier to control when caches will be missed.

    1. alightsoul · · focus · HN ↗
      Maybe have A second model do the management?
      1. theroadnotbacon · · focus · HN ↗
        Looks like they tested that in the paper, and the code allows for it as well. <a href="https:&#x2F;&#x2F;github.com&#x2F;facebookresearch&#x2F;context-language-models&#x2F;tree&#x2F;main&#x2F;clm&#x2F;clm_icl" rel="nofollow">https:&#x2F;&#x2F;github.com&#x2F;facebookresearch&#x2F;context-language-models&#x2F;... Of course, this is for suggesting context management strategies rather than the actual management afaict.
        1. alightsoul · · focus · HN ↗
          Yeah maybe a second model can do the actual management
      2. vatsachak · · focus · HN ↗
        Yeah, that would be the canonical solution. Modularity is better
      3. verdverm · · focus · HN ↗
        I was thinking this, not so dissimilar from co-training dflash drafters
    2. naw103 · · focus · HN ↗

      [dead]

    3. rajveerb · · focus · HN ↗
      An argument against having a separate hypervisor agent.

      A separate hypervisor agent at least doubles the cost because (1) the underlying model needs to be the same so that we get the same degree of intelligence, and (2) it needs to have the same context + more tokens for the work it does.

    4. flyinfra · · focus · HN ↗

      [dead]

Open on Hacker News to reply ↗

Unofficial Hacker News client; not affiliated with Y Combinator.