Monthly Dispatch: September 2026

Issue No. 5September 18, 20268 min read

Welcome back to the Plexara Monthly Dispatch. This month the assistant can hand work to the platform. A report it got right becomes a script Plexara runs on a schedule, with no model in the loop. A CSV you register becomes a table the warehouse can join, and the registration follows the file when the file is replaced. Every query and API call states what it was for, so a session can be opened long after it ended. And sessions start lighter: fewer round trips, a shorter orientation, answers with less back-and-forth. Down in the usage tip: when the report is right, ask for the script.

What is new this month

The assistant writing the report is no longer the thing that has to run it. The same wave also let you register a spreadsheet as a table, put a stated purpose on every call, and cut the start of a session down to what the assistant actually needs.

Your assistant can hand work to the platform

New

Once the assistant has worked out a report, it can save that logic as a script. Plexara runs it on request or on a schedule, under the access its author holds. The run involves no model and charges no tokens. Every run is recorded with what triggered it, which version ran, what it produced, and how it ended.

On September 6 a script also started keeping a record of where it got to between runs, so a nightly job that missed a fire covers the gap on its next one. A script can be handed to a new owner; the handoff states what happens to the reports its runs created and moves them when you ask.

Quoted from the report that runs without the agent: the regional flash is 96 lines, three queries, and 1.85 seconds on a live run. See Automations, lesson 602 for the save, and lesson 604 for the schedule.

For practitioners: when the report is right, save the logic once. For managers: unattended work leaves a run record, and a missed night is covered by the next fire.

The Script page for Daily Sales Report, owned by sarah.chen@example.com, scheduled every weekday at 7:00 AM America/Los_Angeles, status active, running version 2, with required parameters report_date and source, an About section tagged reporting, sales, and weekly, and a What it produces note naming the daily-sales CSV asset. — A script in the portal: the schedule in words, the version that runs, the parameters each fire binds, and what it produces. Lesson 604 covers setting the cadence and reading the run record.

Register a spreadsheet as a table the warehouse can join

A CSV uploaded to Plexara, or one the assistant built, can be registered as a table the warehouse can join, with nothing copied. You or the assistant register it; other files stay files. A file the warehouse would misread is refused with the reason, and the panel offers to save a corrected copy as a new version and register that.

A registration follows its file when the file is replaced. Pinning to one version is a choice on the form. A follow that cannot be completed puts the previous table back and flags it behind its file.

From the spreadsheet that joins your warehouse: the demo chain's median store spends 12.8 percent of revenue on occupancy, and Store 36 sits at 42.2 percent. See Spreadsheets as Tables, lesson 502, and lesson 505.

For practitioners: the join runs in the warehouse instead of in the chat. For managers: replacing the file does not silently leave last month's rows in place.

The Scratch Tables page listing four registrations on the acme-scratch connection: analyst_regional_sales_summary marked Follows the file, analyst_seasonal_factors and analyst_glossary flagged Behind the file, and analyst_q1_promo_codes flagged Source deleted, with columns for table name, connection, source, column count, who registered, and state. — Scratch Tables: every registration you can see, with its qualified name, connection, source file, and whether it still follows that file. A table whose file moved on without it is flagged rather than serving old rows quietly.

Every query and API call states what it was for

Before the platform runs a query or calls an API, the assistant states in one sentence what the call is for: the question behind the query, not a restatement of it. That line leads every row later, because it is the only line about the call a person wrote.

Activity gained My Sessions and My Calls. A session opens as what it produced and its calls in order, each with its stated purpose, and stays readable long after it ended. My Calls catalogs every query and API call and what came of each: satisfied, failed, superseded, or ran, derived on every read. A query that answered a question can be published as a saved query. Every save records the calls the asset was built from; a failed query stays in the record. Calls made by a script's run stay in the audit log and out of the catalog, so the catalog remains a list of calls a person might re-run.

The walk is in Every call your agent makes states its purpose. Lesson 306 covers provenance. The product page is Governance.

For practitioners: open Activity, read one session, publish one query that worked. For managers: "what did the AI do with our data, and why" is now a page.

The Session detail page for an Agent session started 8/29/2026 at 1:58:49 PM, with summary cards for 61 calls, 1 failed call, a duration of 127 hours 16 minutes, 1 asset, and 14 insights, an Assets panel naming Q4 Revenue Dashboard, and an Insights list showing applied, rejected, and pending review statuses. — One session, opened: what it produced, and the insights it captured with the review status each is sitting at. Every call your agent makes states its purpose walks the rest of the record.

Sessions start lighter

The first thing you notice is less back-and-forth. The orientation at the start of every session no longer carries the whole prompt library. It carries one line per capability. Sixteen tools were replaced by four, so a table's whole picture comes back from one call.

Lesson 203 is the discovery path. The argument behind the cut is in Why more tools won't make your agent smarter.

Smaller things worth knowing

Uploaded files are filed in folders, shown with thumbnails, and list every script, session, and person that has written them. A report can reference a logo or a data file instead of carrying it, so a scheduled script refreshes the file and the dashboard stays current. Knowledge now carries built-in documentation pages, each with a Built-in badge. A new APIs page lists every operation a role can call. Agent instructions can be promoted from an approved claim and rolled back.

