← Claude Code Hub
Nov 21, 2026 · 5 min read ✦ Tip #279

easel in Claude Code: Claude draws charts right in your terminal

easel is the mod Claude Code ships with to draw charts in your terminal: when you ask, and unasked under Prometheus, Grafana or Datadog results. What you need to get it, and how to turn the automatic ones off.

easel in Claude Code: a line chart of p95 latency drawn under the result of a Prometheus MCP call, and the three ways to use it: automatic under metrics, on request, or off from /config

TL;DR With a claude.ai subscription on macOS or Linux, say "chart this" after any result with numbers and Claude draws it in the terminal. If the charts that show up on their own under your metrics MCPs are too much, open /config, search Auto charts and switch it off: the ones already drawn disappear too.

easel is the built-in mod Claude Code announced in v2.1.330 to draw charts inside the conversation. It does two things: it gives Claude a tool, easel - chart, which Claude calls when numbers read better as a chart, and it draws a chart on its own under an MCP metrics result, with no action from Claude. Everything is drawn in terminal characters, right in the transcript: if you meet the requirements, you no longer need an ASCII chart skill.

The chart that shows up on its own

With a test MCP server that answers a Prometheus range query (the p95 latency of two services over two hours), Claude calls the tool and this appears under the result in v2.1.330:

  Called prometheus
  ⎿  http_request_duration_seconds:p95 · Nov 21 2026 07:00 → 09:00 UTC
     a checkout  max 0.934 at 08:20  last  0.2  min 0.161  mean 0.275
     b search    max  0.14 at 07:25  last 0.14  min   0.1  mean 0.123
         │                                                                 ⢀⠎⠉⠉⠉⠉⢣
     0.8 ┤┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈⢠⠃┈┈┈┈┈┈⢣┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈
         │                                                               ⢠⠃        ⠣⡀
     0.6 ┤┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈⡰⠁┈┈┈┈┈┈┈┈┈┈⠑⡄┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈
         │                                                             ⡰⠁            ⠘⢄
     0.4 ┤┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈⢀⠖⠁┈┈┈┈┈┈┈┈┈┈┈┈┈┈⠈⢆┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈
         │                                                          ⢀⠎                 ⠈⢆
     0.2 ┤⠤⠤⠤⠤⠤⠤⠤⠤⠤⠤⠤⠤⠤⠤⠤⠤⠤⠤⠤⠤⠤⠤⠤⠤⠤⠤⠤⠤⠤⠤⠤⠤⠤⠤⠤⠤⠤⠤⠤⠤⠤⠤⠤⠤⠤⣀⣀⣀⣀⣀⣀⣀⣀⣀⣀⣀⣀⣠⠊┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈⢣⡠⠤⠤⠤⠤⠤⠤⠤⠤⠤⠤⠤⠤⠤⠤⠤⠤⠤⠤⠤⠤⠤⠤⠤⠤⠤⠤ a
         │⠒⠒⠒⠉⠉⠉⠉⠉⠉⠉⠉⠉⠉⠉⠉⠉⠉⠉⠉⠉⠉⠉⠉⠉⠉⠉⠉⠉⠉⠉⠉⠉⠉⠉⠉⠉⠉⠉⠒⠒⠒⠒⠒⠒⠒⠒⠒⠒⠒⠒⠒⠒⠒⠒⠒⠒⠒⠒⠒⠒⠒⠒⠔⠒⠒⠒⠒⠒⠒⠒⠒⠒⠒⠒⠒⠒⠒⠒⠒⠒⠒⠒⠒⠒⠒⠒⠒⠉⠉⠉⠉⠉⠉⠉⠉⠉⠉⠉⠉⠉⠉⠉⠉⠉⠉⠉⠉ b
         └┬────────────┬────────────┬────────────┬─────────────┬────────────┬────────────┬─────────────┬────────────┬
          07:00        07:15        07:30        07:45         08:00        08:15        08:30         08:45    09:00
     auto chart · turn off in /config: Auto charts

At the top, the metric and the time span. Below it, one line per series with its max, last, min and mean, which is what you read before the curve. The last line tells you the chart is automatic and where to turn it off.

The model doesn't draw it: the mod draws it when it renders the result. Claude only gets a line saying easel already charted that result, so it doesn't make the same chart again.

According to its tool description in the binary, automatic charts come from Prometheus, Grafana and Datadog results. Without being told which columns to use, the tool also reads Graphite, CloudWatch, Cloud Monitoring and AWS Cost Explorer formats.

Ask for a chart

1. Get the numbers into the conversation

A query, a command, a CSV. For example:

Count the lines of each .md file in refs/ with wc -l and draw me a bar chart of it.

2. Look at what Claude calls

