← All concepts

agent-integrated software

When you put an AI agent inside an existing program, you get a coordination problem: the user can change goals or data mid-task, so the agent's isolated actions may no longer match intent. Some propose a pattern where the app core and agent are combined with explicit contracts for authority and task bindings. Others let the agent fill unfinished "code holes" at runtime, or give it structured observations and semantic actions instead of fragile screenshots and clicks.

Across these views, the common thread is that agents cannot just be bolted onto software. They need a disciplined interface, whether that means formal interaction agreements, a structured action layer, or a runtime harness that lets the agent synthesize missing pieces. The goal is to make human, agent, and application cooperate as one evolving system.

Papers
3
Released code
0
First seen
Aug 2026
Latest
Sept 2026

0 papers in the last two months, against 3 in the two before.

Start here

Three papers to read first, in the order they came out
  1. 1Structured software interfaces outperform screenshot-and-click control for AI agents

    ASIL replaces screenshot-and-click with structured JSON observations and semantic actions, achieving over 80% success on 380 tasks with fewer than five actions each.

    Aug 2026
  2. 2Embedded AI agents can adapt software during live use

    Software can dynamically construct missing implementations and adapt to user behavior via an embedded AI agent.

    Sept 2026
  3. 3Embedded software agents need interaction contracts and continuous assurance

    Dependable agent integration requires explicit contracts linking task-level interaction to application behavior and continuous assurance.

    Sept 2026

The papers

Most central to this idea first, not most recent.

Concepts are extracted from each paper and reused across the corpus, so this page grows on its own as the desk reads.