Skip to content

docs: refresh whole-repo token figure (233k -> 503k)#35

Merged
saldestechnology merged 2 commits into
mainfrom
docs/refresh-codebase-token-figure
Jul 12, 2026
Merged

docs: refresh whole-repo token figure (233k -> 503k)#35
saldestechnology merged 2 commits into
mainfrom
docs/refresh-codebase-token-figure

Conversation

@saldestechnology

Copy link
Copy Markdown
Collaborator

The ctx codebase has grown well past the old 233,169-token figure the docs cite. Re-measured with the same command the docs reference (ctx --count-only, cl100k_base, default target): 502,856 tokens (205 files).

Updated every instance and the derived ratio against the ~8,700-token task-scoped ctx smart example (now ~58×, was 27×):

  • README.md — the "wrong 503k" line and the ctx smart comment
  • docs/website/docs/why-ctx.md — both the "one dump" figure and the smart-context ratio
  • docs/website/docs/guides/using-ctx-with-agents.md — full-dump vs task-scoped comparison
  • docs/messaging.md — messaging reference (legacy top-level tree)

Note: this is 502,856, not the ~545k mentioned in passing — 545k isn't reproducible with ctx --count-only; this figure is, matching how the original was obtained.

…x dirs

PR #33 accidentally committed a 155 KB ctx index (codebase.sqlite) under
docs/website/docs/.ctx/. The root .gitignore rule '.ctx/*' is anchored to
the repo root, so nested .ctx dirs were never ignored. Remove the file and
add '**/.ctx/*' (keeping config.toml) so it can't recur.
The codebase grew well past the old 233,169-token figure. Re-measured with
`ctx --count-only` (cl100k_base, default): 502,856 tokens. Update every
instance and the derived ratio vs the ~8,700-token task-scoped example
(now ~58x, was 27x) across the README, why-ctx, using-ctx-with-agents, and
the messaging reference.
@saldestechnology
saldestechnology merged commit d9bcdce into main Jul 12, 2026
8 checks passed
@saldestechnology
saldestechnology deleted the docs/refresh-codebase-token-figure branch July 12, 2026 19:15
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.

1 participant