● easel - chart (MCP)(data: [{"file":"article.md","lines":26}, ...], x: "file",
                     y: ["lines"], form: "bars", title: "Lines per refs/*.md file", unit: "lines")
  ⎿  Lines per refs/*.md file · lines
     article.md         ▆▆▆▆▆▆▆▆▆▆▆▆▆▆▆▆▆▆▆                                                                    26 lines
     buffer.md          ▆▆▆▆▆▆▆▆                                                                               11 lines
     carousel.md        ▆▆▆▆▆▆▆▆▆▆▆▆▆▆▆▆▆▆▆▆▆▆▆▆▆▆▆▆▆▆▆▆▆▆▆▆▆▆▆▆▆                                              57 lines
     claude-code.md     ▆▆▆▆▆                                                                                   7 lines

Those are the first 4 of 17 bars, and the call is trimmed. Claude picked the form; if you want a different one, name it:

form What it draws
line Lines over time (the default when there are dates)
columns Columns standing on zero, one per day, month or other even step
sparks A small row per series, all on one scale: for many series
bars Horizontal bars, one per category (the default when there are names)
share The parts of a whole as a single bar, what a pie chart would show

The limits you'll hit: the data travels inside the call and must stay under 64 KiB. It reads no files and no results Claude Code cut for being too long: ask for fewer rows or a shorter span. And it doesn't count or bucket for you, so pass totals already computed.

Turn off the automatic charts, or the whole mod

1. Open /config and search chart

  ❯ Auto charts · cc-plugin-easel                   on
    Auto charts: servers to skip · cc-plugin-easel  ›

2. Set Auto charts to off

  ⎿  Set Auto charts (cc-plugin-easel) to off

The mod reloads on the spot and the automatic charts already in the conversation disappear; switch it back on and they return, under older results too. The charts you ask for keep working.

3. If only one server bothers you, skip it

In Auto charts: servers to skip, list servers separated by commas, by the name their tools use: grafana for mcp__grafana__query.

4. To remove it entirely, /plugin → Installed → cc-plugin-easel → Disable plugin. Then Claude doesn't get the tool either.

The options are saved in your ~/.claude/settings.json:

{
  "pluginConfigs": {
    "cc-plugin-easel@builtin": { "options": { "autoCharts": false } }
  }
}

Project settings aren't read for this: the v2.1.330 debug log says so in as many words (project settings are not read). A .claude/settings.json in the repo won't turn charts off for your team; each person does it in their user settings.

If you don't see it

  • Your account. It needs a claude.ai subscription: Pro and Max, plus Team and Enterprise where available. With an API key, Bedrock, Vertex or Foundry it doesn't show up.
  • Your version and system. v2.1.321 or later (v2.1.326 on Team and Enterprise), on macOS or Linux outside WSL. Not on Windows.
  • Your organization. The binary turns it off in organizations with HIPAA or zero data retention.
  • claude -p. In headless mode Claude doesn't have the chart tool.

To check, /plugin → Installed: if it's there, you'll see cc-plugin-easel as a plugin and easel as a built-in MCP server. It's one of the mods Claude Code ships with, like You should know.

It adds no fixed context: claude plugin details cc-plugin-easel@builtin reports ~0 tok per session, and the chart tool is deferred, loaded only when Claude searches for it. What you pay for is the call when you ask for a chart, with the data inside. If you want an interactive dashboard of your data rather than a chart in the terminal, see Claude Data.

Official docs: Mods built into Claude Code · Changelog, v2.1.330

Tested with Claude Code v2.1.330 on Linux, on November 21, 2026.

Found this useful? See more of wmedia.es in your Google results.

Add wmedia.es as a preferred source on Google
FREE GUIDE

From the terminal to Desktop, as a guide.

Moving from the terminal to Claude Code Desktop is easy to start and easy to leave half done. 8 pages to keep beside you: day one, the map of the window, the shortcuts and your first cloud routine.

  • 1. Day one import your sessions
  • 2. The window map and shortcuts
  • 3. Conversations which to open and two prompts
  • 4. Panels which to use for what
  • 5. Routines your first in the cloud
Are you a professional Web developer?

You'll receive the guide by email · You join the Gravitas newsletter · Unsubscribe anytime

of 8
#

Wmedia · 8 pages
FREE GUIDE · 8 pages · 2 prompts

From the terminal to Desktop, as a guide.

Moving from the terminal to Claude Code Desktop is easy to start and easy to leave half done. 8 pages to keep beside you: day one, the map of the window, the shortcuts and your first cloud routine.

Are you a professional Web developer? · Unsubscribe anytime
How I use AI

My Claude Code workflow.

The skills, agents and instructions I use as a professional Software Engineer. It's called Craft, and it's a plugin you can install.

See the skills

Moving from the terminal to Claude Code Desktop?