How to Configure JetBrains AI SSH Permissions

Published
Length
3 min read

Luis Felipe Dias

All posts

You set up jetbrains ai ssh permissions by linking your IDE to local SSH keys. The AI assistant then inherits the exact host rights of your local shell user. Engineering teams often start by giving developers broad user keys for remote servers. This fast setup helps people ship code, but it creates big risks later. When an AI assistant runs terminal commands, it uses those same wide user rights. A bad prompt or mistake can change live server files or expose data. How jetbrains ai ssh permissio

AI Agent Permissions + SSH Access Management: the complete guide

Architecture patterns, implementation strategies, and security best practices. Delivered to your inbox.

Free white paper. No spam. Unsubscribe anytime.

You set up jetbrains ai ssh permissions by linking your IDE to local SSH keys. The AI assistant then inherits the exact host rights of your local shell user. Engineering teams often start by giving developers broad user keys for remote servers. This fast setup helps people ship code, but it creates big risks later. When an AI assistant runs terminal commands, it uses those same wide user rights. A bad prompt or mistake can change live server files or expose data.

How jetbrains ai ssh permissions work in practice

JetBrains IDEs use your local OpenSSH client to reach remote hosts and containers. The AI features inside the IDE do not hold their own server credentials. Instead, the IDE runs tasks through the active SSH session on your machine. If your local user can log in to a host, the assistant can too.

Many teams move away from static keys and use OpenSSH certificates instead. In OpenSSH, a certificate authority key signs a user public key to make a certificate. This certificate holds the public key, identity info, principal names, and specific options. OpenSSH certificates use a much simpler format than standard X.509 certificates. Certificate support for users and hosts arrived in OpenSSH 5.4.

When an admin signs a user certificate, they set a key identity. They also list one or more principal names, which match user or host names. The signing step creates a user certificate by default, unless marked for a host. Admins can also attach certificate options and set a time window for validity. If the admin sets no time window, the certificate stays valid forever.

What native host controls solve and what they miss

OpenSSH certificates and local agent rules solve the first part of remote security. They verify who can log in to a server and which principals apply. Teams can skip copying public keys to every single remote machine by hand. They can also set expiration times so old certificates stop working on schedule.

Still, host login checks stop working the moment the SSH session starts. An OpenSSH certificate decides who gets into the box, not what happens next. Once the IDE opens a shell, every command runs with full user privileges. Native SSH rules cannot tell a human command apart from an AI command.

AI Agent Permissions + SSH Access Management: architecture patterns and best practices

Continue reading? Get the full guide.

Free. No spam. Unsubscribe anytime.

This gap matters when developers debug live systems with an AI assistant. A single shell command can read customer logs that hold sensitive text. Those logs often include emails, phone numbers, card numbers, or national IDs. Without command-level checks, you cannot block destructive shell actions in flight. You also cannot mask sensitive fields like emails or card numbers before output returns.

Why teams separate login checks from command checks

Relying only on Linux user groups forces a hard choice on platform teams. If you give developers root or sudo rights, AI tools get them too. If you take away shell rights, engineers cannot fix broken services fast. Static server roles are too blunt for modern IDE workflows.

To fix this, teams split host login from in-flight command control. First, you keep using short-lived OpenSSH certificates for basic user identity. Second, you inspect every command and output stream inside the active session. This lets engineers run safe read commands while dangerous changes wait for approval. It also rewrites matched fields like phone numbers and national IDs in results.

Add command and file guardrails to SSH access

Host firewalls and certificate principals control who opens an SSH session. Yet an allowed user or agent can still run a bad one-shot command or pull sensitive files over sftp. In practice, hoop.dev provides an open-source SSH server with guardrails on the host that uses OpenSSH certificates.

Using hoop.dev SSH controls, guardrails check one-shot commands, env variable names, and sftp or scp paths before they run. Port forwards default to deny unless the target is listed. Because interactive shells have no statement boundary and carry no guardrails, teams can turn them off so every command is checked and logged. Check out the MIT-licensed project on GitHub.

Frequently asked questions

Does JetBrains AI use a separate SSH key from my IDE?

No, the AI assistant uses the same SSH setup as your main IDE. Any terminal action it takes runs under your active local user session.

How do OpenSSH certificates improve on static SSH keys?

A certificate authority signs a public key with an identity, principals, and options. This lets teams set validity windows instead of leaving static keys on hosts.

Can OpenSSH certificates hide sensitive data in terminal output?

No, OpenSSH only handles the login step and basic channel restrictions. It cannot rewrite emails, card numbers, or phone numbers inside command output.

Save the open-source gateway.

hoop is MIT-licensed infrastructure for controlling how AI agents reach production data. Star hoophq/hoop so you can inspect it, deploy it, or share it when your team starts governing agent access.