Project-scoped sessions
Resume the right AI session.
Find recent local Codex tasks for the selected project. Open a task in ChatGPT Work or Codex, or start a new one at that project’s root.
Instance Control
Instance Control for Guidewire development
Your Guidewire work.In parallel.
Create separate Guidewire project instances for parallel work. Bring each project’s AI sessions, runtime, and tools together in one native macOS app.
Research one issue. Implement another. Keep their working environments separate.
- AI orchestration
- Native Guidewire control
- Telegram remote operations
- Webex remote operations
- Trusted devices
One project context
Select the project. Find what you need.
Open its IDE, check the server, or return to an AI session. IDE and runtime actions follow the selected Application; AI sessions follow the project.
Why Instance Control
Different tasks. Separate working states.
Investigate a bug in one instance. Try a different approach in another. Research, implementation, and experiments can each have their own working environment.
- Before
- Unrelated tasks and AI sessions compete for the same project files, ports, database state, and runtime.
- With Instance Control
- Create an isolated instance with its own project root and runtime state, plus separate ports and local databases where supported. Its AI sessions and guidance stay with that environment.
AI orchestration
Switch projects. Find the right AI session.
Return to local Codex tasks for the project you selected. Project-specific AGENTS.md guidance keeps Codex connected to that environment.
Project AI guidance
Keep project instructions in reach.
With an IDE and Application selected, Instance Control automatically maintains its own guidance blocks in AGENTS.md. Individual rules can be switched off; your other instructions are preserved.
Remote operations & notifications
Away from the Mac. Still in control.
Check your project and request supported server actions from Telegram or an authenticated Webex conversation. Receive updates as the server starts, becomes ready, or needs attention.
Telegram remote operations
See status. Start, stop, or restart when available.
Review the current project state from your phone and request an action when the selected runtime allows it.
Before execution, the Mac revalidates the device, project, selected Application, and runtime state. Telegram exposes no shell or generic command channel.
Webex remote operations & notifications
Check status, request actions, and receive lifecycle events.
In a direct bot conversation, choose a device, refresh status, and request available Start, Stop, or Restart actions. Receive selected lifecycle notifications in Webex, using the email associated with your Instance Control account.
Webex exposes no shell or generic command channel. Stop and Restart require confirmation, and the selected Mac revalidates the exact project, Application, and current action before execution.
Native command center
Open the IDE. Follow the server.
Open the IDE, launch the selected Application, and follow the server through startup. Logs, resource use, and maintenance tools stay with the project you are working on.
Know what you’re about to run.
See the project, selected Application, Java runtime, ports, and server state before you act.
- Project
- Project root
- Application
- Selected Application
- Runtime
- Resolved JDK
Control the local server lifecycle.
Start, Stop, or Restart the selected server. Open or focus the matching IDE, launch the current Application, and return to its console or logs.
Start
Stop
Restart
Open IDE
Open server page
Know when the server is ready.
Follow build and startup progress, see readiness or failures, and inspect CPU, memory, and searchable logs in one place.
Readiness
Build lifecycle
CPU / RAM
Local console
Keep specialist tools nearby.
Keep supported database, APD token sync, and log tools close to the selected project. Add projects, copy their paths, create separate instances, or remove projects with confirmation.
Cleanup SQL
Restore
APD token sync
Copy Path / Clone
Development performance
Make a change. Get back to testing.
Build Accelerator can compile supported changes without a routine full Gradle build. Performance profiles put server, IDE, memory, and indexing choices within reach.
Shorten the path from edit to feedback.
For supported changes, Build Accelerator uses the Guidewire compiler through an IDE-like build route. You can build and test the change without routinely rebuilding the whole project.
- Input
- Changed code
- Accelerated route
- JPS / Gosu
- Alternative route
- Supervised Gradle
- Scope
- Selected project
If accelerated compilation cannot be prepared safely, Instance Control can use supervised Gradle.
Tune the local environment for the task.
Keep server, IDE, resource, and indexing choices explicit and user-controlled. Supported PolicyCenter projects also expose Fast Server Mode and Minimal UI Theme.
- PolicyCenter
- Fast Server Mode · Minimal UI Theme
- IDE
- Lightweight IDE · Power Save Mode
- Resources
- Adaptive Memory
- Indexing
- Spotlight Indexing
Exclude workspace projects from Spotlight, or disable indexing on this Mac’s Data volume with administrator approval.
Trusted devices
One account. Known devices. Transfers you approve.
See your registered devices, the limited project state they share, and when it was last updated. Moving a project between devices is a separate action that you explicitly approve.
See the project state that matters.
Check each device’s projects, selected Applications, basic runtime state, and the age of its latest update.
Rename the device, not its identity.
Rename a device without registering it again. Unlink it when it should no longer be connected to your account.
Windows adds visibility. macOS remains the command center.
Windows Device Bridge discovers local Guidewire projects, publishes a constrained device snapshot, and can serve as an approved source for encrypted project transfer. Server lifecycle and IDE control remain on macOS.
Encrypted project transfer
Approve the device. Transfer one project at a time.
- 01Choose
Select one source project.
- 02Compare
Read the pairing code on the other device and enter it to verify trust.
- 03Approve
Explicitly approve the paired device.
- 04Transfer
Encrypt locally, verify, decrypt, and apply on the target.
The relay receives ciphertext and limited transfer metadata, not a readable project archive. Windows Device Bridge can act only as a transfer source.
Security architecture
Remote access without turning the workstation into a remote shell.
Cross-device visibility uses a deliberately small snapshot. Signed device requests, Telegram and Webex actions, and project transfers are protected by different combinations of device proof, explicit approval, and local authorization.
Data boundary
Share only what coordination needs. Keep workstation internals local.
Shared for cross-device visibility
- Device label, stable identity, and platform details
- Safe project title and product
- Selected Application and supported port metadata
- Coarse runtime state and available actions
- Project size and content fingerprints where supported
- Snapshot timestamp and freshness
- Discovery status and device capabilities
Not included in device or remote-control snapshots
- Raw project paths, PIDs, and command lines
- Database connection details and secrets
- Tokens and private keys
- AI conversation bodies
- AI sessions
- Instance Control uses only local session metadata and lifecycle markers to associate a session with a project. Conversation bodies are not displayed, persisted, or uploaded by Instance Control.
- Configured integrations
- Telegram and Webex receive only the limited request, result, and notification data needed for their configured features. Neither integration exposes a shell or generic command channel.
Every supported device request is bound to its device identity.
- Proof
- Ed25519 proof binds the request method, path and query, body digest, timestamp, and one-time nonce.
- Private keys
- Device private keys are stored in macOS Keychain or Windows DPAPI-protected local storage.
The Mac authorizes every remote action.
- Recheck
- Telegram and Webex expose only supported state-aware lifecycle actions, not arbitrary commands. Before execution, the Mac revalidates the registered device, project, selected Application, runtime state, credentials, and requested action.
- Journal
- One-time nonces and a durable local journal block replay and duplicate execution. Repeated delivery returns the recorded result instead of running the action again; conflicting reuse is rejected.
- Result
- If the required checks cannot be completed, the request is rejected.
Trust stays explicit from account to update.
- Account
- Passkeys, password and email changes, session review and revocation, sign out everywhere, and security events keep account access visible and controllable.
- Transfer
- Paired-device approval, local encryption, and target-side verification protect project transfer.
- Stable releases
- Developer ID signing, notarization, hardened runtime, and Sparkle Ed25519 verification protect stable macOS distribution. Ad-hoc builds do not use that update path.
Download
The full control plane on macOS. The bridge on Windows.
Run the full Instance Control command center on macOS. Install Windows Device Bridge only on trusted Windows PCs that should publish limited Guidewire state or act as approved sources for encrypted project transfer.
Full application
Instance Control for macOS
The native command center for Guidewire projects, local Codex tasks, runtime control, remote operations, notifications, and trusted devices.
Requires an Instance Control account, verified email, and an internet connection for account validation.
Developer ID signed and notarized.
Companion preview
Windows Device Bridge
A limited companion that discovers local Guidewire projects, publishes a constrained device and runtime snapshot, and can act as an approved source for encrypted project transfer.
No server lifecycle or IDE control.
Unsigned portable preview ZIP; no installer is provided.
Instance Control