WeSearch

Context window exceeded at turn 23. Here's how I track token usage without a tokenizer.

·1 min read · 0 reactions · 0 comments · 10 views
#ai#technology#development
Context window exceeded at turn 23. Here's how I track token usage without a tokenizer.
TL;DR · WeSearch summary

The article discusses a submission for the Hermes Agent Challenge, focusing on the challenges of managing context windows in AI interactions. The author experienced a context length error after 23 turns of conversation, highlighting the limitations of current systems. The piece emphasizes the need for better handling of token usage in AI applications.

Key facts
Original article
DEV.to (Top)
Read full at DEV.to (Top) →
Opening excerpt (first ~120 words) tap to expand

try { if(localStorage) { let currentUser = localStorage.getItem('current_user'); if (currentUser) { currentUser = JSON.parse(currentUser); if (currentUser.id === 3915555) { document.getElementById('article-show-container').classList.add('current-user-is-article-author'); } } } } catch (e) { console.error(e); } Mukunda Rao Katta Posted on May 25 Context window exceeded at turn 23. Here's how I track token usage without a tokenizer. #hermesagentchallenge #devchallenge #agents #python Hermes Agent Challenge Submission: Write About Hermes Agent This is a submission for the Hermes Agent Challenge. My Hermes agent's context window fills up gradually. Each turn adds messages. Tool call results add more.

Excerpt limited to ~120 words for fair-use compliance. The full article is at DEV.to (Top).

Anonymous · no account needed
Share 𝕏 Facebook Reddit LinkedIn Threads WhatsApp Bluesky Mastodon Email

Discussion

0 comments

More from DEV.to (Top)