Chat

Overview

Chat is an AI assistant built into Tailglow. Ask questions about your metrics, views, collections, and records in natural language, across any project on your team. Chat uses your account’s permissions for supported Tailglow actions, so it can only see and change what you can.

Getting started

Tailglow uses AI managed by Tailglow. When several models are available, use the model picker to choose one. Click the model and effort label to change your selection. When only one model is available, this opens its effort choices directly. Free tokens are shared across your team and its projects. They apply first, then usage is billed to the team if it has a payment method or is on the Enterprise plan.

To use your own provider account, add an Anthropic or OpenAI key in Team Settings > Agents, then select that provider’s model in Chat. Adding or deleting a key does not switch an existing conversation’s payer. If its selected model becomes unavailable, choose another model explicitly. A new chat opens on your saved model when it’s available; otherwise it opens on Tailglow or another model you can use, and your saved choice returns once it’s available again.

The Tailglow name stays the same when the underlying model changes. Open the information drawer in Agents settings, or click the free-token balance beside the chat picker, to see the current provider, model, supported token rates, and balance. The displayed rates include a 15% service fee; no additional service fee is added afterward.

Every new team starts with 10 million Tailglow AI tokens. When your team’s latest monthly invoice is paid, Enterprise teams receive a reset to 100 million tokens, including teams that pay by invoice without a saved payment method. Pro teams with a payment method receive a reset to 10 million tokens. This is included, not a prepaid purchase or an additional charge. Unused AI credits, including higher balances, are replaced by the monthly allowance. Usage since the end of the invoiced month counts against it. Pro teams without a payment method keep their remaining tokens but receive no monthly reset.

Chat history remains accessible when sending needs action. Without a model, or without enough credits on a Pro team with no payment method, the composer explains what to change. Your draft is kept. Provider-key models do not spend Tailglow credits. Teams with a payment method, and Enterprise teams, can continue after their free balance reaches zero; that usage is billed.

Using Chat

Open Chat with Command + / or the chat icon. It is available on every page: inside a project, and on team pages such as billing, users, and roles.

1. Open Chat.
2. Type a question and press Enter.

Chat reads the page you are on, so a question about “this view” or “this metric” means the one in front of you. If you move to a different project mid-conversation, Chat notices and keeps going. When that makes a request ambiguous, it asks rather than guessing.

Responses stream as they are generated. You can attach images to a message.

Example questions

• “What are the top 5 endpoints by error rate this week?”
• “Show me the trend of page views over the last 30 days.”
• “Why did latency spike yesterday at 3pm?”
• “Create the same metric in my sandbox project.”
• “Which roles can delete metrics?”

Chat history

Open the chat panel and switch to the chat list to revisit previous conversations. Your chats follow you between projects, so the list is the same wherever you open it.

The assistant keeps useful notes as it works. For long managed conversations, it also summarizes older work near a 250,000-token context target. Recent exchanges, complete tool calls and results, and your current request remain available alongside that summary. The full transcript remains in your chat history.

Compaction runs between model calls. If a summary fails, the assistant retains the original context and uses additional headroom toward a 400,000-token operating limit, subject to the provider’s capacity. It tries to reduce older context before asking you to shorten an unusually large request. Automatic managed compaction is covered by Tailglow and does not spend your free tokens.

Token billing uses the provider’s reported usage for every generation, including tool continuations. Input, cached input, cache writes, and output are separate categories; reasoning is already included in output. An estimate used to fit context is never used to calculate your bill. Stopping a response can leave a provider generation finishing in the background; its reported usage still counts. If usage cannot be recovered, the unknown remainder is covered by Tailglow, while the answer already received remains available.

Managing chats

Deleting a chat removes it from your chat list. Its messages may be retained for billing records.

Chats are scoped to your user account within a team. Other team members cannot see them.

Permissions

Chat access is controlled by the Chats permission in your role. Read access opens chat history, write access sends messages, and delete access removes chats.