Repository navigation
v1.6.2
New
- Connect to the vault from
/openaion OpenCode 2 (#233)./openai→ Vault → Connect now works on OpenCode 2, as on OpenCode 1. It requests an enrollment for this host and shows theckcommands you run to approve it. It then waits in the background while the menu stays usable, and the result appears in the session that asked. Because it runs inside the host, other OpenCode and Pi processes can keep running. Disconnect (after you confirm) and turning a vault account on or off for this host also work on OpenCode 2. Disconnect forgets this host's enrollment token; revoking the enrollment in the vault is a separateck auth enroll revoke. Setup still needs every OpenCode and Pi process stopped, because it also changes host configuration.
Fixed
- On OpenCode 2,
/openaino longer does nothing when run from the home screen (#232). OpenCode 2 creates a new session to run the command, and the plugin used to give up at once because its terminal UI hadn't seen that session yet. It now waits up to two seconds for it. When no terminal UI connects (for example withopencode runor an HTTP client), it logs why instead of returning silently, and it opens no menu and adds nothing to the conversation. setup --claustrumnow prints the vault grant command for the name the vault actually approved for this host, not a fixed name. When the approved name isn't recorded, it says so and prints the name it proposed (#233).- The OpenCode 2 vault login now points you at
/openai→ Vault → Connect when this host isn't connected yet.
No upgrade steps are needed.