# Polylane for ChatGPT and Codex: ask about production in chat

> Published 2026-10-29 · Updated 2026-11-18 · Canonical: https://polylane.com/changelog/2026-10-29-polylane-for-chatgpt/

Polylane is now an app in ChatGPT and Codex, so engineers can ask about their own production and get issue cards, log lines, charts and dependency graphs back in the chat.

Video: https://polylane.com/videos/for/polylane-for-chatgpt-1080p60.mp4

Product Hunt: https://www.producthunt.com/products/polylane/launches/polylane-for-chatgpt

## What changed

Polylane is now an app in ChatGPT and Codex. Ask what changed, read logs and metrics, trace dependencies and investigate issues, all from your own code and infrastructure. Add the [Polylane plugin](https://polylane.com/for/chatgpt/), sign in, pick a workspace and ask.

### Views in the conversation

Answers come back as views in the chat: issue cards, log lines, metric charts, recent changes and dependency graphs. Every resource in the workspace can be drawn as one context graph, with active issues marked, and an active-issues panel sits beside the conversation. Select anything in a view to ask about it next.

### Tools named for the job

The plugin gives ChatGPT one tool per question you would ask: what changed, what it logged, what it reaches. ChatGPT picks the right one, and every answer links back to the evidence in Polylane.

### A guided first run

The first time you ask, Polylane confirms the connection, picks your workspace, summarises what is connected and suggests a few first questions.

## Issue channels in Slack

An investigation at the severity you choose now opens its own public Slack channel. Polylane posts milestones there, answers people in threads, names the channel after the issue and bookmarks the issue, the thread and the pull request. You choose who joins, from the Slack integration settings or from Slack itself.

## Why it matters

Many engineers already ask ChatGPT and Codex about their code. With Polylane connected, the answers come from their own production: the issues, logs, metrics and recent changes in the workspace, each with a link back to the evidence in Polylane.

## How to use it

1. Add the Polylane plugin from [Polylane for ChatGPT](https://polylane.com/for/chatgpt/).
2. Sign in with your Polylane account and pick a workspace.
3. Ask, for example: "What changed before the errors on the checkout service started?"

## Related

- [Polylane for ChatGPT](https://polylane.com/for/chatgpt/)
- [Polylane for Codex](https://polylane.com/for/codex/)
- [Polylane in Slack](https://polylane.com/product/slack/)
- [Context graph](https://polylane.com/product/context-graph/)

## Improvements

- Slack: Tables, timelines, stats and charts render as native Slack blocks
- Slack: Polylane reads forwarded messages and files, and links a Slack member it recognises to their Polylane account
- Slack: In Slack Connect channels, only members of your own team can ask Polylane for work
- GitHub: A daily dependency scan files one issue per repository for critical and high severity upgrades
- Pull requests: Reviewers on Polylane's pull requests follow fixed rules, and can be set per repository
- Console: Save list filters as personal views on Issues, Escalations and Threads
- Console: Chat about an escalation from its page, and the overview leads with what to do next
- Google Cloud: Each Cloud Monitoring alert policy is assessed, and GCP projects are read and analysed like AWS accounts

## Fixes

- MCP: The MCP grant is kept when a client retries a token refresh
- Console: Dismissed notices stay closed
- Console: Merged pull requests stay out of the Open filter
- Console: Your written prompt is kept when an example question previews
- Billing: One credit usage email instead of several, and invoices open with a current Stripe link
- GitHub: Mentions are answered only in the workspace that knows the repository
- Vercel: A 403 from Vercel is no longer read as zero projects

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