Contact
ansicode is a one-purpose reference site — there's no support contract, no signup, and nothing to monetise from talking to you directly. This page exists so you always have a way to reach a human when something is wrong, and so the site's transparency story is complete.
Try self-serve first
Most of the time you'll get an answer faster by reading what the site already knows. The decoder explains escape sequences token-by-token; the dataset ships every documented sequence as JSON / CSV; the terminal support matrix shows which terminals render which features. If your question is "what does \x1b[…] mean" or "does iTerm2 support …", check those before emailing — answers there are instant and always up to date.
Bug reports, factually wrong content, missing sequences, broken links, and reproducible regressions all go to a single address. Plain text is preferred; please include the page URL and the byte sequence (with `\x1b` form) if relevant. Replies usually land within a few days — there's no SLA but I read everything.
Why a fact is on the site
Every reference page cites the standard or document it descends from — ECMA-48 (the 1976 standard, 5th edition 1991), the xterm Control Sequences reference (xterm-ctlseqs), DEC's STD 070 / VT-series technical manuals, and per-emulator documentation for modern terminals (kitty, iTerm2, Windows Terminal, ghostty, alacritty, wezterm, gnome-terminal, konsole). If you believe a page contradicts one of those sources, mention which one — that's the fastest path to a correction.
What this page is not
There's no contact form, no signup, no chat widget, and no way to leave a comment. The decoder will not store anything you paste into it. The site does not run analytics, set cookies, or log who emails — your message reaches an inbox and stops there.