Skip to content

AgentRun v0.1.0-beta.40

Pre-release
Pre-release

Choose a tag to compare

@claudio-michel claudio-michel released this 16 Nov 11:30
· 290 commits to main since this release
bb7fb3e

AgentRun 0.1.0-beta.40

AgentRun is an open-source platform that supercharges your agents. It adds self-improvement, durable execution and a
control plane on top of your favorite agent harness. Your agents become smarter, more fault tolerant and use fewer
tokens with every run. This release is about templates that set themselves up, and runners that hold up at scale. A
template package's Composio trigger names the package's own Composio need and is made on the server that need resolves
to, so a package carries its Composio events again, and a template whose setup is only parameters is applied from its own
screen with Apply. On OpenRouter, a model that must reason is never sent reasoning off (ERNIE 5.5 Flash Preview, free, which
OpenRouter refused on pi for it), and a pi run's effort reaches a Chat Completions model such as gpt-6.1-sol. On Postgres, a runner renews
its claims and claims a batch of runs in a few statements whatever their count, and a store call waits for a busy pool's
connection up to a write's deadline, so a runner of 300 runs on a database a few milliseconds away no longer loses every
claim at once. The inbox from beta.39 gets its follow-up: email_send asks a person past five sends
in a run and before it writes outside the email's thread, and an email trigger starts watching at its first check. A
npx @parcha/agentrun start that fails now always says why: the step, the exit code or signal, the server's last lines
and a start log.
The store does not change: change only the image, and going back to beta.39 is changing it back. The launcher is
@parcha/agentrun 0.4.8, the Python client parcha-agentrun is 0.3.8, and the server image is
ghcr.io/parcha-ai/agentrun-server:v0.1.0-beta.40 (linux/amd64 and linux/arm64).

No fresh store: beta.40 opens the data beta.39 left, and beta.39 opens what beta.40 leaves. The SQLite schema
stays at version 11 and Postgres at version 14: this release adds no migration and no column. Keep the same data folder
and the same start command. On the Docker image that is --data /data/b37 --listen 0.0.0.0 --port 7340 --drain-timeout 6s as before, and on Render the Docker Command you set for beta.37 stays. Change only the image to
ghcr.io/parcha-ai/agentrun-server:v0.1.0-beta.40. The console keeps its login, and your agents, MCP servers, keys,
sign-ins, email account and triggers are all still there. Upgrade the server first, then the runners, as before.

  • Going back. Set the image back to v0.1.0-beta.39; the command stays and there is nothing to restore. A copy of
    the data folder (or pg_dump --schema=agentrun <url> on Postgres) before you upgrade is still good practice.
  • Nothing else under the store changed shape.

