Use AI Chat

Chat is useful for grounded questions, synthesis, planning, and workspace-aware follow-up. Use this guide when you need a reliable answer or an AI-assisted draft.

Start a focused chat

1. Check the project picker.
2. Open Chat.
3. Select New chat if you are changing topic.
4. Choose the Chat Assistant.
5. Choose source groups.
6. Ask a specific question.

Good prompt:

Using Memory, Docs, Tickets, and Risks, summarize what is blocking the Enterprise onboarding launch. Cite the records I should review before changing priorities.

Weak prompt:

What should we do?

Choose a Chat Assistant

1. Use Default for general questions.
2. Use Chief of Staff for priorities, operating cadence, blockers, risks, and execution summaries.
3. Use CTO for architecture, implementation tradeoffs, and engineering review.
4. Use Memory for direct questions about remembered facts.
5. Use Weekly Review for progress, drift, and planning summaries.

Your default Chat Assistant can be saved in user settings.

Choose source groups

1. Open the source picker.
2. Enable the sources the answer should use.
3. Disable sources that should not influence the answer.
4. Ask for citations when the answer will guide real work.

Source groups include Web, Memory, Docs, Tickets, Decisions, Risks, and Snapshots. If a source is disabled, Chat may give an incomplete answer even when the missing information exists elsewhere in TOW.

Mention workspace records

1. Use a visible display ID such as a ticket key, decision ID, risk ID, snapshot ID, or doc reference.
2. Ask the question around that record.
3. Request related records or evidence.

Example:

Explain the implementation risk around APP-42 using linked docs, decisions, and active risks. What should I verify before moving it to review?

Attach files

1. Select the paperclip button or drag files into Chat.
2. Wait for upload to finish.
3. Ask the question after the attachment chip appears.
4. Tell Chat how the file should be used.
5. Remove attachments that should not be part of the turn.

Attached files are context for that chat turn. Important durable facts should still be captured in Docs or Memory after review.

Ask for evidence

1. Ask Chat to cite the records behind its answer.
2. Open the Sources panel.
3. Review Memory Basis when it appears.
4. Open cited docs, tickets, decisions, risks, or snapshots.
5. Correct stale source records instead of only correcting the chat response.

Use this pattern for customer, technical, financial, legal, security, or planning decisions.

Apply a pending action

Some answers include pending actions such as creating a doc, updating a doc, creating a ticket, updating a ticket, commenting on a ticket, or linking tickets.

1. Read the action summary.
2. Confirm the active project scope.
3. Confirm the target item.
4. Select the pending action.
5. Wait for the applied status.
6. Open the created or updated item.
7. Review and edit the result.

Workspace writes

Applying a pending action writes to the workspace. Treat it like accepting an AI proposal.

Retry or stop a response

1. Use Stop response when the answer is going in the wrong direction or sources were wrong.
2. Change mode, sources, or prompt.
3. Use Retry last response to run the last user message again.
4. Review the new answer and sources.

Manage chat history

1. Use the chat rail to search old conversations.
2. Star important conversations.
3. Rename conversations with useful titles.
4. Delete conversations that no longer need to be kept.
5. Check project scope if an expected conversation is missing.

Project-scoped chats are saved separately from All Projects chats.

Related concepts: Chat, Inbox, Search and references.