# Charts, tables and architecture diagrams in console chat

> Published 2026-11-06 · Updated 2026-11-18 · Canonical: https://polylane.com/changelog/2026-11-06-visuals-in-console-chat/

Polylane can now answer in the console with a chart, a table, a comparison or an architecture diagram, and each visual can be shared on its own link.

Blog: https://polylane.com/blog/what-even-is-code-mode/

## What changed

Ask how something works or how two options compare, and the answer comes back as a visual. Polylane checks each visual in a browser before it shows it to you. Privacy Mode, which keeps your workspace's data out of model training, is now available on every plan.

### Architecture diagrams with real logos

Architecture diagrams show each component with its real logo, its boundaries and labelled arrows, and can show a before and after in one picture. Expand a diagram or download it as a PNG. Charts and traces can be copied as JSON.

### Share a visual

Each visual has its own link and sharing setting, so you can share one without sharing its thread. When Polylane revises a visual, it keeps one link with numbered versions.

## Why it matters

Some answers read better as a picture: how a request moves through your services, or how two designs compare. A diagram with real logos and labelled arrows can go straight into a design doc or a Slack thread, without sharing the thread it came from.

## How to use it

1. Open a thread in the console and ask, for example: "Draw how a request reaches the checkout database."
2. Expand the diagram, or download it as a PNG.
3. To share one visual, change its own sharing setting. The thread keeps its own.

## Related

- [Polylane console](https://polylane.com/product/console/)
- [Context graph](https://polylane.com/product/context-graph/)

## Improvements

- Context graph: Filter the context graph by tier and save the view, as on the Threads list
- Cloudflare: Flagship apps and their flags join the context graph, and a flag change shows as a possible cause of an issue
- Cloudflare: Workers Issues and other Cloudflare notifications become alerts that Polylane investigates
- Cloudflare: K2 streams, Workers VPC services and Email Sending join the context graph, and investigations can query the Cloudflare SQL API
- Vercel: Vercel Services, Daemons, shared environment variables, PrivateLink endpoints and Secure Compute networks join the context graph, linked to AWS
- GitLab: Merge requests get the production impact review, inline suggestions and answers to `@polylane`, and projects get the daily dependency scan
- Escalations: An ask you finish in a provider's dashboard gets a Guide me button that points at each control
- Escalations: The escalations digest email is sent once a week
- Console: The issues list shows when each issue was first seen and the resource it affects, with filters for both
- Console: Timestamps show in your own time zone, in the console and in Slack
- Console: An Automated tab on Threads lists the threads Polylane started, and third-party services show their own logos
- Pull requests: Observability suggestions can be turned off for a workspace or a repository, and Polylane opens no new fix for a problem whose fix a person closed in the past 30 days

## Fixes

- MCP: MCP clients stay signed in past 30 days
- Pull requests: A title or description a person edited is kept, and advice people declined is not repeated
- Issues: Monitoring issues that go quiet for seven days resolve
- Slack: Polylane posts nothing when it has nothing to add
- Console: A streamed reply with several steps renders once
- Console: The LangSmith and Braintrust logos show in dark mode

[All updates](https://polylane.com/changelog/)