Lesson 209 covers the resource library. The rest of the portal tour is on the portal page. Full release notes are on the changelog.

From the Learning section

Two new lesson series landed this month. 500 Spreadsheets as Tables starts with why the last mile of data is a spreadsheet, and why loading it used to be a project. 600 Automations starts with the division of labor the series runs on: a script for the deterministic part, the model for writing it and for judgment about what it produced.

500: Spreadsheets as Tables

Five lessons, from the gap a chat agent cannot close on its own through upload, meaning, the join, and next month's file. The registration model is a table over the file where it sits, nothing copied, and a file the warehouse would misread is refused with the repair written through the file's own history.

600: Automations

Six lessons, from the Monday report that gets rebuilt every week through the agent writing the first script, outputs that refresh themselves, running by hand and on a schedule, what a run may do, and a weekly review where three scripts do the data work and the model does the judgment.

A tool catalog is not a data platform

August 13, 2026

Agent integration platforms now advertise thousands of connected apps. Catalog size is the wrong axis. What determines whether an agent produces dependable work is what surrounds the call: where the answer lands, who was allowed to make it, and what the platform remembers afterward. One production deployment exposes a fundraising CRM with 577 operations this way; the agent finds the one it needs by describing the goal.

The public data your warehouse is missing

August 22, 2026

The federal statistical system publishes demographics, income, employment, weather, and traffic through free APIs. Almost none of it sits next to company data, because getting one source into a warehouse was an integration project. Give an agent a governed gateway to these sources and the friction is gone. Every figure in the piece was fetched live through a Plexara deployment while it was being written.

When the answer is an action

August 30, 2026

Business intelligence has always ended at a finding: the analysis stops, and the action moves to other tools, other people, and next week. An agent that reaches remote systems through a governed API gateway closes that gap. The same session that finds twelve thousand lapsed members can push the segment, schedule the send, and read the result, with access granted per route rather than per app.

Usage tip: when the report is right, ask for the script

The first thing most people do with an AI agent is speed up their daily routine, and reporting is the first thing most teams point it at. That works until it becomes a habit: every Monday you ask the assistant for the same regional flash, it re-derives the joins and the baseline, and you spend tokens on logic that was settled weeks ago. Two Mondays can also come back slightly different, a changed rounding, an alternate join that looked equivalent.

The settled part should move to a script. The judgment stays in conversation: whether this week's movement is the holiday surge arriving on schedule, or something that needs a call. Getting the report right is an hour you should spend once. Running it is three queries and a couple of seconds.

This report is right. Save the logic as a script called 'Monday regional flash': the same queries, the same baseline, the same layout. Dry-run it, show me the log, and if it matches, schedule it for weekdays at 6:30 in Los Angeles time and publish the result to the dashboard I already have.

What happens next is a loop the platform enforces. Validation parses the source and reports what it would reach, before anything runs. A dry run executes it for real under your identity, with nothing persisted, and returns the log. Only a save makes a version live, and a version that does not parse cannot be saved. The schedule is a cadence, a timezone, and the parameter values each fire binds, set in those words. A failed scheduled run mails its owner with the reason and the log's tail. Lesson 602 is the save. Lesson 604 is the schedule.

For practitioners. You stop being the person who re-asks for the numbers and become the person who reads them. The compiling still happens. It just is not your Monday morning anymore.
For managers. The report stops living in one person's chat history. It becomes a versioned script with a run record, and a failure arrives as an email with the log rather than as a missing attachment.

Worth reading from others

Three pieces this month: the MCP spec's next direction, a CLI that refuses to let a model pick the next step, and a general explainer on what a trace of agent work has to carry.

The New MCP Roadmap

David Soria Parra and Den Delimarsky, Model Context Protocol Blog, August 22, 2026

It follows the 2026-07-28 spec release last issue covered and names five priority areas for the next release: agentic messaging primitives, HTTP-native transport unification, agent identity and enterprise security, better primitives for tool calling, and SDK developer experience. For a reader whose agent reaches Plexara over MCP, the direction that matters is toward stateless servers and stronger identity, which is the direction Plexara already runs in.

Conductor: Deterministic orchestration for multi-agent AI workflows

Jason Robert, Microsoft Open Source Blog, May 14, 2026

An open-source CLI where workflow routing is fixed in YAML rather than decided by a model at run time. The argument that matters for this issue: when a workflow has known structure, a model deciding the next step is cost without benefit. That is the same split the automations item makes between judgment and repetition.

What Is AI Agent Observability? How to Trace, Govern, and Control Agents at Scale

Olivia Greene, OpenHands, August 25, 2026

A general explainer that narrows into a product pitch in its last third; read it for the four things it says a trace must carry (instructions and plan, tool calls and actions, validation outcomes, cost attribution) and then stop. A Plexara session record already carries the first three as purpose, the call timeline with outcomes, and what the session produced. Cost attribution against a model bill is a different layer: automated runs on Plexara involve no model, so there is no token line to attribute.

We read every reply. One concrete pointer: the built-in documentation pages now sit inside every Knowledge area, with a Built-in badge. If your team wants its own version of a topic, hide the built-in page and write yours; it can be restored later.

If a scheduled report failed last week and the email with the log did not land where you expected, reach out and ask. We would rather hear it from you now.

The Plexara team