Every verified Soval account can use its own context through the supported OAuth chat connection. Connect Soval, sign in with the account that owns the records, and review the requested permissions. Website login alone does not connect chat. Older owner-only dispatch connections remain restricted; use the supported sign-in connection for individual accounts.
Select Soval
Add the Soval connection to the chat. Ask whether account bootstrap, context selection, and persona capabilities are available.
Identify a saved work thread
Ask Soval to find it by name. Choose the correct result if names overlap. If needed, provide the work link or exact record ID.
Load context explicitly
Ask Soval to load your account context and report the selected profile, governance preferences, starting work, and persona. Account bootstrap can work without a saved work session. To inspect a particular thread, ask for that work’s context separately; that request requires the thread. Name additional records explicitly.
Request the next action
After checking the loaded material, ask for the result you need. A saved Soval draft is a separate action from reading context or receiving ordinary chat text.
“Load my Soval account context and report missing selections. Find my saved team-meeting work and load its context. Treat historical approvals as evidence only.”
Missing actions versus missing permission
If an action is absent from the connection’s Actions list, its discovery is incomplete. Reconnecting once may not update that list. Inspect the plugin details and report the missing action names, the server address without credentials, and any available update control. Do not repeat reconnect indefinitely or assume the server is missing code.
After a connection update, open a new chat with Soval selected. Ask it to call bootstrap_context and confirm set_context_preferences is exposed without changing preferences. A successful read verifies bootstrap; exposure alone does not verify the writer. Existing chats may still show the older list.
When an ordinary reconnect keeps an outdated grant, open Preferences, choose Reset connected chat, confirm revocation, and reconnect with the same account. Reset revokes all Soval chat grants for that account but preserves its identity and private work.
Work actions in chat
Ask for get_work to inspect a saved thread and its current required declarations. With explicit work-write consent, create_work, continue_work and change_work use the same save and revision checks as Workroom. compile_book requires a configured trusted compiler service; coordinate_work executes only an already prepared, owner-bound command. Tool exposure does not prove the service is configured. Existing grants do not automatically gain work-write permission. Reuse the same operation reference and exact content after an uncertain save; read current work before any changed action.
If permission is missing
In ChatGPT’s Soval connection settings, refresh the tools if that control is offered. If an action says Reconnect needed, reconnect and review the requested context and persona permissions. Start a new chat with Soval selected, then check availability again.
After reconnect, check for bootstrap_context, set_context_preferences, and the persona tools. If only search, fetch, and capture remain, individual records may still be retrievable. Do not assume the missing capabilities are connected. If no permission screen appears, report that instead of repeating reconnect indefinitely.
The same account choices apply on web and in connected chat. Reading extra records does not save them as preferences. Saving new choices requires context-write permission and an explicit action. Soval cannot force automatic startup in every external chat.