Unable to fetch Word doc summaries on version 0.4.0
Nobody has claimed this yet.
- Dominant language
- PowerShell
- Stars
- 1k
- Forks
- 132
- Avg merge
- 5d 19h
- Merged PRs (30d)
- 6
Description
Input:
npx -y "@microsoft/workiq@0.4.0" ask -q "Summarize the contents of doc-name-placeholder. What are the main sections, key design decisions, and technical details?" -f "doc-url-placeholder" -v
Output:
I'm unable to summarize doc-name because its contents aren't accessible to me under your organization's security policies. The file upload succeeded, but the document text itself can't be read, so I can't reliably identify sections, design decisions, or technical details without seeing the content.
What I can do right now (pick any):
- Paste the document text (or key sections) here, and I'll produce a concise, structured summary immediately.
- Share an accessible copy (e.g., export to PDF or remove restricted permissions) and re-upload it.
- Tell me what you want emphasized (architecture, security model, Android specifics, performance, dependencies), and I'll tailor the summary once the text is available.
Once I can read the document, I'll deliver:
- A section-by-section outline
- Key design decisions with rationale and trade-offs
- Technical details (components, APIs, data flow, security, build/deploy notes)
- A short TL;DR for quick consumption
If you'd like, paste just the table of contents first-I can map the structure and call out likely focus areas even before the full text.
Notes:
I was able to link the same doc in M365 Copilot Chat and that was able to generate a summary so seems M365 Copilot has access but WorkIQ doesn't?
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reproducing the npx @microsoft/workiq@0.4.0 ask command with the Word document URL and compare its behavior with M365 Copilot Chat. Trace the document retrieval and text-access path; done means the command can read the document contents and produce the requested section, design-decision, and technical-detail summary.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- node.js
- Domain
- backend, cli
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100