`GenerateTelosSummary.parseModels()` silently drops every model after the third
Maintainers usually reply within 11 days
Nobody has claimed this yet.
Assessment
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Newbie friendliness
- 86/100
- Issue type
- Bug
- Clarity
- Clearly specified
- Activity status
- Active
- Tech stack
- typescript
- Domain
- tooling
Research direction
Start at LifeOS/install/LIFEOS/TOOLS/GenerateTelosSummary.ts:610-617 and inspect parseModels, then run the clean-tree reproduction with bun and check the Core Models section using rg. Done means models beyond MD2 are represented in PRINCIPAL_TELOS.md, or any intentional limit is explicitly reported as described in the issue.
Written by the indexing model from the issue text.
Description
Version
LifeOS 7.40.4 / Telos
What is broken
PRINCIPAL_TELOS.md is generated from the TELOS files and loaded at session start. Its Core Models section is built by parseModels(), which keeps only the first three MD* items from MODELS.md and drops the rest without a notice. A user with five models gets three in every session, and nothing tells them that MD3 and MD4 never reach the context. The function comment says only "first sentence only", so the cap is undocumented. Each model is also truncated to 65 characters (at a word boundary), which cuts off longer model statements.
Where (file:line)
LifeOS/install/LIFEOS/TOOLS/GenerateTelosSummary.ts:610-617 (cap at :613).
Repro on a clean tree
H=$(mktemp -d); T=$H/.claude/LIFEOS/USER/TELOS; mkdir -p $T; cp LifeOS/install/USER/TELOS/*.md $T/
printf '# Models\n\n- **MD0**: Model zero is here. More.\n- **MD1**: Model one is here. More.\n- **MD2**: Model two is here. More.\n- **MD3**: Model three is here. More.\n- **MD4**: Model four is here. More.\n' > $T/MODELS.md
HOME=$H bun LifeOS/install/LIFEOS/TOOLS/GenerateTelosSummary.ts
rg -A5 'Core Models' $T/PRINCIPAL_TELOS.md
Negative control
On unpatched 7.40.4 the generator prints ✅ Generated PRINCIPAL_TELOS.md (41 lines), and ## Core Models lists only Model zero/one/two is here. MD3 and MD4 are absent and no line says they were omitted.
Suggested fix
Render every MD* item. If always-loaded context size is the reason for the cap, make it an explicit constant and append - (+N more in MODELS.md) whenever items are dropped. Related, closed: #1140, #1260 (which rewrote parseModels without touching the cap). Untested.
Before submitting
- I searched open and closed issues for this defect.
- The repro runs against a clean tree of the version above, not against my modified install.
- I removed personal data from the pasted output — real names, absolute home paths, tokens, my own content.
- Dominant language
- TypeScript
- Stars
- 19.4k
- Forks
- 2.5k
- PR merge metrics
- No merged PRs in 30d
Getting set up
This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.
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.
More from danielmiessler/LifeOS
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
danielmiessler/LifeOS#2349 ·
Maintainers usually reply within 11 days
-
Difficulty 1/5 Under an hour Newbie friendliness 94/100
danielmiessler/LifeOS#2338 ·
Maintainers usually reply within 11 days
-
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
danielmiessler/LifeOS#2337 ·
Maintainers usually reply within 11 days
-
Difficulty 2/5 1-3 hours Newbie friendliness 90/100
danielmiessler/LifeOS#2336 ·
Maintainers usually reply within 11 days
-
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
danielmiessler/LifeOS#2335 ·
Maintainers usually reply within 11 days
All issues in danielmiessler/LifeOS
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
paperclipai/paperclip#16785 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
code-yeongyu/senpi#3661 ·
Maintainers usually reply within 1 day
-
community first-timers-only good first issue hacktoberfest help wanted low hanging fruit up-for-grabs
Difficulty 1/5 Under an hour Newbie friendliness 78/100
lingdojo/kana-dojo#32731 · 1 comment · 5 reactions ·
Maintainers usually reply within 1 day
-
bug status: needs triage
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
mastra-ai/mastra#27538 · 1 comment ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
Yeachan-Heo/oh-my-codex#3822 ·
Maintainers usually reply within 1 day