iop/apps/edge
toki 71c66aeaab fix(openai): caller workspace 경로 차단을 제거한다
Plan과 Review의 정확한 접근만 상태로 기록하고 일반 작업 경로는 모델과 caller 도구에 그대로 맡긴다.
2026-08-15 08:10:53 +09:00
..
cmd/edge
internal fix(openai): caller workspace 경로 차단을 제거한다 2026-08-15 08:10:53 +09:00
Dockerfile
README.md

IOP Edge

IOP Edge owns Node registration, dispatch readiness, provider-pool routing, queue admission, leases, reconnect fencing, external inference surfaces, and Control Plane operations.

Provider boundary

  • Public model ids resolve to provider adapter/target routes.
  • Normalized inference uses ordered run events; OpenAI-compatible passthrough uses provider tunnel frames.
  • session_id is correlation only and never resumes local execution state.
  • Cancellation targets an active run id.
  • Edge operations are health.check, node.status, and provider.command.
  • Provider commands are limited to capabilities, transport status, and the Ollama API tunnel.
  • Caller metadata remains an ordinary bounded string map.
  • Edge and Node use a shared tunnel-tolerant liveness profile: a 30-second heartbeat interval and a 45-second response wait. Long provider prefill or streamed-response backpressure does not prematurely fence a healthy connection; a real timeout still closes only the current generation and triggers Node reconnect.

Edge and Node preserve standard OpenAI/Anthropic-compatible inference, streaming, tools, usage, provider lifecycle, capacity, queues, and reconnect behavior. They do not own interactive host programs, persistent conversations, terminal emulation, arbitrary host commands, or local filesystem execution context.

Development

go test -count=1 ./apps/edge/...
go test -race -count=1 ./apps/edge/internal/service ./apps/edge/internal/openai
make test-e2e

Canonical contracts:

  • agent-contract/outer/openai-compatible-api.md
  • agent-contract/outer/anthropic-compatible-api.md
  • agent-contract/inner/edge-node-runtime-wire.md
  • agent-contract/inner/control-plane-edge-wire.md