← Back to home
Comparison · ai-assistants

btw vs Docling

A side-by-side editorial comparison of btw and Docling — release velocity, themes, recent moves, and the top alternatives to consider.

btw vs Docling: at a glance

FeaturebtwDocling
Sectorai-assistantsai-assistants
Velocity score2.56.3
Sparks · 30d00
Top themesllm tooling, r, agentic workflows, developer toolsdocument-parsing, format-coverage, pluggable-engines, ocr
Last editorial update3d ago1d ago
WebsiteVisit →Visit →

What is btw?

btw is turning into an agentic R harness that no longer needs you to be in R

btw assembles context about an R session — packages, documentation, files, data frames — and hands it to an LLM through ellmer, with btw_app() as a chat interface. Over the last year it has grown well past context assembly: LLMs can document, check, test and measure coverage of a package, read CLAUDE.md and AGENTS.md as project context, fetch skills from packages or GitHub, and inspect the source of any installed namespace. Much of this is now reachable from a terminal CLI rather than only from an R prompt.

Read the full btw trajectory →

What is Docling?

Docling keeps swallowing new formats, and now the parsing engines behind them are swappable.

Docling releases every three to four days, alternating feature drops with tight fix releases. The current one is purely corrective: DOCX headings detected by outline level when the style is not literally named Heading, Markdown tables keeping their last cell without a trailing pipe, and the service client serializing engine options in full. Format coverage now spans PDF, Office, ODF, HTML, JATS, email, audio and video.

Read the full Docling trajectory →

btw vs Docling: editorial side-by-side

B
btw
AI-ASSISTANTS
2.5

btw is turning into an agentic R harness that no longer needs you to be in R

◆ Current state

btw assembles context about an R session — packages, documentation, files, data frames — and hands it to an LLM through ellmer, with btw_app() as a chat interface. Over the last year it has grown well past context assembly: LLMs can document, check, test and measure coverage of a package, read CLAUDE.md and AGENTS.md as project context, fetch skills from packages or GitHub, and inspect the source of any installed namespace. Much of this is now reachable from a terminal CLI rather than only from an R prompt.

◆ Where it's heading

The direction is from describing a session to operating on it, and from inside R to outside it. Each release adds either a tool group that lets a model do something (document, check, test, cover; read namespace source; fetch skill resources) or a CLI command that removes the need to start R first. The 1.2.0 tool renaming — session becoming sessioninfo, search becoming cran, files_read_text_file becoming files_read — reads as the naming cleanup you do when you expect a lot more tools to follow.

◆ Prediction

The CLI has been absorbing one tool family per release (skills, then pkg desc and pkg src) while the R-side tool groups stay ahead of it, so the next releases likely continue exposing existing tool groups as terminal commands rather than adding new capabilities.

D
Docling
AI-ASSISTANTS
6.3

Docling keeps swallowing new formats, and now the parsing engines behind them are swappable.

◆ Current state

Docling releases every three to four days, alternating feature drops with tight fix releases. The current one is purely corrective: DOCX headings detected by outline level when the style is not literally named Heading, Markdown tables keeping their last cell without a trailing pipe, and the service client serializing engine options in full. Format coverage now spans PDF, Office, ODF, HTML, JATS, email, audio and video.

◆ Where it's heading

The engine layer is where the interesting movement is. Docling is shifting from one opinionated pipeline to a set of interchangeable layout, table and OCR backends the caller picks per run, which turns the library into a harness for models rather than a fixed parser. A second thread: the project shipped agent skills for itself in v2.118.0 and a separate docling-client package in v2.120.0, both pointing at being consumed programmatically rather than only imported. The structural-inference work — heading levels from font weight, now from DOCX outline levels — shows the parser learning to read documents that never declared their own structure.

◆ Prediction

Expect the engine-selection surface to keep widening, with OCR joining layout and table structure as a CLI-selectable backend. The steady stream of format-specific crash fixes suggests coverage is outrunning hardening, so more of these short corrective releases are likely between feature drops.

Alternatives to btw and Docling

Other ai-assistants products tracked by Sparkpulse, ranked by recent ship velocity. Each card links to a full editorial trajectory and lets you pivot into a head-to-head comparison with either btw or Docling.

See all btw alternatives → · See all Docling alternatives →

Recent activity from btw and Docling

Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.

  1. 2d agoDoclingDOCX outline-level headings and Markdown table cell fixes
  2. 4d agoDoclingRelease CI fix, no user-facing changes
  3. 5d agoDoclingHeading levels inferred from font weight; pluggable CLI engines
  4. 9d agoDoclingOutlook .msg support and Unlimited-OCR grounding
  5. 11d agoDoclingLayout label and PDF picture-in-table fixes
  6. 13d agobtwbtw 1.4.0 adds CLI commands for reading R package source
  7. 15d agoDoclingEBCDIC backend, docling agent skills, all PP-OCR languages
  8. 1mo agobtwbtw 1.3.0 makes skills fetchable from the terminal
  9. 4mo agobtwbtw 1.2.1
  10. 5mo agobtwbtw 1.2.0 renames its tool groups ahead of expansion
  11. 7mo agobtwbtw 1.1.0 lets an LLM document, check and test an R package

Frequently asked questions

What is the difference between btw and Docling?

They serve adjacent needs but don't currently overlap on shipped themes. Docling is currently shipping more aggressively (velocity 6.3 vs 2.5), with 0 editorial sparks in the last 30 days against 0. See the at-a-glance table above for a side-by-side breakdown of velocity, recent sparks, and editorial themes.

Is btw better than Docling?

Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. Docling is currently shipping more aggressively (velocity 6.3 vs 2.5), with 0 editorial sparks in the last 30 days against 0. For your specific use case, the alternatives sections above list other ai-assistants products to evaluate alongside.

What are the best alternatives to btw?

Top btw alternatives in ai-assistants are ranked by recent ship velocity. Browse the "btw alternatives" section above for the current picks, or visit /alternatives/btw-r for the full list with editorial commentary on each.

What are the best alternatives to Docling?

Top Docling alternatives in ai-assistants are ranked by recent ship velocity. Browse the "Docling alternatives" section above for the current picks, or visit /alternatives/docling for the full list with editorial commentary on each.