DEV Community

TeX64
TeX64

Posted on

I Stopped Dreading LaTeX Error Logs — Here's What Changed

#latex #macos #productivity #ai

Let me describe a scene every LaTeX user has lived:

It's 11pm. You've been writing all day. You hit compile, walk away to make tea, come back to find this in the log:

! Package inputenc Error: Unicode character 的 (U+7684)
(inputenc)                not set up for use with LaTeX.

See the inputenc package documentation for explanation.
Type  H <return>  for immediate help.
 ...
l.1847 ...rithm based on the work of Li et al. 的

?
Enter fullscreen mode Exit fullscreen mode

And you just stare at it. You didn't even type a Chinese character. Where did that come from? Is it in a bibliography entry? A comment someone else left? A package that auto-inserted something?

This is the specific kind of LaTeX suffering that has no good solution — until recently.

The problem with current LaTeX debugging tools

When your compile log hits 400 lines, the challenge isn't understanding individual error messages. It's triage — figuring out which errors are root causes and which ones are just cascading side effects of a single upstream problem.

I used to do this manually. Open the log. Search for !. Copy the error. Google it. Read StackOverflow answers that almost match my situation. Try a fix. Recompile. Different error. Repeat.

Calling ChatGPT helps a little. But here's the issue: ChatGPT doesn't know your codebase. You paste a snippet, it gives you a generic answer. It doesn't know what packages you've loaded, what custom commands you've defined, or what your root file structure looks like. So you get answers like "make sure amsmath is loaded" when you already have amsmath loaded and the real problem is something three files upstream.

What TeX64's Axiom does differently

TeX64 is a local-first LaTeX editor for macOS. Its AI assistant, Axiom, has access to your entire project — all .tex files, your actual compile log, and your BibTeX. Not a snippet you pasted. The whole thing.

This changes the quality of the answers dramatically.

Here's a real example. I had a project with 23 errors in the log. I typed "analyze these errors" into Axiom's chat. The response:

"You have 23 errors but they stem from 3 root causes:

Root cause 1 (generates 18 errors): macros.tex line 34 defines \proof using \newcommand, but the amsthm package already defines a proof environment. This causes a naming conflict that cascades throughout the document.

Root cause 2 (generates 4 errors): chapter4.tex line 209 has a \begin{table} with no matching \end{table} — LaTeX loses track of the environment and the errors pile up from there.

Root cause 3 (1 error): bibliography.bib entry Zhang2019 has a { in the title field that's not closed.

I'll show diffs for each fix. Want to start with root cause 1?"

That analysis would have taken me an hour of manual log reading. It took Axiom about 20 seconds.

The diff-before-apply approach

One thing Axiom does that I deeply appreciate: it shows you exactly what it wants to change before changing anything.

Every suggestion comes with a diff:

  % macros.tex, line 34
- \newcommand{\proof}[1]{\textit{Proof.} #1 \qed}
+ \newcommand{\myproof}[1]{\textit{Proof.} #1 \qed}
Enter fullscreen mode Exit fullscreen mode

And then: "Apply this change?"

You see what's happening, you understand why, and you decide. Axiom never silently edits your files. For a thesis or paper where every word matters, this is the right way to work with AI.

Other things I've used it for

Once I started using TeX64, I found Axiom useful for things beyond error fixing:

Generating math I don't remember the syntax for: I can describe a formula in plain English — "the limit as n approaches infinity of the sum from k=1 to n of 1/k^2" — and get clean LaTeX back. No more digging through the LaTeX math symbol list.

Literature: paste title, get BibTeX: Tell Axiom you want to cite a paper, it searches arXiv and drops the BibTeX entry into your .bib file. This alone has saved me probably 20 minutes per writing session.

Package conflict diagnosis: When adding packages to a big project causes mysterious new errors, Axiom can spot ordering conflicts. "You're loading cleveref before hyperref — switch the order."

Honest limitations

TeX64 is macOS only. If you're on Windows or Linux, this isn't for you.

You need MacTeX or TeX Live installed separately — TeX64 is the editor, not a LaTeX distribution. The app's environment diagnostics will walk you through setup if you don't have it already.

AI features require internet. Compilation itself is fully local and offline-capable. On my M2 MacBook Air, a 120-page document compiles in about 8 seconds — no internet bottleneck on the compile step.

There's a free tier to start with. If you end up using Axiom heavily, there are paid plans.

The thing that surprised me most

I expected Axiom to be useful. What I didn't expect was how much it changed my relationship with errors.

Before: compile error → dread → 45-minute debugging session.

After: compile error → "let Axiom look at this" → usually fixed in under 5 minutes.

The psychological difference is real. When you're not scared of errors, you compile more often. When you compile more often, you catch problems earlier. It's a virtuous loop that actually makes you write more.

If you're on a Mac and spend meaningful time in LaTeX, it's worth trying.

→ tex64.com

Top comments (0)