Get AutoComp ready to write.

Set up your connection

1. After installing AutoComp, enable it in Safari > Settings > Extensions. Allow access to docs.google.com.
2. Click AutoComp in the Safari toolbar to open its options.
3. Enter your Base URL, Model, and API key. Use the HTTPS API base, such as https://your-provider.example/v1, without appending /chat/completions.
4. Choose Save and test connection and allow access to your endpoint's domain when Safari asks.
5. Reload an editable Google Docs document and start typing. Try a document containing only non-sensitive test text first.

You supply the endpoint and any required provider account or credit. The extension does not import settings from Chrome.

Use a suggestion

• Tab accepts the next word.
• Shift + Tab or the backtick key accepts the full suggestion.
• Esc dismisses the suggestion.

No suggestions appear

Confirm that the document is editable and AutoComp is enabled in the Safari profile you are using. Check permissions for Google Docs and your endpoint, then reload the document. Disable any duplicate AutoComp installation and test the connection again.

A successful connection test checks the model-list endpoint. Your server must also support chat completions. Changes to Google Docs can affect how suggestions appear or are inserted.

The connection test fails

Check the HTTPS base URL, valid TLS certificate, model identifier, API key, and Safari permission for the endpoint. AutoComp uses /models to test the connection and /chat/completions for suggestions. Plain HTTP endpoints are not supported.

Settings are missing

Check the Safari profile and installation you are using. Different installations do not share settings. Removing extension data or changing the installation identity can require setup again. Settings are not synced through iCloud.