Antigravity Auto Accept: 에이전트 작업을 위한 안전 승인 규칙

Auto accept는 Antigravity 작업을 빠르게 하지만 터미널 명령, 파일 삭제, 자격 증명, MCP 작업을 모두 승인한다는 뜻이 아닙니다. 자동화할 범위와 사람이 확인할 범위를 나눕니다.

Xuper TV APK Logo

Auto Accept 안전 가이드

Works with current v2.2.1-era builds Windows, macOS, Linux July 9, 2026
Download Latest Antigravity Check Approval Matrix

Default to review for destructive, network, credential, and broad file-system actions

Antigravity IDE workspace used for reviewing agent approvals
Antigravity IDE project view for reviewing auto accept agent changes
Use auto accept inside a controlled repository, then inspect the diff before trusting broader agent actions.

빠른 답변: 자동 승인은 파일 읽기, 알려진 파일의 작은 수정, 포맷, 신뢰된 테스트처럼 되돌리기 쉬운 작업에만 사용하세요. 삭제, 설치, 비밀 정보, git 기록, 배포, 외부 계정과 연결된 MCP 작업은 수동 승인으로 남겨야 합니다.

가이드 목차

Auto Accept의 실제 의미

Antigravity에서 auto accept는 반복 승인을 줄이는 편의 기능이지 모든 작업이 안전하다는 보장이 아닙니다. 에이전트는 파일 읽기, 코드 수정, 명령 실행, MCP 호출, 브라우저 작업을 제안할 수 있습니다. 일부는 일상적이지만 일부는 삭제나 외부 전송으로 이어질 수 있습니다.

이 사이트는 다운로드와 설치 사용자를 다루므로 권장 방식은 보수적입니다. 공식 출처, 현재 버전, 테스트 저장소를 먼저 확인한 뒤 자동 승인 범위를 넓히세요. 회사 장비에서는 내부 보안 정책이 우선입니다.

버전 확인에서는 이 사이트를 소프트웨어 다운로드 사이트로 처리했습니다. 로컬 콘텐츠는 v2.2.1과 공식 다운로드 페이지를 가리킵니다. 2026년 7월 9일 실행 환경에서 공식 download/changelog는 시간 초과되었으므로 새 버전, 파일 크기, 직접 링크를 만들지 않았습니다.

승인 매트릭스

Use this matrix before turning a repeated prompt into an automatic rule. The safest setting depends on the command, the workspace, and whether you can easily undo the change.

작업 유형 권장 수준 판단 기준
Read files, list folders, inspect git status Usually safe to auto accept Allow in the active workspace when no secrets or private customer data are exposed.
Edit one known source file Often safe after review pattern is clear Allow after the agent has shown the exact file path and you use version control.
Run tests, linters, formatters, type checks Good auto accept candidate Allow trusted project commands such as python build.py, npm test, or lint scripts that you already use.
Install packages or run downloaded scripts Ask first Review package name, source, lockfile impact, and whether the command can execute post-install scripts.
Delete files, move directories, rewrite git history Manual approval Require review because the blast radius can be larger than the agent summary.
Read environment variables, tokens, browser sessions, or cloud accounts Manual approval or blocked Do not auto accept actions that can expose credentials or send private data outside the workspace.

안전한 흐름 설정

Start with a small repository and one repeated workflow. Good examples are running a formatter after edits, executing a unit test command, or accepting a patch to a single file that you can review in git. Avoid creating a global rule on the first day you use Antigravity. The first few sessions are when you learn which commands the agent tends to request and which prompts are actually protecting you.

Keep the approval scope narrow. If the setting lets you choose between workspace-only actions and unrestricted shell access, prefer workspace-only. If it lets you remember a command, remember the exact command rather than every command from the same tool. A safe rule says “allow this test command in this repository”; a risky rule says “allow any shell command forever.”

Antigravity panel used while choosing safe approval behavior
Start by observing the agent panel, then allow only repeated low-risk actions.
  1. Step 1 - Update Antigravity and verify the About dialog before changing approval settings.
  2. Step 2 - Open a non-critical repository and let the agent complete a small task while approvals stay visible.
  3. Step 3 - Auto accept only the repeated low-risk actions you understand, then confirm the git diff after each run.
  4. Step 4 - Keep manual approval for destructive, network, credential, installer, and account-connected actions.

일상 작업 안전 모드

A productive Antigravity setup does not need to be fully manual. The middle ground is to let the agent move quickly inside a controlled lane. Reading files, applying a small patch, and running a known validation command can be automatic. Decisions that change dependencies, call external services, or remove data should pause for human review.

Use git as your recovery boundary. Before a larger auto-accepted session, start from a clean status, make a small commit, or at least know which files are expected to change. After the session, inspect the diff before you run or publish anything. Auto accept saves clicks; it does not replace code review.

Antigravity About dialog used before changing approval settings
Verify the installed version before debugging approval or automation behavior.
  • Good default - Allow read-only exploration and known validation commands.
  • Review checkpoint - Inspect the diff before dependency, deployment, database, or workflow changes.
  • Rollback plan - Keep changes small enough that one git revert or file restore can undo them.
  • Team rule - Document which commands are approved so teammates do not inherit hidden risky defaults.

사용하지 말아야 할 때

Disable auto accept when you are working in a repository with production credentials, private customer data, regulated records, payment flows, or deployment permissions. The cost of one wrong command is too high, and the agent may not know every internal boundary. Manual prompts are cheap compared with rotating secrets or restoring deleted data.

Also avoid auto accept while debugging a broken MCP server, a failing terminal environment, or a suspicious installer. If a command is failing, repeating it automatically can create confusing partial state. Fix the environment first, then re-enable only the commands that are now predictable.

Security note

Never auto accept a shell command copied from an unknown page, a curl-to-shell installer, a command that prints secrets, or a broad delete/move operation. If the command would make you nervous in a normal terminal, it should not be automatic inside an IDE agent.

문제 해결

If automatic approvals create errors or unexpected changes, narrow the scope instead of turning every prompt back on.

The agent keeps asking anyway

The action probably falls outside the remembered scope. Check whether the path, command arguments, shell, or MCP tool changed.

Auto accepted commands fail

Run the same command in a normal terminal. If PATH, npx, permissions, or PowerShell policy differ, fix the environment before allowing repeats.

A diff is larger than expected

Stop the session, review each file, and restore unrelated changes before continuing. Then replace broad approval with a narrower rule.

A rule feels too broad

Delete the remembered approval and recreate it only after you see the exact action pattern you want to allow.

FAQ - Antigravity Auto Accept

Is Antigravity auto accept safe?

It can be safe for narrow, reversible actions such as reading files, applying known edits, and running trusted checks. It is not safe as a blanket approval for deletes, installs, secrets, cloud actions, or unknown shell scripts.

Should I auto accept terminal commands?

Only for commands you already trust in that repository, such as test, lint, format, or build commands. Ask first for package installs, network calls, database changes, and deployment commands.

Can auto accept expose secrets?

Yes, if a tool can read environment variables, config files, browser sessions, or cloud accounts and then send data elsewhere. Keep those actions manual or blocked.

What is the best beginner setting?

Keep approvals visible for the first few sessions, then allow only read-only exploration and known validation commands. Expand slowly after reviewing several clean diffs.

Does updating Antigravity change approval rules?

It can change features or defaults, so verify your settings after an update and test in a non-critical workspace before using automatic approvals on important code.