workiq 0.4.0.16790+fddb48205182762e636ad9e581c0c81540b2add2 does not cache identity
Open
Nobody has claimed this yet.
authZ
- Dominant language
- PowerShell
- Stars
- 1k
- Forks
- 132
- Avg merge
- 5d 19h
- Merged PRs (30d)
- 6
Description
I have workiq set up as my mcp using the following:
"workiq": {
"command": "npx",
"args": [
"-y",
"@microsoft/workiq",
"mcp"
],
"type": "stdio"
}
I noticed is start failing with this message:
{
"response": null,
"conversationId": null,
"error": "An error occurred while processing your request."
}
every time I run the mcp tool with
npx -y @microsoft/workiq ask -q "who am i"
I get a popup where I need to pick my work account.
That is never cached and it occurs every time.
That makes the mcp calls fail all the time.
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 with the shown npx @microsoft/workiq ask -q "who am i" entry point and MCP stdio configuration; trace how work-account selection is handled across repeated invocations. Done means the account picker is not shown on every run and the command returns a successful response.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- node.js
- Domain
- authentication, cli
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100