Bug Report / DX Feedback
Description
When calling any memwal_* tool without a valid authenticated session, the error returned is:
``nMemWal server error (401):
`
Expected Behavior
The error should include a clear, actionable message, for example:
``nMemWal server error (401): Not authenticated. Run memwal_login to connect your Sui wallet.
`
Why It Matters
Developers integrating MemWal for the first time will inevitably hit this before running memwal_login. A blank error message provides no signal about what to do next and forces them to search documentation or ask for help.
Suggested Fix
Return a descriptive message on 401 responses that points the developer to memwal_login.
Reported during Walrus Session 7 - Prompt Evolution
Bug Report / DX Feedback
Description
When calling any
memwal_*tool without a valid authenticated session, the error returned is:``nMemWal server error (401):
`
Expected Behavior
The error should include a clear, actionable message, for example:
``nMemWal server error (401): Not authenticated. Run memwal_login to connect your Sui wallet.
`
Why It Matters
Developers integrating MemWal for the first time will inevitably hit this before running
memwal_login. A blank error message provides no signal about what to do next and forces them to search documentation or ask for help.Suggested Fix
Return a descriptive message on 401 responses that points the developer to
memwal_login.Reported during Walrus Session 7 - Prompt Evolution