Skip to content

Update 1Password fill outcomes for autosubmitFailed and fill_unknown #692

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
rgarcia merged 2 commits into from
Oct 9, 2026
+6 −4
Merged

Update 1Password fill outcomes for autosubmitFailed and fill_unknown #692

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
3c7e8e4
Update 1Password fill outcomes: autosubmitFailed is fill_unknown, ins…
rgarcia Oct 9, 2026
89f3f1b
Merge remote-tracking branch 'origin/main' into hypeship/1pw-fill-unk…
rgarcia Oct 9, 2026
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
10 changes: 6 additions & 4 deletions vaults/1password.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -617,8 +617,9 @@ when more than one approved entry has that origin, pass its `entry_id` from
`state.access_request.entries`. the extension selects the fields, fills them,
and submits the form; you can't supply selectors or values.
`fill_submitted` means the extension reported that it submitted the form. if the extension fills
the form but can't submit it, it clears what it filled and KERNEL returns
`fill_failed`. a submitted form doesn't mean the login succeeded.
and submits the form but can't confirm the fill finished, it clears what it filled and KERNEL
returns `fill_unknown` with `error_code: "autosubmitFailed"`. the page might already have moved
on, for example to the next sign-in step. a submitted form doesn't mean the login succeeded.

for a sign-in that spans several pages, such as a username page, a password
page, and a one-time password page, invoke `1pw_fill` again on each page. each
Expand Down Expand Up @@ -707,11 +708,12 @@ defaults to 30,000.
| outcome | meaning | next step |
| --- | --- | --- |
| `200` `fill_submitted` | the extension filled and submitted the form | check the page; website authentication isn't verified |
| `200` `fill_failed` | the extension reported `fillFailed`, `autosubmitFailed`, `noExistingCredentials`, or `authenticationFailed` | inspect the page before trying again |
| `200` `fill_unknown` | the fill was dispatched but the outcome is inconclusive; it might have submitted | check the page; don't retry in the same browser |
| `200` `fill_failed` | the extension reported `fillFailed`, `noExistingCredentials`, or `authenticationFailed` | inspect the page before trying again |
| `200` `fill_unknown` | the form might have been filled or submitted, but the outcome is inconclusive. `error_code` is `autosubmitFailed` when the extension submitted but couldn't confirm the fill finished | inspect the page to see the result of the fill |
| `400` `page_not_found` or `ambiguous_page` | `page_url` matched no page or more than one | fix the url or close duplicate tabs |
| `400` `invalid_request` | the fill request was rejected as invalid | check `browser_id`, `page_url`, and `timeout_ms` before trying again |
| `403` `destination_denied` | the page is outside every approved login origin | navigate to a requested website |
| `409` `agentic_mode_unavailable` | the 1Password extension couldn't take control of the page; nothing was filled | check the page in the live view, then fill again |
| `409` | the item isn't `ready`, its approval is unusable, `entry_id` is missing or doesn't match an approved entry for the page, or a stored access token has expired | retrieve the item and follow `available_operations` |

### Fall back to KERNEL-hosted collection
Expand Down
Loading