Ask Weaver
Ask Weaver questions about your product, customers, and plans, or ask it to help create something. It draws on the product context Devplan builds from connected code, tickets, documents, and conversations, so you can connect what customers need with what your team has planned and delivered.
Use it to investigate a launch risk, understand why a feature exists, prepare a customer update, or turn an idea into a plan. You can move from a broad question to its supporting evidence and a useful next step in the same conversation.
What you can do
Open Ask Weaver, type a question or describe the result you want, and select Send. Add files, images, or relevant document and issue links to focus the conversation. Supported links show a preview when the connected service and your access allow it.
Useful questions include:
- “What changed in billing this week, and what evidence supports that?”
- “Which customer requests relate to this project?”
- “What remains uncertain about the launch?”
- “Why did we choose this approach, and what decisions are recorded?”
Mention the project, customer, feature, or time period where possible. Ask Weaver to separate confirmed findings from assumptions when that distinction matters.
For example, start with “Which onboarding problems have customers raised recently?” Then ask “Which are already addressed by planned work?” and “Draft a short update explaining what we know and what still needs a decision.” Each follow-up builds on the conversation, so you can refine the result without starting the investigation again.
Start with an action
Select Actions beside the message box to start a guided conversation for a common task. Actions help you get to a useful output without having to write the entire request yourself. Examples include:
- Research: synthesize recurring customer needs or investigate competitors.
- Understand the product: explain a feature or trace the decisions behind it.
- Plan work: write a product spec or draft tickets.
- Communicate: prepare a product update, relevant customer updates, or an onboarding guide.
Choose an action, then supply the audience, scope, or other details Weaver needs. You can refine the output through follow-up messages just as you would in any other chat.
When Weaver proposes projects, review and edit the candidates, select the ones you want, and create them from the chat. For Jira or Linear ticket drafts, review the content and destination before selecting Create tickets. The preview lets you turn the discussion into work while choosing exactly what gets created.
Continue an investigation
Your previous conversations appear in chat history. Search by conversation title, reopen a chat to continue it, or mark it as a favorite for quick access. You can rename a conversation by selecting its title, which makes ongoing topics easier to find.
Use New session when you want to start a separate discussion. You can also stop a response while it is running and send a follow-up to redirect the investigation.
Where to use it
Use Ask Weaver in Devplan for workspace conversations. You can also interact with Weaver through the Slack and Microsoft Teams integrations. To use workspace context in another AI assistant, connect Devplan MCP; that client controls its own conversation and tool use.
Radar surfaces a daily view of what needs attention. Ask Weaver is where you can bring your own question and explore it in depth.
Check an answer
Open the evidence references in an answer to inspect the sources behind it. This helps you check a conclusion before using it in a decision or sharing it with someone else. If an answer is incomplete, add the missing context or ask what was checked and which evidence is still needed.
For questions about using Devplan itself, refer to this documentation. For questions about your own product, use workspace evidence and Live Docs.
Connections and actions
Additional connections can give Weaver tools to retrieve information or perform supported actions in other services. For example, a connection can let an investigation use information from a service beyond the sources already in your product knowledge. What Weaver can do depends on the connected account and allowed tools. State whether you want an explanation, a draft, or an actual change.
Troubleshooting
If an answer is missing expected context, confirm the active workspace, source access, configured scope, and processing status. If a connected service needs attention, reconnect it through Integrations. Do not assume an empty result means the source contains no relevant information.