AI SPACE

GitHub App repo management (PUBLIC + PRIVATE via user's App installation). All operations target the repository's default_branch only — non-default branches are not accessible. repo_connect: check status, get connect_url | repo_disconnect: remove DB token | repo_list: list repos | repo_files: browse repo (read-only) | repo_write_file: commit single file then auto-redeploy linked project | repo_deploy: deploy new project from repo (repo_name required; **force=true: 같은 ID 강제 재배포 — 컨테이너만 새로, base_uid/env/acl/domain/user_data/DB 모두 보존. 완전 삭제 원하면 웹콘솔 사용. force 사용 전 사용자 확인 필수.**) | repo_update: redeploy latest commit All action names are prefixed with `repo_` to avoid collision with the top-level deploy_project tool. **MANDATORY pre-flight (repo_update / repo_write_file 호출 전):** get_project_status 응답의 source 가 "github" 인지 확인. "internal" 이면 호출 금지 — update_project 또는 project_upload(update=true) 사용. 잘못 호출 시 서버가 SOURCE_MISMATCH 응답 (repo_write_file 은 commit 만 수행하고 자동 재배포 skip). **프로젝트 매칭 규칙 (오탐 방지):** repo_update/repo_write_file 의 자동 매칭은 system.projects.github_repo 컬럼 LIKE 매칭으로 동작. 리포명과 프로젝트명이 달라도 1:1 매핑이면 자동 OK. 단: • 한 리포가 여러 프로젝트에 deploy 된 경우 → AMBIGUOUS_PROJECT 응답. 반드시 project_name 명시. • 가장 안전한 호출 패턴: 먼저 list_my_projects 로 실제 project_id 확인 → project_name 으로 정확히 명시 호출. • repo_name 만 넘기면 자동 lookup 이지만 1:N 또는 0건 케이스에서 의도와 달라질 수 있음 (project_name 명시 권장). Always show the guide field from response to user.

external_repo

Manage project access control. set_ip: mode=deny→block IP, mode=allow→whitelist (blocks all others) | clear_ip | set_geo: block country by ISO code | clear_geo | get_acl

project_acl

Add/remove Pod-mode add-ons (redis|memcached). Remove deletes all data for that service.

project_option

Manage project env vars (get|set|delete). DB/Redis vars are server-auto-injected — do not set manually.

project_env

Update existing project with latest code. App container recreated; DB data/options preserved. Set rebuild=true to force full image rebuild. **MANDATORY pre-flight (둘 다 필수):** 1) get_project_status 응답의 source 가 "internal" 인지 확인. "github" 이면 호출 금지 — external_repo 의 repo_update / repo_write_file 사용. 2) 기존 runtime 과 새 코드 runtime 일치 확인. 불일치 시 호출 금지 — 웹콘솔 삭제 후 재배포 안내. source 가드: 잘못 호출 시 서버가 SOURCE_MISMATCH 응답.

update_project

JSON upload path. **Required when create_session was called with mode='json'** (sandboxed/no-shell environments). curl on a json-locked session returns 409 — and json on a curl-locked session also returns 409. Limits: 3MB/file, 10 files/request, 5MB total. Text files: send plain text (no encoding field). Binary files: pre-base64-encode and set encoding='base64' — otherwise the server rejects with 400 (binary detected). Batches exceeding these limits must use curl mode + create_archive instead. **Retry: 4xx → fail immediately, 5xx → 1–2 retries, timeout → 1 retry. Every retry from a new create_session (new batch_id).** Final failure response includes `fallback_options` (external_repo / deploy_project) — surface to user.

upload_json

Session-based file upload. **Step 0 — capability self-check (MANDATORY before create_session):** • If you have a Bash/shell tool available → mode='curl' (preferred: faster, no per-request size limits). • If you are sandboxed (browser/Canvas, no shell) → mode='json' (use upload_json after create_session). • Do NOT probe with `which curl` or any shell command. A sandboxed runtime cannot execute shell at all — the probe itself is the symptom. Decide from your own tool inventory. **Mode lock policy:** mode is locked at create_session time (NOT at first file upload). Once locked, the other path returns 409. To switch modes you MUST create a new session. **Retry policy (json mode):** 4xx → fail immediately (no retry). 5xx → retry 1–2 times. timeout → retry 1 time. Every retry MUST start from a NEW create_session (new batch_id) — never reuse a batch_id whose first attempt failed. **Final-failure fallback:** if json upload fails after retries, the response includes `fallback_options` listing alternatives (external_repo for GitHub App connect+deploy, deploy_project for public Git URL). Surface those options to the user instead of looping. **중요: 모든 시도 (신규 deploy / update / force / rebuild) 시 항상 새 create_session 부터 시작. 같은 batch_id 재사용 금지 — finalize 후 session+파일이 cleanup 되어 재사용 시 repo 유실 위험.** **update=true 호출 전 MANDATORY: get_project_status 응답의 source 가 "internal" 인지 확인. "github" 이면 호출 금지 — external_repo 의 repo_write_file 사용. 잘못 호출 시 서버가 SOURCE_MISMATCH 응답.** create_session: files+repo required, mode recommended → batch_id+upload_url (mode locked at this point) create_archive: for 10+ files, compressed (curl only) finalize: batch_id required; deploy=true→push+deploy, false→push only status: check progress Create files under aispace_files/{name}/ — never /tmp.

project_upload

Verify deployed site HTTP accessibility. Optionally checks content/title. retry_on_fail=true for auto-rebuild.

site_verify