Plexara
What is new in Plexara
Start at the beginning: the Plexara historyFully managed, always current
Plexara is a fully hosted and managed service. Upgrades, infrastructure, and routine maintenance happen automatically behind the scenes, so there is nothing for your team to install or patch. This log covers only the changes you can see and use: new capabilities, portal improvements, and platform changes that affect how your teams work.
- v1.126.4
Spreadsheets as tables, shared files, and automations in the portal
Knowledge & CatalogPortal & UXIntegrationsA CSV uploaded to Plexara, or one the assistant built, is now a table the warehouse can join, with nothing copied. A report can reference a logo or a data file instead of carrying its bytes, so a scheduled script refreshes the file and the dashboard reading it stays current. Automations got their own section of the portal, and the platform now ships its own documentation as pages inside your Knowledge area.
Spreadsheets as tables
A CSV saved as an asset or uploaded as a resource now carries a Query as a table panel: pick the connection, name the table or accept the default, and the assistant joins it against the warehouse with SQL over the file where it sits. The assistant can register a file by reference without the portal step. A file the warehouse would misread, a line break inside a cell, carriage-return line endings, an encoding that would corrupt columns, is refused with the reason, and the panel offers to save a corrected copy as a new version and register that, with the correction recorded in the file history. A new Scratch Tables page lists every registration you can see, with its qualified name, connection, and source file, and flags a table that is behind its file or whose file is gone.
Automations in the portal
Scripts have a section of their own: what you have, what is scheduled, and what is failing, with a Runs tab across every script you own. Opening a script shows its details, a schedule you set in words rather than cron (weekdays at 7:00 AM in your timezone), what it says about itself as a formatted document filed under a category and tags, its source with version history, and its run history directly beneath. Run, Validate, and Dry run sit above the editor: a dry run executes what is on screen as you, keeps nothing, and reports what it would have produced. A script can call the same tools its author can, publish a document as well as a table, and refresh the data behind a dashboard without rewriting the dashboard itself. Admins see every script on the platform and can move one to a new owner.
Reports that reference files instead of carrying them
An asset can name a logo, a photograph, a data dictionary, or another asset by reference instead of embedding its bytes, and every viewer resolves the reference when the page is read. A reference to another asset always resolves to its current content, so a script that rewrites a CSV on a schedule keeps the dashboard reading it current without the dashboard being re-saved. A References panel shows what an asset depends on, Used by shows which reports read a file, deleting a referenced file warns and names them first, and the assistant is told before a reference is made that anyone who can open the asset can load the file through it.
A resource library organized by category
Uploaded files now group by category, with sections that fold and remember how you left them, and a section of images is shown as a grid of tiles. Each resource opens at a page of its own, can be moved to another library (yours, a team persona, or the shared library) with the move recorded, and can be written by the assistant or a scheduled script, with the change landing in the file history like any upload. Uploading is offered only in a library you are allowed to add to.
Documentation that ships with the platform
Your Knowledge area now carries a set of built-in pages: how to write a script, how outputs and exports are named, the dashboard pattern that refreshes its own data, asset references and the refresh loop, and the content types for stored files. Each carries a Built-in badge and a diagram, is updated with every release, and is read-only where your own pages are edited. If your team wants its own version of a topic, hide the built-in page and write yours; it can be restored later.
Every API operation, browsable
A new APIs page lists the connected APIs your role can call and, on each, the operations it may reach, grouped the way the API documents them and searchable by name, path, or summary. Opening one shows its parameters, request body, and responses, the requests promoted from calls that worked, and a copyable call that performs it through the Plexara API from a pipeline or a script. An admin now sets which endpoints a persona may call from the portal, and the page and the assistant agree on what a caller reaches because they read the same rules.
Version history with a bound, and previews that match
An asset keeps its most recent hundred versions, its owner can raise or lower that from the sidebar, and the current version is never pruned. JSON assets get previews, collection previews follow your light or dark mode, an owner can recapture a preview on demand, and a signed-in colleague who opens a share link lands on the item in their own portal, with its feedback panel beside it.
- v1.121.1
Automations, and every session on the record
Agent EfficiencySecurity & GovernancePortal & UXYour assistant can now hand work to the platform: a report it worked out once becomes a script Plexara runs on demand or on a schedule, with no model in the loop. Every session, query, and API call is now a record with a stated purpose and an outcome, a saved asset points at the calls that produced it, and the portal was rebuilt on one consistent set of components.
Automations: scripts your assistant writes, Plexara runs
Once the assistant has worked out a report, an export, or a dashboard refresh, it can save that logic as a script. The script runs on request or on a schedule (hourly, daily, weekdays, or a day of the month), under the access its author holds, and delivers its output as a saved asset or to a storage bucket your team has been granted. Every run is recorded with what triggered it, which version ran, what it produced, and how it ended, and a scheduled fire that arrives while the previous run is still going is recorded as skipped rather than dropped. Scripts turn up in search by what they do, and a prompt can reference one.
Sessions and calls you can open
Before the platform runs a query or calls an API, the assistant now states in one sentence what the call is for: the question behind the query, not a restatement of it. Activity gained My Sessions and My Calls beside the overview. A session opens as what it produced and its calls in order, each with its stated purpose, the connection it went to, and whether it succeeded, and it stays readable long after it ended. My Calls is the catalog of every query and API call you made and what came of each. Admins see the same views across everyone, and a query that answered a question can be published to the catalog as a saved query, or an API call as a worked example on its endpoint, so the next person starts from something that worked.
An asset names the calls that produced it
Every save records the queries and API calls the asset was built from, with each call's purpose, outcome, and duration, and the assistant can name the exact calls it used. The asset viewer shows that provenance by version, keeps a failed query in the record rather than hiding it, and links to the session the work belongs to. The assistant can recall its own past work the same way, by what it was for, and follow a result back to the session that made it.
Told what is waiting, at the start of a session
The first thing your assistant learns in a new session is what is waiting for you: unresolved feedback on assets you own and what was newly shared with you, which it relays before starting on your request. Each notice is delivered once, so a session repeats nothing you were already told. Sharing an asset with a colleague can now be done from the conversation as well, and a link that only signed-in users can open no longer expires. Admins can share and hand on any asset or collection, including ones an agent created under a service account that nobody can sign in as.
Knowledge that says how to check it
An insight delivered to your assistant now names the table and connection one query would settle it against, so a claim about your warehouse arrives with the way to verify it. Reviewers see the same under a pending claim: what the entity is queryable as and where it lives. Rolling back an applied change returns its insights to the review queue for a fresh decision instead of retiring them, a long knowledge page is now searchable across its whole length, and anything saved, edited, uploaded, or approved is searchable as soon as it lands.
A portal rebuilt on one set of components
Every section of the portal, from the catalog and prompts to knowledge, assets, and admin, now sits on one consistent set of components, with pages, cards, and panels told apart by their surface. Lists open on the work most recently touched and let you choose the order, every page has an address you can bookmark or hand to a colleague, glossary and domain definitions render as formatted text, prompts group into collections in both your own library and the team library, and connected APIs accept file uploads and paths with more than one parameter in a segment.
- v1.119.0
One place to govern what your business knows
Knowledge & CatalogPortal & UXAgent EfficiencyThe two libraries your team leans on most, its prompts and its catalog, both grew into something a person can actually maintain. Prompts carry version history, collections, and run counts. The whole catalog is now governed inside Plexara rather than in a separate tool. And a fact one person teaches the platform is findable by everyone, whichever shelf it landed on.
A prompt library with history, collections, and usage
Every prompt now keeps its own version history, with the approval bound to the version it approved and any two versions comparable line by line. Prompts group into collections by team, domain, or workflow, and each row reports its run count and how long since it last ran, so the procedures your team actually relies on are easy to tell apart from the ones nobody has opened in months.
Your prompt library, open inside the chat
Ask your assistant to show your prompts and the library opens in the conversation: search as you type, filter by collection or tag, then fill in a form built from whatever the prompt needs and run it right there. Clients that do not render interactive panels get the same results as plain text, so nothing depends on which one your team uses.
Govern the whole catalog without leaving Plexara
Tables, context documents, tags, domains, and the business glossary now sit under one Catalog tab. Define what a tag means, describe the business areas your data is grouped into, and maintain the glossary your organization writes its definitions in, all with the same editing your team already has for table descriptions. Retiring anything states its blast radius first, so removing an unused label never looks like removing one the warehouse depends on.
See the shape of what your team knows
A new graph view draws your knowledge as its reference network: every page, every table, prompt, and asset a page cites, and every link between them. It opens on the idea the most connections run through, groups the corpus into topics, and sizes each node by how much of the picture it holds together, so the concepts your business is really built around are the ones you see first.
What one person teaches, the whole team can find
Once a captured insight is reviewed and promoted, everyone who searches can find it, attributed to whoever captured it. Before this, a fact written into the catalog rather than onto a knowledge page reached nobody but its author unless a question happened to name the exact table it hung off. Your catalog descriptions are now searched by meaning too, so a question about a topic finds the tables described in those terms.
Reference material your agent can actually find
The files your team uploads for agents to use as they are, templates, brand files, data dictionaries, now turn up in the same search as everything else, matched on what is inside them rather than just their names. Replacing a file keeps every prompt and citation pointing at it working, each revision is kept and restorable, and each resource reports how often it is actually read.
- v1.106.0
Work that reaches people outside the portal
Portal & UXSecurity & GovernanceSharing stopped depending on the other person being signed in and looking. A share or a comment now sends an email, everyone sets their own delivery, and someone with no Plexara account can open exactly what was sent to them without the link turning into something anyone can forward.
Told when something needs you
Sharing an asset, collection, or prompt emails the person you shared it with, and so does a comment on something you own or that was shared with you. Everyone picks their own delivery: one email per event, a single daily digest, or none at all, with separate switches for shares, comments, and mentions. The email never holds up the share or the comment that triggered it.
Guests can open what was shared with them
A recipient with no Plexara account lands on a branded page and can ask for a one-time view link, sent only to the address the share names. It expires within minutes, dies after its first use, and opens a view-only session scoped to that single item. Guests can download but never edit, and never reach the portal.
A share reaches only the person it was addressed to
The emailed link resolves once the named recipient is signed in, so forwarding the message on grants nothing. Link shares stay their own separate thing, with their own bounded life.
Unsubscribe in one click
Every notification carries an unsubscribe link that works without signing in, and opening it asks for confirmation rather than acting on the click, so a corporate mail scanner that follows links inside messages cannot quietly opt someone out.
- v1.100.1
Grounded answers, tighter access, leaner context
Agent EfficiencySecurity & GovernanceKnowledge & CatalogThis stretch made answers more grounded and the platform tighter around them. Every answer is now anchored in your catalog before it reaches the warehouse, the portal picked up a round of security hardening, and the business context wrapped around each answer stays lean so it never crowds out your data.
Answers grounded in your catalog first
Before it runs a warehouse query, the assistant now grounds itself in your catalog, so answers reflect the data you actually have rather than a guess at its shape. Fewer confident wrong turns, and more answers you can trust.
A round of security hardening
The portal gained cross-site request protection on every change you make through it, and sign-in was hardened to current standards, so the day-to-day work your team does in Plexara sits on a tighter foundation.
Curate the catalog without losing your work
Making several catalog edits in a row no longer overwrites the tags, glossary terms, or descriptions already there, and every change reports the full result. New portal actions let you remove a tag, edit custom properties, and bulk untag, and the Catalog and Context Docs tabs respect who on your team is allowed to write.
Context that stays out of the way
The business context added to each answer now stays within a set budget with a summary-first layout, and search will not let one slow source hold up a whole query, so responses come back fast and keep the focus on your data.
Nothing captured waits unreviewed
The knowledge review queue now shows how long its oldest item has been waiting and how much has aged past thirty days, so the knowledge your team captures gets reviewed and promoted instead of quietly piling up.
- v1.94.0
Canonical knowledge, linked like a wiki
Knowledge & CatalogPortal & UXAgent EfficiencyYour knowledge layer grew into a real, linked body of institutional knowledge. Captured lessons now flow into durable, human-readable pages that cite the exact data they describe and cross-link to each other, so what your business knows lives in one navigable place instead of scattered notes, and the assistant surfaces it wherever it is relevant.
Canonical knowledge pages
A new layer of durable, human-readable pages, written in formatted text with diagrams, version-tracked on every save, searchable by meaning, and open to feedback in place. They hold the vocabulary, definitions, runbooks, and context that do not fit inside the metadata on a single table.
One Knowledge home
Memory, proposed insights, and canonical pages are unified into a single Knowledge area that shows their shared lifecycle: a note is captured, promoted to an insight for review, and finally promoted to shared, canonical knowledge, with each step gated by who is allowed to apply knowledge.
Knowledge linked to what it describes
Pages and insights reference the exact assets, prompts, collections, connections, and catalog entries they are about. Those references render as live links that always show the current name and work in both directions, so from any item you can see the knowledge that documents it and click through the whole graph like a wiki.
Discover, read, then cite
Search finds the right piece across every kind of knowledge, a retrieve step reads any result back in full, and a canonical reference lets the assistant cite it precisely, closing the loop from finding knowledge to using it in an answer.
Duplicates are prevented, not just discouraged
When the assistant tries to create a page that closely matches one that already exists, the platform steers it to update the existing page instead, so canonical knowledge consolidates over time rather than fragmenting.
- v1.87.0
One front door for discovery
Agent EfficiencyKnowledge & CatalogPortal & UXDiscovery got a single front door. Instead of needing to know the shape of your platform before it could ask, the assistant now finds what exists across every system it can reach with one call, and records knowledge through one consistent action. The portal also got a round of visual and performance polish.
Find anything with one search
A single, universal search spans every source a role can reach, your catalog, memory, captured knowledge, saved assets, prompts, connected APIs, and connections, and returns a balanced set that keeps each source visible rather than letting the largest one dominate, along with a summary of where the matches live.
One way to record knowledge
Capturing knowledge is now a single action that files each note in the right place and avoids re-recording something already known, so the path from a useful moment to durable knowledge is one clear step.
A more polished portal
Asset previews now match light and dark mode and fill the frame edge to edge, the asset grid loads noticeably faster on large libraries, the sign-in button label is customizable, and interactive results built with common React patterns render reliably.
Long documents stay findable
Longer reference documents now index reliably for search, so a big runbook, spec, or policy is something the assistant can actually surface and pull from rather than something too large to find.
- v1.86.0
A human feedback and review loop, end to end
Portal & UXKnowledge & CatalogAgent EfficiencyThe throughline this week was review. People can leave structured feedback directly on saved work, an agent can resolve it into catalog knowledge, and a new Feedback hub gathers everything waiting on you in one place. Sharing with teammates and browsing your assets both got easier.
Feedback threads on your work
Reviewers can open a correction, question, or suggestion directly on a saved asset or collection, or on a specific quote within it, then reply and work it through an open, answered, resolved lifecycle. Asset and collection lists show how many threads are still open, and someone who arrives through a public share link can take part without a separate account.
Resolve feedback into catalog knowledge
The assistant can close a feedback thread by capturing the knowledge it represents, linking the thread to the resulting catalog update so the path from comment to documented change stays visible. The author then confirms or disputes how it was resolved, and disputing reopens the thread.
A Feedback hub, and an agent that works your inbox
A new hub lists every comment, question, and correction across the assets, collections, and prompts you can see, newest first, with a sidebar badge when something is waiting. A dedicated feedback tool lets you ask the assistant to review and reply to anything pending in a single pass, and validation and sign-off keep open items on a worklist so nothing is dropped.
Easier sharing with teammates
The share dialog now suggests known teammates by name as you type while still accepting any email, and a user with editor access can edit a shared asset details, not just its content.
Browse assets by ownership
Collections and items shared with you now live in one Assets area with a Mine, Shared, or All filter instead of separate pages, and Prompts gains a Shared tab.
- v1.83.0
Your context shows up everywhere, and search gets sharper
Knowledge & CatalogAgent EfficiencyPortal & UXThe business context Plexara attaches to every answer now reaches you no matter which assistant you connect, search across your work returns cleaner and better-ordered results, and the prompts your team relies on are finally findable.
Context that follows the answer into any client
The context Plexara travels with every answer, the owners, descriptions, related memory, and what each column actually means, now arrives in a form that every MCP client can read, not just some. If you connect a tool that previously showed bare results, the surrounding context now comes with them.
Sharper, better-ordered search
Results across memory, saved assets, collections, and prompts now separate cleanly instead of bunching together, so the closest match rises to the top instead of getting lost in a tie.
Find every prompt your team relies on
Built-in workflow prompts and the prompts your administrators set up now appear in prompt search alongside everything else, so a shared workflow is something you can look up rather than something you have to already know exists.
Edits that report what changed
Editing only the body of a saved asset no longer shows a failure after it actually saved, and knowledge you or an admin reject is now correctly kept out of what the assistant recalls later.
Shared downloads that work from anywhere
Download links for exported results and files now resolve from outside your network, so a link you share with a colleague or partner opens for them instead of dead-ending.
- v1.81.1
A governed prompt library and search that ranks by meaning
Agent EfficiencyPortal & UXKnowledge & CatalogPrompts grew into a governed, shareable library, and relevance search that ranks by meaning now reaches every corner of the platform: knowledge, prompts, saved assets, and collections, in both the assistant and the portal.
A first-class prompt library
Prompts gain a full lifecycle (draft, approved, deprecated), tags, admin promotion through a review queue, and direct sharing by email, where the recipient gets a real, runnable prompt rather than a flattened copy.
Search by meaning, everywhere
Relevance search (meaning plus keywords, with an automatic keyword-only fallback) now covers captured knowledge, prompts, saved assets, and collections, across both the assistant and the portal, always scoped to what you are allowed to see.
Consistent, self-describing errors
Failed tool calls now report in a uniform, self-describing way, so the assistant can tell a fixable input mistake from an authentication problem or an outage.
- v1.79.1
Bigger exports and self-service configuration
Platform StabilitySecurity & GovernanceIntegrationsThis week rounded out reliability and control. Plexara now handles very large exports without strain, and admins can configure the whole platform just by asking the assistant.
Reliable large exports
Large query results and API responses now stream straight to storage, so you can export big datasets without hitting size limits or slowing the platform.
Configure the platform by asking
Admins can set up the platform by talking to the assistant: create roles, add connections, adjust the assistant instructions, and manage prompts and API keys, with every change attributed and logged.
Tighter access control
Connection access is now closed by default. Each role sees exactly the connections it has been granted and nothing more.
Readable connection notes
Connections can carry richly formatted descriptions with a collapsible reveal, so the context behind each one is easy to read.
- v1.76.0
Smarter tool selection and memory
Agent EfficiencyIntegrationsPortal & UXA busy week focused on making the platform intelligence visible and its answers faster. New dashboards surface the health of search, the assistant finds the right tool on its own, and memory recall got sharper.
See the health of search
A dashboard shows the state of semantic search across your connected systems, with accurate coverage and clear status.
Find the right tool automatically
The assistant can locate the best tool for a request based on what you mean, not just the tool name.
Smarter memory recall
Memory search now blends meaning and keywords, so the assistant brings back more relevant context from past sessions.
Broader connectivity and cleaner audit
Added support for file-based (WebDAV) services, and activity logs now separate assistant activity from API activity for cleaner audit trails.
- v1.67.0
Operability, more authentication, and security hardening
Security & GovernanceIntegrationsPortal & UXOperability and security took center stage. Connected APIs became usable from outside the assistant, live operational dashboards arrived, and security hardening tightened isolation between users.
Use connected APIs from other tools
A web endpoint exposes your connected APIs to tools beyond the assistant, such as data pipelines and scripts, under the same access rules and activity logging.
Live operational dashboards
Live health and usage metrics for your platform, in an admin dashboard for monitoring how it is running.
More ways to authenticate
Added support for APIs that use basic username and password, and for internal or corporate APIs secured with client certificates (mTLS).
Redesigned role editor
A single, clearer editor for a role permissions and the assistant behavior settings.
Security hardening
Tightened isolation so one user activity history can no longer be visible to another on a specific connection type.
- v1.62.2
The API connector matures
IntegrationsAgent EfficiencySecurity & GovernanceWith the API connector in place, this week hardened it for real-world use: versioned catalogs the assistant can understand, more reliable sign-in, and search that matches on intent.
Versioned API catalogs
Each connected API now has a versioned catalog so the assistant reliably understands its operations and inputs, including APIs that need a second credential header.
More reliable connection sign-in
Sign-in for AI-tool and web-API connections is unified, with automatic token refresh before expiry, a history of authentication events, and clearer errors.
Search by intent
API operations are now ranked by what you mean rather than exact keyword match.
- v1.58.3
Connect to any REST or HTTP API
IntegrationsOne of the biggest capabilities yet landed this week: the assistant can connect to and use any external REST or web API.
Call external web APIs directly
The assistant reads each API published description to discover what operations are available, signs in securely on your behalf with OAuth, enforces per-role rules on individual endpoints, and can export API results as assets.
- v1.57.5
Smoother connections, refreshed portal
IntegrationsPortal & UXA round of refinement made connecting external services less fiddly, and the portal adopted a refreshed visual identity.
Easier external connections
Connecting external services is smoother: a clear Connect button for sign-in, and friendly error messages when something needs attention.
Refreshed look
The portal adopts a refreshed visual identity.
- v1.57.0
Reach beyond Plexara
IntegrationsPortal & UXThe platform began reaching outward. A new gateway lets it connect to and use tools hosted on other servers, weaving their capabilities and your context into the same experience.
Connect to other AI tool servers
A new gateway lets Plexara connect to and use tools hosted on other MCP servers, automatically carrying your business context across them.
Redesigned Tools page
A cleaner master-detail layout for browsing everything the assistant can do.
- v1.56.1
Get results out, stay in sync
Portal & UXKnowledge & CatalogPlatform StabilityGetting results out of the platform and keeping clients in sync were the focus. A new export turns any query straight into a downloadable file, and tool lists update live for everyone connected.
Export results to a file
A new export turns any query directly into a downloadable, shareable asset in CSV, JSON, or Markdown.
Live updates
The assistant available tools refresh automatically for everyone connected whenever configuration changes.
Formatted knowledge and memory
Knowledge and memory now render as cleanly formatted text in the portal.
- v1.55.6
The assistant remembers
Agent EfficiencyKnowledge & CatalogPortal & UXThe assistant gained a longer memory and the platform gained more day-to-day flexibility. Preferences and context now carry across sessions, and prompts and reference files can be managed on the fly.
A first-class memory layer
Memory keeps preferences, corrections, and context across sessions, for both agents and analysts.
Manage prompts on the fly
Create and edit prompts directly in the portal.
Upload reference files
Upload and manage files the assistant can use as reference material.
- v1.50.1
Organize and configure without engineering
Portal & UXSecurity & GovernanceKnowledge & CatalogThis week made the platform more organized and more configurable without engineering help. Saved work can be grouped into collections, and more settings became editable directly in the admin screens.
Collections
Group related assets into shareable collections with thumbnails and a browser.
Editable settings
Configure the platform through admin settings screens, with roles and API keys changeable at any time.
Per-role tool and data filtering
Tools and connections are now filtered by role.
Advanced catalog search
Search the catalog with column-level filtering.
- v1.46.0
Richer catalog edits
Knowledge & CatalogA small, focused update broadened how the assistant can contribute to the catalog, adding richer document-style changes when it writes context back.
Document-style catalog updates
The assistant can make richer, document-style updates when it writes business context back to the catalog.
- v1.45.0
Maintain the catalog, not just read it
Knowledge & CatalogUntil now the assistant could read the data catalog. Now it can help maintain it, improving documentation, tags, and ownership through conversation.
Update the catalog, not just read it
The assistant gains tools to create and update catalog entries, so it can help maintain documentation, tags, and ownership.
- v1.44.0
A polished sharing experience
Portal & UXPlatform StabilityThe work this week centered on making sharing genuinely pleasant to use. The public viewer matured into a polished experience, and saved assets gained preview thumbnails and full version history. This week also moved the platform to 1.x versioning: v0.37 became v1.38 under the new scheme, and near-daily releases carried it to v1.44 by the end of the week.
A polished public viewer
A large investment in the public viewer: dark mode, expiration notices, sharing by email with permission levels, save to my assets, view counts, and branded headers on shared links.
Preview thumbnails and version history
Saved assets get automatic preview thumbnails and full version history, including the ability to revert to an earlier version.
One-click prompt workflows
A reusable prompt system with categories and workflow prompts.
Spreadsheet exports
Save and download results as CSV.
- v0.37.0
Save and share what the assistant creates
Portal & UXSecurity & GovernanceA milestone week. The asset portal arrived, turning the things the assistant produces into saved, viewable, shareable items rather than one-off outputs that disappear at the end of a chat.
The asset portal launches
Dashboards, reports, charts, and other outputs can be saved, viewed in the browser, and shared through a branded public viewer, with a record of which tool calls produced each one.
One portal, one login
A single unified portal with single sign-on.
- v0.30.0
Tailored to who is asking
Agent EfficiencySecurity & GovernanceKnowledge & CatalogThe experience started tailoring itself to who is asking. The platform self-introduction now adapts to a person role, tools carry friendly names, and admins can publish their own reference material.
Role-aware introduction
The platform introduction adapts to each person role, and tools carry friendly, human-readable names.
Custom reference material
Admins can publish custom resources the assistant can read on its own.
- v0.26.1
Richer conversations, sharper answers
Agent EfficiencyPortal & UXTwo themes ran in parallel: making the assistant conversational abilities richer, and making its answers sharper, so responses stay relevant without unnecessary noise.
Richer assistant interactions
Reusable prompts, file and resource attachments, live progress updates, and the assistant asking a clarifying follow-up when it needs one.
Smarter, leaner answers
Context is narrowed to the columns a query actually uses, empty descriptions are dropped, and search results include ready-to-run example queries and a schema preview.
Admin portal polish
Light and dark branding, and the ability to replay a past tool call straight from the activity log.
- v0.19.0
Administration and a knowledge loop
Knowledge & CatalogPortal & UXSecurity & GovernanceAdministration moved into a real web dashboard, and the platform learned to get smarter over time. The standout was a knowledge loop: the assistant can capture what people teach it and fold it back into the catalog.
The admin dashboard arrives
A web admin portal with an activity dashboard and the ability to run and inspect tool calls.
Capture and apply knowledge
The assistant can capture insights from a conversation, for example that a column is gross margin rather than revenue, and, with admin approval, write them back into the catalog so no one explains the same thing twice.
Control which tools are available
Admins can turn specific tools on or off.
- v0.14.0
Accountability and smoother sign-in
Security & GovernanceThis stretch was about trust behind the scenes. The platform gained complete, durable activity logging so every action is accountable, and smoothed out the sign-in experience across clients.
Complete activity logging
Every action is now recorded in full detail for accountability and audit.
Smoother sign-in
A round of fixes to the login flow so signing in is seamless across different clients.
- v0.11.0
Richer answers at a glance
Agent EfficiencyKnowledge & CatalogPortal & UXWith access and basic context in place, attention turned to making answers richer at a glance. The assistant began tracing how data connects across systems and showed its first interactive results.
Data lineage in context
Answers now show where data comes from and what depends on it.
The assistant knows the platform
It starts each session aware of which data and tools are available, which produces better, better-routed answers.
Interactive query results
An early look at visual, interactive result views in place of plain text, plus the ability to add custom interactive apps.
- v0.7.1
Where it began
Security & GovernanceKnowledge & CatalogThe earliest releases focused on the essentials everything else builds on: getting people securely signed in with their own accounts, and grounding answers in your own definitions rather than raw database columns.
Single sign-on
People sign in with their existing company accounts, with access governed by their role from day one.
Answers come with business context
When the assistant describes or queries a table, it automatically brings in the surrounding context (owners, descriptions, tags, and glossary terms) from the catalog, so results are not just raw columns.
Before the first release
2018 to 2026: the longer story
This changelog starts with v0.7.1 in January 2026, but Plexara did not start there. It began inside Deasil Works as Methodology, a research project built on a single thesis: a company's data is described by the way its people query it. The foundational pieces were in motion from 2018, the local-model toolkit arrived in 2023, and when Anthropic published the Model Context Protocol in November 2024, Methodology stopped trying to beat frontier models and became the governed layer that makes them fluent in your business. It was renamed Plexara in 2025.
Read the full history