Highlights

  • Composio triggers in template packages. A package's composio trigger names its own Composio need by its toolkit
    (source.server: github for the need {source: composio, toolkit: github, required: true}), and Apply makes the
    trigger on the saved Composio server that need resolves to: the one candidate, or the owner's pick. Its config may
    hold ${parameters.<name>}, so one package watches the owner's repository. A trigger this server can't set up yet (no
    public URL, no connected account) is skipped with a not_set_up_here warning and the agent stands (#2974).
  • Apply for a template that needs only parameters. A template with no MCP tool and no key to set up is applied from
    its own screen: Apply is the main action there and Configure on its card, and "Set it up with an agent" is the second
    way. One that reads mail waits for a mailbox saved under Settings → Email and links there (#2981).
  • OpenRouter reasoning. A model OpenRouter marks as one that must reason is registered so pi never sends it
    reasoning off: ERNIE 5.5 Flash Preview (free) answered every request with "Reasoning is mandatory for this endpoint and
    cannot be disabled." and is now sent no reasoning off, so it reasons at OpenRouter's default effort for it. Ling 3.2 Flash (free), which may stop
    reasoning, still runs with thinking off (#2984). A pi run's effort now reaches an OpenRouter model that speaks Chat
    Completions, openrouter/openai/gpt-6.1-sol (pi's default on an OpenRouter key) included, as reasoning: { effort }
    mapped by the model's catalog entry (#2985).
  • Postgres runners at scale. A runner's renew of the claims it holds, and its claim of a batch of runs, are a few
    statements whatever the count: a runner holding 300 runs no longer renews in about 600 round trips with every row held,
    which on a database a few milliseconds away outlasted the claim deadline and lost every claim at once (#2971). A store
    call that finds every pool connection in use waits up to a write's deadline (10 s, poolWaitMs) instead of the 4 s
    connect timeout, so a busy runner's runs no longer fail for good with "no connection to the store's Postgres" while
    the database answers; a database that does not answer still fails fast, in words that say so (#2976).
  • Email follow-up. email_send asks a person in two more cases, even when it is set to allow: after a run has sent
    5 emails, each further send asks ("this run has sent N emails"), which stops two auto-responders from answering each
    other without end; and on a run an email started, a send to anyone outside that email's thread asks, naming them. The
    approval says why ("Asks because …"). An email trigger starts watching at its first check, which runs at once when the
    trigger is made, turned on again or edited, and a create or turn-on answers once that check is done (10 seconds at
    most), with last_check in its answer (#2977).
  • A launcher start that says why. When npx @parcha/agentrun can't start the server it says, on stderr, the step that
    failed, how the server ended (its exit code; the signal, with a hint when a SIGKILL nobody sent points to the system
    running out of memory; still running after 60 s, then stopped; or never started, with the error), the server's last
    lines on stderr and stdout, and start.log in the data folder, which holds everything the server wrote in that start.
    A server that ignores the SIGTERM after 60 s gets a SIGKILL instead of leaving the command waiting forever (#2980).
  • Learning keeps its replays. A running replay finishes: a revision that arrives meanwhile is queued, and only the
    newest queued one replays next (#2970). The Learning tab's after figure counts only runs a learned workflow served, and
    says why it is empty when it is; on a 480-run agent the cost read takes 7 store calls instead of 1,549 (#2975).
  • Judge requests that fit Jev. A Jev request that may not fit Jev's context goes in its long-context mode, and one
    that may not fit that either has its longest state values cut, each marked [cut], where Jev refused the whole request
    and failed the workflow step (#2969).
  • Computer vendors. The shared machine-host adapter takes vendors that keep no labels, splits exec into the calls a
    vendor has (framedExec), sets a backstop on a vendor's own delete timer and keeps a vendor's idle timer from ending a
    quiet computer; the conformance kit prints what a machine offers and runs on a plan that keeps few machines at once
    (#2973, #2979, #2982, #2967, #2978).
  • A console that lines up. Settings pages share one layout, forms use the width they have, the Playground's code
    panel folds, and a keyboard or a screen reader gets through every page (#2675).

Breaking

  • A running replay is never cancelled (#2970). decided: "superseded" and superseded_by are gone from a learned
    workflow's promotion records and from a replay read's decided: a revision that arrives while another replays is
    queued, and one queued before a newer one is skipped, with skipped_by naming the newer revision. A client that
    read superseded reads queued, skipped and skipped_by. Both generated clients change with it.
  • A hosted vendor's exec carries text (#2979). It has to keep UTF-8 text intact both ways, where it had to carry every
    byte value; the daemon's upload through exec goes as base64 text. In the conformance kit the pre-check's
    stdout-bytes and stdin-bytes are stdout-text and stdin-text, bytesProblem is textProblem, and runToExit's
    stdin is an iterable of pieces, each whole UTF-8 text.
  • The box Dockerfile takes no build arguments (#2989). Its build is box/install.sh, with the archil client's version
    and sums pinned there.

Behaviour changes

  • A template package's Composio trigger must name a required Composio need of the package (#2974): one that names no
    source: composio need is refused when the package is read (422 at import), and the need it names is
    required: true. A trigger made with POST /v2/triggers is unchanged.
  • A pi run's effort costs what it asks for on OpenRouter (#2985): a run that sets an effort on an OpenRouter Chat
    Completions model may cost more and take longer than it did, since the effort was dropped before; a run with no effort
    set sends what it sent before.
  • The learning cost read's after side is served runs only (#2975). A replay run, and a run by hand after the takeover,
    no longer move summary.after, times_cheaper, withheld or hand_backs; the new summary.after_state says why
    after is null (no_served_runs or cost_unknown), else priced.
  • A Jev judge request over the default context runs in the slower long-context mode instead of failing (#2969); pass
    longContext: false to cut to the default context instead. A decision receipt's state is the state its provider sent,
    with state_cut naming each value cut; state_sha256 is still the digest of the state asked.
  • apps.launch of a url in an app that already runs fails unsupported when the launch shows a dialog of its own
    (Firefox's "already running" box), naming the dialog and what to do, where it answered that it opened (#2972).
  • A machine host that keeps labels in the machine (HostFacts.labels: "machine") must declare lifetime: "vendor" or
    backstop: true, and a host with idleMs must give a keepalive (#2973, #2982).
  • A new box image (#2989). The box recipe's hash covers box/install.sh, so beta.40 uses a new box image
    (agentrun-box-<hash>, a new E2B template and Daytona snapshot): the first computer in an account starts it once more
    as on first use (Agent37 registers it, Modal pulls it).
  • email_send asks past 5 sends in a run, and outside the email's thread, even on allow (#2977). With accounts off,
    where no one can approve, such a send is refused in those words. An email trigger's create or turn-on waits for its
    first check (10 seconds at most) before it answers; mail that lands during that call counts as already there, a mail
    server that can't be reached at creation writes no history line, and a sign-in refused at creation counts toward the
    three in a row that turn the trigger off.
  • npx @parcha/agentrun makes its data folder and writes start.log there (#2980): the folder is made before the
    server starts (mode 0700, as the server makes it) and the log is private (0600), since the server's first lines name its
    API token. Each start overwrites it. A server's stderr now passes through the command at the pace it is read.

Known issues

Known issue, Mode 2 (the run folder on your Archil disk):

  • Works: sandboxes on Agent37, Modal and E2B, and desktops on Agent37 and E2B, in any account. The first computer in an account starts from AgentRun's public box image: Agent37 registers it once ("pulling" for about 15 s), Modal pulls it once (about 35 s), E2B starts from a public template in about 5-10 s. Shell commands start in /workspace, the run folder.
  • Not yet: Modal sandboxes with GPUs (the Archil mount isn't proven on Modal's GPU runtime), and Daytona (no Archil mount yet).
  • What to do: for those two, use another provider for Mode 2, or set the computer to none.

Known issue, spend caps: a cap below what the model needs for one step and an answer wraps up early; saving such an agent now warns.

Dependencies

  • No dependency changed: package-lock.json, every workspace manifest's dependencies and docs/dependencies.md are as
    in beta.39.

What you can do now

  • Ship a template package with a Composio trigger on its own Composio need, filled from the owner's parameters (#2974).
  • Apply a template whose setup is only parameters from its own screen (#2981).
  • Run ERNIE 5.5 Flash Preview (free) on pi through OpenRouter, and set a pi run's effort on gpt-6.1-sol through OpenRouter
    (#2984, #2985).
  • Run a runner of hundreds of runs on a Postgres store a few milliseconds away (#2971, #2976).
  • Read why the Learning tab's after figure is empty (summary.after_state) (#2975).
  • Fold the Playground's code panel to give its form the room (#2675).
  • Measure a computer vendor before writing its provider: --exec-stream prints what the machine offers, --concurrency
    fits a plan that keeps few machines, and --long checks a quiet computer outlives the vendor's idle timer (#2967,
    #2978).
  • Follow the inbox quickstart: an inbox assistant on your laptop in three minutes, on your ChatGPT plan (#2955).

Fixed

  • Runs and servers:
    • A runner holding hundreds of runs on Postgres renews its claims in a few statements, so it no longer loses them all at
      once on a database a few milliseconds away (#2971).
    • A store call on a busy Postgres pool waits up to a write's deadline instead of failing at 4 s (#2976).
    • A person's answer that lands just as a run parks on its question resumes the run from the park, where it could start
      a turn the park then cut and leave the run reading working/idle for good (#2986).
    • With the runner beside the server (the default), a SQLite write no longer fails "the store stayed locked past its busy
      wait" when the process is held up about 10 s while a transaction of its own holds the lock: the wait gives back the
      time the process was held up, as that transaction's deadline does; a wait on another process's write still ends at
      the busy wait (#2986).
  • Models:
    • pi never sends reasoning off to an OpenRouter model that must reason (ERNIE 5.5 Flash Preview, free) (#2984; its
      changelog entry came in #2987).
    • A pi run's effort reaches an OpenRouter Chat Completions model; on a model that can stop reasoning (Ling 3.2 Flash),
      any effort was sent as reasoning off (#2985).
  • Learning:
    • A running replay is no longer cancelled by a newer revision (#2970).
    • A promotion record a beta.39 store holds as decided: "superseded" reads as skipped, with skipped_by and a reason
      saying so, so the promotions list and its replay read show it decided, never running; nothing rewrites the stored
      record, and it never blocks a new draft's replay (#2990).
    • The learning cost read's after side counts only served runs, and its reads are batched per agent (#2975).
    • A Jev judge request over Jev's context no longer fails the workflow step with max_tokens_exceeded (#2969).
  • Computers and console:
    • A url handed to a running Firefox no longer reads as opened when Firefox never got it; the Screen tab no longer says
      "released" right after a person allows a parked run; the "Asked your approval" row sits above a park's rows on the
      Timeline (#2972).
    • A vendor's own delete timer gets a backstop so a machine still ends when the server is gone, and a vendor's idle timer
      no longer ends a quiet computer under a run (#2982).
    • Console layout and accessibility across Settings and the Playground (#2675).
  • Email: the OpenAPI document's cap on the email account's password is the server's, 1,024 characters (it said 320),
    and the tool catalog's email summaries are the tools' own descriptions (#2977).
  • Launcher: a start that fails always says why, with the step, the exit code or signal, the last lines and the start
    log; a launcher that can't be run says so instead of a stack trace, a server command (import, ...) that can't be
    started or is ended by a signal says so instead of exiting 1 silently, and a closed stderr (a | head) never ends the
    command (#2980).

Also in this release

  • Computers: the shared adapter for vendors that keep no labels (#2973), framedExec and exec as text (#2979), the
    backstop and keepalive (#2982), the conformance kit's machine facts, stdout-unread, deleted-stays-gone and
    lifetime.idle (#2967), --concurrency with the listing's backoff (#2978), and the box image's build as
    box/install.sh, so a vendor that builds images in its own account runs the Dockerfile's steps, with the
    prepareImage contract written down and a conformance case that calls it twice (#2989).
  • Shipped in beta.39's packages, listed now: the shared machine-host adapter packs labels into what a vendor has,
    adopts a machine a create already named, and logs in over SSH as the host says (#2966); PROVIDERS.md tells a provider
    author in minute one whether and how their vendor fits (#2965). Both merged just before beta.39's release commit, so
    their code shipped in beta.39 while its notes missed them; the changelog files them under 0.1.0-beta.39.
  • Templates: Composio triggers in packages (#2974), Apply for parameter-only templates (#2981).
  • Docs: an inbox assistant on your laptop in three minutes, with Codex on your ChatGPT plan, linked from getting
    started (#2955); PROVIDERS.md catches up with the provider push (packed labels, a 409 adopted, a deleted computer
    kept gone, --long), and the exec pre-check's text failure says "at byte N" (#2988).
  • Tests and CI: a web-fetch test reads its hostile-text link parse as linear in the text's length, not against a
    1,000 ms budget (#2983); a runner test waits on the release event instead of a fixed sleep, and a Docker volume test
    labels its computers by its own volume so a second run of the file beside it no longer leaks into its list (#2986);
    the email-trigger tests wait for a poll's check before moving the fake clock (#2991).

Known limits

  • The learning loop is further along but not finished: a learned workflow that answers wrong with confidence is not caught by the money rule.
  • deploy/compose.yaml (a server and runners) has no Docker socket, so its agents get file tools and web_fetch but no shell; for a Docker sandbox, use the root compose.yaml, run the server on the host, or use a Daytona or E2B computer.
  • The other limits listed for beta.32 still hold.