Lyhnis - Changelog

v2.3726 May 2026· EngineeringFeature

Outbound MCP credentials (`MCP_OAUTH`)

Workflows can now call external MCP servers as tools. A new MCP_OAUTH credential type stores the server URL plus OAuth tokens, encrypted with Fernet under the per-tenant key. Agents accept MCP server URLs alongside built-in activities in their tools list.

The agent’s tool vocabulary expands transparently and the same author-explicit safety primitives apply. Every external MCP call lands in the audit log with its credential ID and target server, so outside tool usage stays fully reviewable.

Python · agent.run with an MCP server

credentials.create(
    name="linear_mcp",
    type="MCP_OAUTH",
    server_url="https://mcp.linear.app",
)

@workflow("refund_triage")
def refund_triage(ticket_id):
    return agent.run(
        model="claude-sonnet-4-7",
        tools=[stripe.refund_charge, notify.slack, mcp("linear_mcp")],
        budget=budget(turns=10, tokens=50_000),
    )

Fernet-encrypted with per-tenant key derivation - the same vault as every other credential type
Audit log captures mcp.call events with server URL and tool name
Step-up auth required to rotate or revoke the credential
Available on Professional and Enterprise tiers

Documentation →SDK reference →Migration guide →

v2.36.119 May 2026Fix

Schedule rotation edge case at month boundaries

Cron schedules with day-of-month constraints (30 23 30 * *) could skip a fire when the previous month had fewer days. Fixed - affected schedules catch up on their next nominal fire.

v2.3612 May 2026· EngineeringFeature

Sub-workflows as tools

Agents can now invoke other workflows as typed tools. The author defines the signature; the agent calls it like any built-in. Validation, HITL gates and audit-by-construction wire in at the workflow boundary, so the agent never touches raw API access.

This is the cleanest pattern we have found for letting agents do real work safely: the workflow is the safety primitive. To let an agent issue refunds you do not grant it Stripe access - you grant it your process_refund workflow, which already carries the right policies, gates and logging.

Sub-workflows declared in the parent’s tools=[...] list, same as built-in activities
Recursive cost rollup: the parent’s budget includes the sub-workflow’s spend
HITL gates inside sub-workflows pause the entire parent run, durably
Available on Professional and Enterprise tiers

Documentation →Pattern: workflow-as-safety-primitive →

v2.35.25 May 2026Improvement

Audit log export now streams

Previously paginated at 1,000 entries per request, so large ranges needed client-side orchestration. Export endpoints now stream NDJSON for arbitrary ranges - customers with multi-million-entry ledgers saw export wall-clock drop from minutes to seconds.

v2.35.130 Apr 2026Fix

Communications: subject overflow in narrow viewports

Long subject lines could overlap status pills under 1100px. Added an ellipsis at the column boundary and a hover tooltip for the full subject.

v2.3528 Apr 2026· EngineeringImprovement

Recursive cost rollup for `agent.run`

Previously a parent agent that invoked sub-agents or sub-workflows reported only its own token spend. Customers with multi-level compositions had to reconstruct cost by hand from the audit log.

Now: one number per agent run, top to bottom. The parent’s tokens_used and cost_usd include every nested agent’s spend, every sub-workflow’s tokens and every external tool call. Budgets enforce against the rollup, not just the parent’s own usage.

- tokens_used: 4,200 # parent only - cost_usd: 0.18 # parent only + tokens_used: 47,180 # rollup, incl. 3 sub-agents + cost_usd: 2.04 # rollup + breakdown: # new field + parent: 4,200 + sub_agents: 42,980

Migration note: if your monitoring alerts on cost_usd, expect values to jump for agent runs that compose other agents. The old behaviour is available as cost_usd_parent_only for two more releases.

Documentation →Migration guide →

v2.34.121 Apr 2026Security

Step-up auth now required for credential rotation

Rotating any stored credential - API keys, OAuth tokens, MCP credentials - now requires re-authentication regardless of session age, bringing rotation in line with other destructive operations. Applies automatically; no customer action needed.

v2.3414 Apr 2026· EngineeringFeature

Communications

Every Slack, Teams, email and Telegram message your workflows send, in one place. Each row carries the recipient, channel, subject preview, delivery status and a one-click jump back to the workflow step that sent it.

Built for compliance and ops in equal measure: compliance gets proof of contact with audit-grade timestamps, ops gets a deliverability view with retry status and per-channel failure rates.

Captures notify.slack, notify.teams, notify.email and notify.telegram
Filter by channel, recipient, status, date range and originating workflow
Retry tracking for transient failures - rate limits, temporary network errors
CSV export for compliance reporting
Available on all paid tiers

Documentation →Compliance use cases →

v2.33.27 Apr 2026Improvement

Files & lineage: 40% faster for large tenants

Rewrote the lineage fetcher to use a single BFS query instead of N+1 traversal across the junction table. Tenants with 10K+ files saw first paint drop from ~2.4s to ~1.4s.

v2.33.11 Apr 2026Fix

PDF preview lazy-load on Safari

PDF.js worker initialisation could race with Safari tab-throttling, leaving the preview blank on first open. Now waits for the worker ready signal. Affected roughly 3% of Files sessions.

v2.3324 Mar 2026· EngineeringFeature

Files & lineage tracking

Every file produced or consumed across runs is now tracked, with role inference - upload, source, artifact, dataset, template - and full lineage back to the uploader, the workflow and the activity.

For regulated industries this is a compliance primitive: prove what data went into a model, which workflow produced a given output, and who uploaded the source documents.

Explicit junction table for producer / consumer relationships - no JSONB scanning
Per-type previews: PDF, images, CSV/XLSX, JSON tree, plain text
Inline lineage graph with BFS traversal and bezier-routed edges
Bulk select, delete and CSV export

Documentation →Compliance patterns →

v2.3217 Mar 2026Improvement

Jobs list: server-side filter, search and pagination

The Jobs list previously loaded everything and filtered client-side, which struggled past 100K jobs. Now server-side search across name and ID, status and trigger filters, and cursor-based pagination - plus a summary endpoint for the stats row.

What we shipped,
and when.

Outbound MCP credentials (`MCP_OAUTH`)

Schedule rotation edge case at month boundaries

Sub-workflows as tools

Audit log export now streams

Communications: subject overflow in narrow viewports

Recursive cost rollup for `agent.run`

Step-up auth now required for credential rotation

Communications

Files & lineage: 40% faster for large tenants

PDF preview lazy-load on Safari

Files & lineage tracking

Jobs list: server-side filter, search and pagination

Hear about every release.

What we shipped,and when.

Outbound MCP credentials (MCP_OAUTH)

Schedule rotation edge case at month boundaries

Sub-workflows as tools

Audit log export now streams

Communications: subject overflow in narrow viewports

Recursive cost rollup for agent.run

Step-up auth now required for credential rotation

Communications

Files & lineage: 40% faster for large tenants

PDF preview lazy-load on Safari

Files & lineage tracking

Jobs list: server-side filter, search and pagination

Hear about every release.

What we shipped,
and when.

Outbound MCP credentials (`MCP_OAUTH`)

Recursive cost rollup for `agent.run`