What Happened
GitHub Copilot added server-to-server authentication for GitHub Apps in public preview. Services built with the Copilot SDK can now make requests on an organization’s behalf using a short-lived installation token, without relying on a signed-in developer’s credentials. The app needs the read-only Copilot Requests organization permission. Usage is billed to the organization and remains subject to its model policies, budgets, and spending controls. [1]
Copilot’s assisted permissions are now generally available in its CLI, app, and Visual Studio Code. An LLM automatically allows requests it judges clearly safe to run a command, access a file-system path, or open a URL; other requests require approval. Enterprise administrators can restrict available permission modes and set a session default. [3]
JetBrains IDEs 2026.3 EAP builds enable a new libghostty-based terminal by default, replacing JediTerm. It improves keyboard handling and control-sequence rendering for terminal-based coding tools. Users can switch back through a registry setting if they encounter problems. [2]
Why It Matters to Businesses
Server-to-server authentication makes unattended coding services easier to operate without storing a developer’s personal credentials. Assisted permissions may reduce approval interruptions, but they also move some access decisions from a person to a model. JetBrains’ terminal change addresses a different source of friction: prompts, shortcuts, and output that behave incorrectly inside an IDE. [1][2][3]
These notes establish changes for GitHub Copilot and JetBrains; they do not establish new releases for Cursor, Windsurf, Replit, Sourcegraph, or Continue.dev.
Kimbodo Engineering Perspective
Separate identity, authorization, and convenience. An installation token identifies the service making a Copilot request; it does not justify broad access to repositories, files, or execution environments. Likewise, assisted permissions are useful for routine work but should not be the sole control for consequential commands. The terminal upgrade improves interaction with coding agents, not their security boundaries. [1][2][3]
How We Would Implement It
- Install a dedicated GitHub App with the Copilot Requests permission, issue short-lived installation tokens server-side, and keep tokens out of client applications and logs. [1]
- Set organization model policies and spending limits, then attribute and monitor app consumption using app_client_id in AI usage reports. [1]
- Pilot assisted permissions with a defined group. Keep manual approval for sensitive workflows, and test representative commands, paths, and URLs before changing enterprise defaults. [3]
- Test terminal-based agents in JetBrains 2026.3 against keyboard shortcuts, multiline prompts, and output rendering; retain the JediTerm fallback during rollout. [2]
Risks, Costs and Security
Organization-billed automation can generate costs without a developer initiating each request, so budgets and usage monitoring matter. App installations should be reviewed and revoked by suspension or uninstallation when no longer needed. Assisted permissions can misclassify a request; restrict what the agent can reach or execute even when automatic approval is enabled. Finally, JetBrains’ libghostty rollout is still described in EAP builds, so validate compatibility before treating it as a fleet-wide dependency. [1][2][3]
Where Kimbodo Comes In
Kimbodo builds and operates this in production for businesses — see our AI Application Development practice, or Estimate My AI Application.
