Skip to main content

Opening Quibble

  1. Click the extension button on an ordinary web page.
  2. If the button works but the shortcut does not, check Quibble’s shortcut at chrome://extensions/shortcuts for a conflict or a changed binding.
Chrome restricts extensions on browser-internal pages and some other protected pages.
  1. Check that you are signed in to the expected workspace.
  2. Check that the project’s URL patterns include this page’s protocol, host, and port. See project sites.

Comments and pins

  1. Restore your network connection.
  2. Check the extension’s connection in its Options page.
  3. Sign in with the account that saved the comment.
  4. Check that the intended project includes the page URL.
  5. Follow any delivery or retry message shown on the comment.
The comment has not yet been shared with your workspace.
Keep the extension installed and its local data intact while recovering an unsent comment. Clearing extension data or removing the extension can remove the only copy of feedback that has not reached the server.
  1. Return to the page where the quibble was left.
  2. Open Comments to look for resolved feedback or comments whose element is no longer present.
  3. Look in the web app, where shared quibbles are also available.
  1. Unless your project attaches one by default, choose Add screenshot before saving.
  2. If an attached screenshot reports that it is unavailable, retry when your connection recovers.
A quibble can be saved without a screenshot. That is different from an attached screenshot that cannot be read.

Issues and agents

  1. Confirm that you chose Create issue and submitted the form.
  2. Read the error on the quibble.
  3. Ask a workspace administrator to reconnect the tracker or restore access to the selected destination, if needed.
  4. Retry the existing export when offered.
Saving a quibble alone does not create an issue. Your saved comment remains available.
  1. Check that the comment has been shared.
  2. Check that the agent is authorized with the correct Quibble account.
  3. Check that the account belongs to the comment’s workspace.
  4. Reconnect through Settings → MCP server if needed.