Back to home

IACoder

Engine

An embeddable agent engine

The core our products share. It owns the hard part — the agent loop, tool dispatch, context management, provider adaptation, quality gates — and never holds a system resource it can borrow from its host.

Built for embedding; not shipped on its own.

Surface · The engine under the products

engine core
IACoder
  • Agent loop
  • Tool dispatch
  • Context management
  • Provider adaptation
  • Quality gates
Lent by the host, never owned
FilesystemProcessesNetworkTabs
Why a separate engine

The engine owns the hard part; the host owns its own world.

01

Never holds host resources

Filesystem, processes, network, browser tabs — anything the host can lend, the engine does not own; it is injected through a seam. That is what lets one engine live in a terminal, a browser extension and a desktop app at once.

02

Provider and platform neutral

No hand-maintained model knowledge base is baked in. Providers arrive through one interface and keys are held by the host, so switching providers does not touch the engine.

03

Bounded, observable, grounded

Every capability carries a budget and an off switch; every tool call, permission decision and context compaction is a structured event, so the session narrative can be rebuilt faithfully; completion is tested against ground truth rather than self-report.

INFINIACT