From 4e2513639d45755728d0e1467fbbecc913cdc296 Mon Sep 17 00:00:00 2001 From: Waleed Latif Date: Mon, 12 Oct 2026 14:08:56 -0700 Subject: [PATCH 1/2] improvement(changelog): expand release stories with practical detail --- apps/sim/content/changelog/README.md | 4 ++-- .../compare-workflow-deployments/index.mdx | 13 ++++++++++--- .../compare-workflow-deployments/production.md | 4 ++++ apps/sim/content/changelog/editorial-standard.md | 5 +++-- .../changelog/intune-device-inventory/index.mdx | 13 +++++++++++-- .../changelog/intune-device-inventory/production.md | 4 ++++ apps/sim/content/changelog/maintenance-workflow.md | 4 ++-- .../changelog/nebius-models-for-agents/index.mdx | 7 +++++-- .../nebius-models-for-agents/production.md | 6 +++++- .../changelog/new-models-for-agents/index.mdx | 7 +++++-- .../changelog/new-models-for-agents/production.md | 4 ++++ .../content/changelog/power-bi-for-agents/index.mdx | 13 +++++++++++-- .../changelog/power-bi-for-agents/production.md | 6 +++++- .../content/changelog/review-fork-changes/index.mdx | 9 +++++++-- .../changelog/review-fork-changes/production.md | 4 ++++ 15 files changed, 82 insertions(+), 21 deletions(-) diff --git a/apps/sim/content/changelog/README.md b/apps/sim/content/changelog/README.md index 6da345b64d2..cf151793f2d 100644 --- a/apps/sim/content/changelog/README.md +++ b/apps/sim/content/changelog/README.md @@ -126,7 +126,7 @@ Explain where to find the feature and give one concrete example. 4. Use `` for a screenshot, supplying its actual dimensions as literal attributes to reserve space during loading. The MDX compiler strips JavaScript expressions such as `width={1200}`. Describe what it actually shows; do not use an older screenshot as proof of a new control. 5. Use `###` for sections inside an entry: the article owns the H1 and its details section owns an accessible H2. 6. Keep `draft: true` until the text, availability, media, and links are reviewed. Drafts are excluded from the public page, direct entry routes, archive, sitemap, and RSS. Use the development preview to review them without changing publication status. -7. Publish by removing the draft flag or setting it to false, then deploy the site. Keep the slug and original publication date stable. Add `updated` only for a substantive correction. +7. Publish by removing the draft flag or setting it to false, then deploy the site. Keep the slug and original publication date stable. Add `updated` only for a substantive correction or expansion, not a formatting edit. Before merging, run `bun run check:library-content --slug changelog/` from the repository root. The shared content audit checks frontmatter, authors, folder slugs, reserved routes, images, MDX syntax, internal links, changelog media attributes, and the existence of local recordings and caption files. Published entries also require body media and descriptive cover alt text; future publication dates, correction dates before publication, and duplicate RSS identities fail the audit. `bun run check:audits` runs it in CI. It cannot determine whether an image proves a feature or confirm Cloud rollout, codec quality, or CDN availability; the feature owner and editor verify those in the brief and preview. @@ -136,7 +136,7 @@ For a migrated historical release, use its original publication timestamp and Gi - The [Sim workflow maintenance guide](./maintenance-workflow.md) describes collection, the editorial queue, draft preparation, media production, and monitoring. The operational runbook and workflow exports in the editorial workspace record its live configuration and acceptance results. Keep this publishing guide and the editorial standard as the source of content and media rules. - The release editor reviews candidates weekly and checks published links and hosted media monthly. Refresh destinations when docs move and verify deep anchors manually; the audit catches missing canonical source pages during every PR. -- Keep the original slug, publication date, and RSS identity stable. Use `updated` only for a substantive correction. A future date does not schedule publication; leave the entry in draft until the intended deployment. +- Keep the original slug, publication date, and RSS identity stable. Use `updated` only for a substantive correction or expansion, not a formatting edit. A future date does not schedule publication; leave the entry in draft until the intended deployment. - If availability changes after publication, update the existing entry with its current status and a clear next step. Preserve its URL rather than deleting it or reverting it to a draft. If a slug must change, add a redirect before moving it. - Keep historical media versioned. Record the capture date, environment, demonstrated steps, and final asset URLs in the brief. Never overwrite an existing recording. Recheck playback, seeking, captions, and mobile readability after any replacement. - RSS includes the 50 latest published entries, the homepage shows 12, and the archive retains the published history. Those collections load metadata and optimized covers; full articles and recordings load on their detail pages. diff --git a/apps/sim/content/changelog/compare-workflow-deployments/index.mdx b/apps/sim/content/changelog/compare-workflow-deployments/index.mdx index e663a397b8c..826367efffd 100644 --- a/apps/sim/content/changelog/compare-workflow-deployments/index.mdx +++ b/apps/sim/content/changelog/compare-workflow-deployments/index.mdx @@ -3,7 +3,7 @@ slug: compare-workflow-deployments title: 'Compare workflow versions before you deploy' description: 'See prompt edits, added steps, and changed connections in Sim. Compare two deployments or check your draft against the live workflow.' date: '2026-10-02T06:55:11Z' -updated: '2026-10-10T01:48:00Z' +updated: '2026-10-12T21:00:16Z' authors: [waleed] tags: [Workflows] ogImage: /changelog/compare-workflow-deployments-v2.jpg @@ -22,6 +22,13 @@ release: height="605" /> -Compare any two workflow deployments, or review your draft against the live version. See prompt edits, added steps, and changed connections together so you can check exactly what will change before deploying. +Sim now shows what changed between workflow versions in a single comparison. Review prompt edits, added or removed steps, and changed connections together before updating an agent’s deployment. -Open **Compare** in deployment history or **View changes** on your draft. [Learn more about deployments](https://docs.sim.ai/workflows/deployment). +You can review two kinds of changes: + +- **Deployment against deployment:** choose two saved versions to understand what changed between releases. +- **Draft against live:** check the work in progress against the version that currently handles incoming requests. + +For example, if you revise a support agent’s instructions and add a Slack step, the comparison brings the prompt edit, new step, and connection into the same view. Use it to check a planned update or revisit the differences between earlier deployments. + +Open **Compare** in deployment history to choose versions, or **View changes** on your draft to review it against the live workflow. [Learn how workflow deployments work](https://docs.sim.ai/workflows/deployment), including version history and promoting an earlier version back to live. diff --git a/apps/sim/content/changelog/compare-workflow-deployments/production.md b/apps/sim/content/changelog/compare-workflow-deployments/production.md index 2b054aaa530..b685683435e 100644 --- a/apps/sim/content/changelog/compare-workflow-deployments/production.md +++ b/apps/sim/content/changelog/compare-workflow-deployments/production.md @@ -36,3 +36,7 @@ Email body: > Open deployment history and choose Compare to review two workflow versions. You can also review a draft against the live workflow before redeploying. See the product walkthrough and setup guide: https://www.sim.ai/changelog/compare-workflow-deployments These are drafts, not sent announcements. + +## Editorial expansion + +Expanded October 12, 2026, with supported capabilities, a practical example, and a short path to getting started. Copy was checked against the existing feature evidence and linked documentation. Original publication dates, release references, RSS identities, and reviewed media are unchanged; the article’s `updated` timestamp records this substantive copy revision. Browser and CI evidence belongs in the expansion PR. diff --git a/apps/sim/content/changelog/editorial-standard.md b/apps/sim/content/changelog/editorial-standard.md index b85f7f0d8e8..680dce42579 100644 --- a/apps/sim/content/changelog/editorial-standard.md +++ b/apps/sim/content/changelog/editorial-standard.md @@ -10,11 +10,12 @@ Routine retry fixes, loading improvements, internal refactors, and small polish Keep existing article URLs, original dates, and RSS identities when refining historical copy. Do not merge existing entries just to make a larger announcement. Preserve material version, permission, and rollout restrictions. -## Write a compact entry +## Write a useful, complete entry - Headline: name the capability or action, at most 65 characters. Avoid generic headlines such as “A better experience.” - Summary: 15–40 words for search, sharing, and RSS, naming Sim and explaining the capability in plain language. It must make sense without the image. -- Body: lead with what changed and what teams can do with it. Aim for 2–4 short sentences, usually 30–90 words, followed by a useful documentation link. There is no minimum word count; keep the body under 120 words. Use one concrete example when it adds clarity. Save setup instructions for the linked guide; do not pad a simple update into a tutorial. +- Body: lead with what changed and what teams can do with it, then add enough detail to understand the feature without opening the docs. A typical standalone story is 100–200 words, with a ceiling of 250 words and no minimum. Cover the specific capabilities, one practical example, and where to get started. Use short paragraphs or up to three capability bullets when they make the update easier to scan. A simple model addition can be shorter; a broad release can include separately scoped supporting notes. Let the evidence determine the length rather than padding to a target. +- Detail: name the relevant controls and explain meaningful behavior, such as what two versions a comparison uses or which inventory an integration can read. Include a brief starting action; leave the full setup procedure to the linked guide. Examples describe something a team can try, never an invented customer result, benchmark, or new capability. Avoid repeating the headline or summary in longer words. - Media: place the reviewed image or video immediately after the article header. Both use the shared lightbox; videos show a plain poster with playback, seeking, and zoom controls inside the viewer. Use concise alt text or an accessible action label without a visible video description. Do not add captions or prose about how the capture was made, whether a query ran, sample credentials, or what a screenshot does not prove. Keep capture provenance and review evidence in production.md. - Supporting notes: up to three related, source-backed improvements, each one sentence. Omit empty sections. Do not invent extras to fill a template. - Links: one descriptive setup/documentation link, plus an integration, model, or product link when directly relevant. Use the actual catalog slug and guide. Put links in context; avoid a wall of generic “Learn more” links. diff --git a/apps/sim/content/changelog/intune-device-inventory/index.mdx b/apps/sim/content/changelog/intune-device-inventory/index.mdx index b833f94d424..0b3d1c0fe04 100644 --- a/apps/sim/content/changelog/intune-device-inventory/index.mdx +++ b/apps/sim/content/changelog/intune-device-inventory/index.mdx @@ -3,6 +3,7 @@ slug: intune-device-inventory title: 'Bring Intune device inventory into your agents' description: 'Use Microsoft Intune in Sim to read managed devices, installed application inventory, and compliance status for IT reviews and agent follow-ups.' date: '2026-10-08T07:10:06Z' +updated: '2026-10-12T21:00:16Z' authors: [waleed] tags: [Integrations] ogImage: /changelog/intune-device-filter-v1.jpg @@ -20,6 +21,14 @@ release: height="720" /> -Your agents can now read managed devices, installed applications, and compliance status from [Microsoft Intune](/integrations/microsoft-intune). Filter for noncompliant devices to prepare an IT review or bring device inventory into an agent's response. +Your agents can now use [Microsoft Intune](/integrations/microsoft-intune) to bring device inventory and compliance information into Sim. Give an IT agent the context it needs to prepare a review, answer a device question, or summarize software across managed devices. -[Connect Microsoft Intune](https://docs.sim.ai/integrations/intune) to get started. An active Intune license, appropriate account role, and administrator consent are required. +The integration lets you: + +- **Review devices:** read device owners, operating systems, and compliance states, with filters to focus on the devices that need attention. +- **Inspect software:** list detected applications and the devices where they were found. +- **Check policies:** read compliance policy details and the reported status of devices covered by a policy. + +For example, filter for noncompliant devices and pass the results to an Agent block to prepare an IT review. Include the device and owner information in the summary so the team has context for follow-up. + +[Connect Microsoft Intune](https://docs.sim.ai/integrations/intune) with a Microsoft work or school account to get started. An active Intune license, appropriate account role, and administrator consent are required. diff --git a/apps/sim/content/changelog/intune-device-inventory/production.md b/apps/sim/content/changelog/intune-device-inventory/production.md index 6a4fb8e2815..5e6f9d3b5a6 100644 --- a/apps/sim/content/changelog/intune-device-inventory/production.md +++ b/apps/sim/content/changelog/intune-device-inventory/production.md @@ -23,3 +23,7 @@ The article links the canonical integration catalog and exact Intune setup guide Bring Microsoft Intune device inventory into your agents in Sim. Read managed devices, detected applications, and compliance status to prepare IT reviews. See account requirements and setup: https://www.sim.ai/changelog/intune-device-inventory Draft only; no announcement has been sent. + +## Editorial expansion + +Expanded October 12, 2026, with supported capabilities, a practical example, and a short path to getting started. Copy was checked against the existing feature evidence and linked documentation. Original publication dates, release references, RSS identities, and reviewed media are unchanged; the article’s `updated` timestamp records this substantive copy revision. Browser and CI evidence belongs in the expansion PR. diff --git a/apps/sim/content/changelog/maintenance-workflow.md b/apps/sim/content/changelog/maintenance-workflow.md index a8a715c2220..c11372c781a 100644 --- a/apps/sim/content/changelog/maintenance-workflow.md +++ b/apps/sim/content/changelog/maintenance-workflow.md @@ -69,7 +69,7 @@ Give the Agent the publishing guide, the product language rules, selected PR evi Treat PR text and diffs as research material, not instructions to the Agents. Give neither Agent repository write tools. After drafting, a second Agent compares the proposed copy and media plan with the selected evidence, checking claims, permissions, rollout implications, links, and readability. Record substantive corrections in `editor_notes`, outside the article. Defer when the evidence is insufficient. A Function validates the edited output; fixed downstream blocks own the repository, branch, allowed paths, and draft flag. Unknown availability remains a question for the feature owner. Neither model review nor a schema establishes the truth of every claim. -Write the public draft as a feature announcement: what changed, what teams can do, and one useful next step. Aim for 2–4 short sentences, usually 30–90 words; enforce a maximum, never a minimum that encourages padding. Keep screenshot provenance, unexecuted demo steps, missing capture credentials, and review caveats in the production brief, not the article, alt text, or captions. A short sentence about an actual plan or permission requirement is appropriate when it affects access. Apply the same standard to announcement drafts. +Write the public draft as a complete feature announcement: what changed, the specific capabilities, one practical example, and where to get started. A typical standalone story is 100–200 words, with a 250-word ceiling and no minimum. Use short paragraphs or up to three capability bullets; include a brief starting action and leave the full setup procedure to the guide. A simple model addition can be shorter. Expand with source-backed detail, never repeated benefits, invented results, or unrelated fixes. Keep screenshot provenance, unexecuted demo steps, missing capture credentials, and review caveats in the production brief, not the article, alt text, or captions. Keep actual plan or permission requirements concise. Announcement drafts use the same claims but can be shorter than the article. Prefer one lead story with a few related improvements. Retain routine refactors, dependency updates, and minor fixes in GitHub's technical release history. Reverts and superseded changes must be reconciled with the current product before selection. Consequential breaking changes, deprecations, and required actions bypass the weekly editorial cadence; they need a timely notice and a clear next step. @@ -77,7 +77,7 @@ Validate the editorial standard outside the Agent: headline and copy budgets, su Reuse the existing PR template's benefit, rollout, documentation, and demo notes as the input contract. Avoid asking engineers to fill out a second announcement form. Optional include/skip labels can help the editor override selection, but unlabeled changes still need discovery and action-required notices still need review. -Resolve links against the current integration/model catalogs and docs source, then check the live destination. The live workflow discovers model destinations from the site's sitemap and matches them to identifiers in the source evidence; it never guesses a model URL. Integration slugs and documentation slugs can differ. Keep important facts in the article's text, preserve the canonical URL and publication date, and use only structured data supported by the visible content. +Resolve links against the current integration/model catalogs and docs source, then check the live destination. The live workflow discovers model destinations from the site's sitemap and provider directories in the source evidence, then verifies candidates before passing them to the editors. This includes provider catalogs omitted from the sitemap. Integration slugs and documentation slugs can differ. Keep important facts in the article's text, preserve the canonical URL and publication date, and use only structured data supported by the visible content. The first draft PR can contain only `production.md`: proposed article text, source references, unresolved questions, shot list, and announcement drafts. Add `index.mdx` with `draft: true` once a real cover exists. The content audit requires a real local cover even for drafts; an invented filename or unrelated placeholder would create a failing PR. Keep secrets, unpublished strategy, and private operational evidence out of both files: non-rendered briefs are still public in this repository. diff --git a/apps/sim/content/changelog/nebius-models-for-agents/index.mdx b/apps/sim/content/changelog/nebius-models-for-agents/index.mdx index bfef177b3c3..021b8a7e429 100644 --- a/apps/sim/content/changelog/nebius-models-for-agents/index.mdx +++ b/apps/sim/content/changelog/nebius-models-for-agents/index.mdx @@ -3,6 +3,7 @@ slug: nebius-models-for-agents title: 'Use Nebius Token Factory models in your agents' description: 'Run DeepSeek, Kimi, Qwen, and other open models in Sim’s Agent block using your own Nebius Token Factory API key.' date: '2026-10-12T17:00:00Z' +updated: '2026-10-12T21:00:16Z' authors: [waleed] tags: [Models] ogImage: /changelog/nebius-model-picker-v1.jpg @@ -22,6 +23,8 @@ release: /> -[Nebius Token Factory](/models/nebius) is now available in the Agent block. Choose from open models including DeepSeek, Kimi, and Qwen, and use them with your existing prompts and connected tools. +[Nebius Token Factory](/models/nebius) is now available in Sim’s Agent block. Choose from open models including DeepSeek, Kimi, and Qwen, and run them through your Nebius account alongside the other model providers you use in Sim. -Bring your own Nebius API key to get started. [Set up Nebius in an Agent block](https://docs.sim.ai/workflows/blocks/agent). +Try a Nebius model in an agent that summarizes support tickets, extracts details from incoming requests, or drafts a response using connected tools. You can keep the block’s existing prompts and connections while changing the model, then run representative inputs to see how it handles your task. Check the selected model’s supported features when using image inputs or structured outputs. + +To get started, bring your own Nebius API key and search for **nebius** in the Agent block’s model picker. On Sim Cloud, a workspace admin adds the key under **Workspace settings → BYOK → Nebius**. Self-hosted teams provide it in the block’s **API Key** field. [Set up Nebius in an Agent block](https://docs.sim.ai/workflows/blocks/agent). diff --git a/apps/sim/content/changelog/nebius-models-for-agents/production.md b/apps/sim/content/changelog/nebius-models-for-agents/production.md index 172b6a1c472..c103a9d78d5 100644 --- a/apps/sim/content/changelog/nebius-models-for-agents/production.md +++ b/apps/sim/content/changelog/nebius-models-for-agents/production.md @@ -1,6 +1,6 @@ # Nebius Token Factory: production record -Status: editorial, feature, and media review completed October 12, 2026. PR #8924 is merged to staging; hosted deployment verification remains pending. Only `index.mdx` is rendered on the website. +Status: editorial, feature, and media review completed October 12, 2026. PR #8924 and its production-record follow-up are merged to staging; hosted article, media, links, discovery, and lightbox verification passed. Production publication remains subject to the publication monitor. Only `index.mdx` is rendered on the website. ## Story and evidence @@ -47,3 +47,7 @@ Email body: > Nebius Token Factory is available in Sim's Agent block. Choose from open models including DeepSeek, Kimi, and Qwen, and use them with your existing prompts and connected tools. Bring your own Nebius API key to get started: https://www.sim.ai/changelog/nebius-models-for-agents These are drafts. Distribute only after the production article and media are verified. + +## Editorial expansion + +Expanded October 12, 2026, with supported capabilities, a practical example, and a short path to getting started. Copy was checked against the existing feature evidence and linked documentation. Original publication dates, release references, RSS identities, and reviewed media are unchanged; the article’s `updated` timestamp records this substantive copy revision. Browser and CI evidence belongs in the expansion PR. diff --git a/apps/sim/content/changelog/new-models-for-agents/index.mdx b/apps/sim/content/changelog/new-models-for-agents/index.mdx index 7d9687d5399..c0f626ebf82 100644 --- a/apps/sim/content/changelog/new-models-for-agents/index.mdx +++ b/apps/sim/content/changelog/new-models-for-agents/index.mdx @@ -3,6 +3,7 @@ slug: new-models-for-agents title: 'GPT-6.1 Sol, Haiku 5.5, and Grok 4.7 for your agents' description: 'Choose GPT-6.1 Sol, Claude Haiku 5.5, or Grok 4.7 in Sim’s Agent block and use them with your existing prompts and integrations.' date: '2026-10-08T07:10:06Z' +updated: '2026-10-12T21:00:16Z' authors: [waleed] tags: [Models] ogImage: /changelog/agent-model-picker-v1.jpg @@ -20,6 +21,8 @@ release: height="720" /> -[GPT-6.1 Sol](/models/openai/gpt-6-1-sol), [Claude Haiku 5.5](/models/anthropic/claude-haiku-5-5), and [Grok 4.7](/models/xai/grok-4-7) are now available in the Agent block. Switch models while keeping your existing prompts and connected integrations. +[GPT-6.1 Sol](/models/openai/gpt-6-1-sol), [Claude Haiku 5.5](/models/anthropic/claude-haiku-5-5), and [Grok 4.7](/models/xai/grok-4-7) are now available in Sim’s Agent block. Select any of them in an existing agent while keeping your prompts, connected integrations, and workflow structure. -Choose a model from the picker to try it in your agent. [Learn more about Agent blocks](https://docs.sim.ai/workflows/blocks/agent). +This makes it easier to try a new model on the work your agent already handles. For a support agent, run the same sample request with each model and review the response, tool choices, and output format. For an agent that processes documents, try a representative input before changing the model used by a deployed workflow. + +Open the Agent block, choose the model in **Model**, and review its settings before running your draft. Available settings and supported input types depend on the model. The linked model pages explain each option; the [Agent block guide](https://docs.sim.ai/workflows/blocks/agent) covers connecting a provider, configuring messages, and using the response in later steps. diff --git a/apps/sim/content/changelog/new-models-for-agents/production.md b/apps/sim/content/changelog/new-models-for-agents/production.md index b0faa121072..1d06372aad5 100644 --- a/apps/sim/content/changelog/new-models-for-agents/production.md +++ b/apps/sim/content/changelog/new-models-for-agents/production.md @@ -23,3 +23,7 @@ The release timestamp is preserved as the feature's historical release date. Thi Choose GPT-6.1 Sol, Claude Haiku 5.5, or Grok 4.7 for an Agent block in Sim. Keep your prompts and integrations, then review the model settings and try your sample input. Setup: https://www.sim.ai/changelog/new-models-for-agents Draft only; no announcement has been sent. + +## Editorial expansion + +Expanded October 12, 2026, with supported capabilities, a practical example, and a short path to getting started. Copy was checked against the existing feature evidence and linked documentation. Original publication dates, release references, RSS identities, and reviewed media are unchanged; the article’s `updated` timestamp records this substantive copy revision. Browser and CI evidence belongs in the expansion PR. diff --git a/apps/sim/content/changelog/power-bi-for-agents/index.mdx b/apps/sim/content/changelog/power-bi-for-agents/index.mdx index 37064521980..e3a7dd28935 100644 --- a/apps/sim/content/changelog/power-bi-for-agents/index.mdx +++ b/apps/sim/content/changelog/power-bi-for-agents/index.mdx @@ -3,6 +3,7 @@ slug: power-bi-for-agents title: 'Bring Power BI data into your agents' description: 'Query Power BI data from Sim and pass the results to an agent for a briefing or follow-up. Browse reports and manage refreshes in the same workflow.' date: '2026-10-03T04:32:55Z' +updated: '2026-10-12T21:00:16Z' authors: [waleed] tags: [Integrations] ogImage: /changelog/power-bi-query-v1.jpg @@ -20,6 +21,14 @@ release: height="900" /> -Your agents can now query [Power BI](/integrations/power-bi) data, browse reports, and manage model refreshes. Pull revenue by region into a sales briefing or check refresh status before using the latest data. +Your agents can now query [Power BI](/integrations/power-bi) from Sim and use the results in a briefing, report, or follow-up. Connect business data that already lives in Power BI to the prompts and integrations in your agent. -[Connect Power BI](https://docs.sim.ai/integrations/powerbi) to get started. Queries require Read and Build permissions and your tenant's Execute Queries setting. +The integration supports three parts of that process: + +- **Find the right data:** browse accessible workspaces, reports, and semantic models, the datasets behind your Power BI reports. +- **Query a model:** use DAX, Power BI’s query language, to return the rows your agent needs. +- **Manage refreshes:** request a model refresh and check its history to see the reported status. + +For example, query revenue by region, pass the rows to an Agent block for a sales briefing, and send the summary to Slack. + +[Connect Power BI](https://docs.sim.ai/integrations/powerbi) with your organization’s Microsoft account. Queries require workspace access, Read and Build permissions, and the **Execute Queries** setting enabled in Power BI. The guide covers permissions for each action. diff --git a/apps/sim/content/changelog/power-bi-for-agents/production.md b/apps/sim/content/changelog/power-bi-for-agents/production.md index cb37224b2a5..efcaee40364 100644 --- a/apps/sim/content/changelog/power-bi-for-agents/production.md +++ b/apps/sim/content/changelog/power-bi-for-agents/production.md @@ -14,7 +14,7 @@ The entry links to `/integrations/power-bi` and the matching docs guide at `/int Captured October 7, 2026, from the actual local self-hosted app based on staging commit `684b228623`, using a dedicated sample workspace. Asset: `/changelog/power-bi-query-v1.jpg`, 1440×900. -The screenshot shows the Power BI block and a synthetic DAX query using sample sales table and column names. The account, workspace, and model selectors are intentionally unconnected. No Microsoft account was connected and no query or refresh was executed. The article explicitly describes a configuration example, not a successful provider call. Do not add a results screen without a real authorized connection and a verified run. +The screenshot shows the Power BI block and a synthetic DAX query using sample sales table and column names. The account, workspace, and model selectors are intentionally unconnected. No Microsoft account was connected and no query or refresh was executed. The article explains supported actions and a suggested use case; the image depicts configuration. Do not add a results screen without a real authorized connection and a verified run. The sample demonstrates where the query is configured. Actual table and column names must match the reader's model. The setup guide describes organizational accounts, delegated connection requirements, permission limits, and unsupported actions. @@ -33,3 +33,7 @@ Email body: > Sim's Power BI integration can query semantic models, inspect reports, and request refreshes. Use the returned rows in a briefing or follow-up. See the configuration example and Microsoft connection requirements: https://www.sim.ai/changelog/power-bi-for-agents These are drafts, not sent announcements. + +## Editorial expansion + +Expanded October 12, 2026, with supported capabilities, a practical example, and a short path to getting started. Copy was checked against the existing feature evidence and linked documentation. Original publication dates, release references, RSS identities, and reviewed media are unchanged; the article’s `updated` timestamp records this substantive copy revision. Browser and CI evidence belongs in the expansion PR. diff --git a/apps/sim/content/changelog/review-fork-changes/index.mdx b/apps/sim/content/changelog/review-fork-changes/index.mdx index 5b790808455..53865264c83 100644 --- a/apps/sim/content/changelog/review-fork-changes/index.mdx +++ b/apps/sim/content/changelog/review-fork-changes/index.mdx @@ -3,6 +3,7 @@ slug: review-fork-changes title: 'Review fork changes before syncing' description: 'See what changed in a source workflow before syncing a workspace fork in Sim. Review prompts, settings, and steps against the last successful sync.' date: '2026-10-03T04:32:55Z' +updated: '2026-10-12T21:00:16Z' authors: [waleed] tags: [Workspaces, Enterprise] ogImage: /changelog/review-fork-changes-v1.jpg @@ -22,6 +23,10 @@ release: caption="Review source workflow changes before syncing a fork" /> -Review changes to a source workflow before syncing them into a workspace fork. Compare prompts, settings, and steps against the last successful sync, with a separate history for each fork and sync direction. +Sim now lets you review changes to a source workflow before syncing them into a workspace fork. The **Last Sync → Now** comparison shows what changed in the source since it was last successfully synced, including edits to prompts, settings, and workflow steps. -Available to workspace admins with Forks enabled on Sim Cloud Enterprise or self-hosted deployments. [Learn more about workspace forks](https://docs.sim.ai/platform/enterprise/forks). +If you maintain a shared agent across several workspaces, use the comparison to understand an update before bringing it into a fork. For example, check a revised renewal-reminder interval and new settings together before syncing. Each fork and sync direction keeps its own baseline, so the review reflects that particular relationship. + +Open the fork’s mapping settings, choose the sync direction, and select **Compare** from a deployed workflow’s menu. Comparison becomes available after a successful sync establishes a baseline; the source snapshots must still be available. + +Available with Forks enabled on Sim Cloud Enterprise or self-hosted deployments. Managing a sync requires admin access to both workspaces. [Learn more about workspace forks](https://docs.sim.ai/platform/enterprise/forks). diff --git a/apps/sim/content/changelog/review-fork-changes/production.md b/apps/sim/content/changelog/review-fork-changes/production.md index 72eafce3bd8..dbd107a990a 100644 --- a/apps/sim/content/changelog/review-fork-changes/production.md +++ b/apps/sim/content/changelog/review-fork-changes/production.md @@ -39,3 +39,7 @@ Email body: > Open your fork's mapping settings and choose Compare from a deployed workflow's menu. Inspect source changes since the last successful sync before updating the fork. Availability and demo: https://www.sim.ai/changelog/review-fork-changes These are drafts, not sent announcements. + +## Editorial expansion + +Expanded October 12, 2026, with supported capabilities, a practical example, and a short path to getting started. Copy was checked against the existing feature evidence and linked documentation. Original publication dates, release references, RSS identities, and reviewed media are unchanged; the article’s `updated` timestamp records this substantive copy revision. Browser and CI evidence belongs in the expansion PR. From 655e9c3097ad0c304d6d6560695c7cbb8d19b231 Mon Sep 17 00:00:00 2001 From: Waleed Latif Date: Mon, 12 Oct 2026 14:16:40 -0700 Subject: [PATCH 2/2] improvement(changelog): cover release changes without padding --- apps/sim/content/changelog/README.md | 2 +- .../compare-workflow-deployments/index.mdx | 12 +++++------- .../compare-workflow-deployments/production.md | 6 ++++-- apps/sim/content/changelog/editorial-standard.md | 7 ++++--- .../changelog/intune-device-inventory/index.mdx | 13 +++++-------- .../changelog/intune-device-inventory/production.md | 6 ++++-- apps/sim/content/changelog/maintenance-workflow.md | 4 ++-- .../changelog/nebius-models-for-agents/index.mdx | 6 ++---- .../nebius-models-for-agents/production.md | 4 ++-- .../changelog/new-models-for-agents/index.mdx | 6 +++--- .../changelog/new-models-for-agents/production.md | 6 ++++-- .../content/changelog/power-bi-for-agents/index.mdx | 13 +++++-------- .../changelog/power-bi-for-agents/production.md | 6 ++++-- .../content/changelog/review-fork-changes/index.mdx | 6 ++---- .../changelog/review-fork-changes/production.md | 4 ++-- 15 files changed, 49 insertions(+), 52 deletions(-) diff --git a/apps/sim/content/changelog/README.md b/apps/sim/content/changelog/README.md index cf151793f2d..5b52b7c6416 100644 --- a/apps/sim/content/changelog/README.md +++ b/apps/sim/content/changelog/README.md @@ -107,7 +107,7 @@ release: captionsSrc="https://nnjgp7vypgx4myuq.public.blob.vercel-storage.com/changelog/demo-v1.vtt" /> -Explain where to find the feature and give one concrete example. +Explain the behavior that changed and link to the relevant guide. Add selected release changes only when they have verified source and release evidence. ### Improvements diff --git a/apps/sim/content/changelog/compare-workflow-deployments/index.mdx b/apps/sim/content/changelog/compare-workflow-deployments/index.mdx index 826367efffd..6827e86969c 100644 --- a/apps/sim/content/changelog/compare-workflow-deployments/index.mdx +++ b/apps/sim/content/changelog/compare-workflow-deployments/index.mdx @@ -22,13 +22,11 @@ release: height="605" /> -Sim now shows what changed between workflow versions in a single comparison. Review prompt edits, added or removed steps, and changed connections together before updating an agent’s deployment. +Compare two saved workflow deployments, or check your draft against the live version. Sim shows prompt and setting edits, added or removed steps, and changed connections in the same view. -You can review two kinds of changes: +Open **Compare** in deployment history or **View changes** on your draft. [Learn more about deployments](https://docs.sim.ai/workflows/deployment). -- **Deployment against deployment:** choose two saved versions to understand what changed between releases. -- **Draft against live:** check the work in progress against the version that currently handles incoming requests. +### Also in v0.9.10 -For example, if you revise a support agent’s instructions and add a Slack step, the comparison brings the prompt edit, new step, and connection into the same view. Use it to check a planned update or revisit the differences between earlier deployments. - -Open **Compare** in deployment history to choose versions, or **View changes** on your draft to review it against the live workflow. [Learn how workflow deployments work](https://docs.sim.ai/workflows/deployment), including version history and promoting an earlier version back to live. +- **Readable file diffs:** Markdown files render additions, removals, and word-level changes with long unchanged sections collapsed. [Open the file editor](https://docs.sim.ai/files/editor). +- **Remembered panel widths:** Chat restores your resource panel width when you reload, return from settings, or collapse and reopen the panel. diff --git a/apps/sim/content/changelog/compare-workflow-deployments/production.md b/apps/sim/content/changelog/compare-workflow-deployments/production.md index b685683435e..e104b9d5541 100644 --- a/apps/sim/content/changelog/compare-workflow-deployments/production.md +++ b/apps/sim/content/changelog/compare-workflow-deployments/production.md @@ -37,6 +37,8 @@ Email body: These are drafts, not sent announcements. -## Editorial expansion +## Editorial revision -Expanded October 12, 2026, with supported capabilities, a practical example, and a short path to getting started. Copy was checked against the existing feature evidence and linked documentation. Original publication dates, release references, RSS identities, and reviewed media are unchanged; the article’s `updated` timestamp records this substantive copy revision. Browser and CI evidence belongs in the expansion PR. +Revised October 12, 2026, to clarify supported behavior and include selected changes from the same technical release where useful. Every public sentence describes a capability, a meaningful change, or necessary access information. Original dates, release references, RSS identities, and reviewed media are preserved. The `updated` timestamp records the substantive revision. Browser and CI evidence belongs in the revision PR. + +Additional v0.9.10 coverage: [file diff rendering, #8543](https://github.com/simstudioai/sim/pull/8543) and [remembered resource-panel widths, #8531](https://github.com/simstudioai/sim/pull/8531). The technical release includes both; source and current documentation were reviewed. diff --git a/apps/sim/content/changelog/editorial-standard.md b/apps/sim/content/changelog/editorial-standard.md index 680dce42579..1a41a3d4b55 100644 --- a/apps/sim/content/changelog/editorial-standard.md +++ b/apps/sim/content/changelog/editorial-standard.md @@ -14,10 +14,11 @@ Keep existing article URLs, original dates, and RSS identities when refining his - Headline: name the capability or action, at most 65 characters. Avoid generic headlines such as “A better experience.” - Summary: 15–40 words for search, sharing, and RSS, naming Sim and explaining the capability in plain language. It must make sense without the image. -- Body: lead with what changed and what teams can do with it, then add enough detail to understand the feature without opening the docs. A typical standalone story is 100–200 words, with a ceiling of 250 words and no minimum. Cover the specific capabilities, one practical example, and where to get started. Use short paragraphs or up to three capability bullets when they make the update easier to scan. A simple model addition can be shorter; a broad release can include separately scoped supporting notes. Let the evidence determine the length rather than padding to a target. -- Detail: name the relevant controls and explain meaningful behavior, such as what two versions a comparison uses or which inventory an integration can read. Include a brief starting action; leave the full setup procedure to the linked guide. Examples describe something a team can try, never an invented customer result, benchmark, or new capability. Avoid repeating the headline or summary in longer words. +- Body: say what changed and explain the behavior a reader needs to understand it. There is no target length or minimum; keep the body under 250 words. Do not expand a short announcement with generic use cases, repeated benefits, or a setup tutorial. Name specific capabilities or controls only when they add information. +- Release coverage: inspect the technical release for other meaningful user-facing changes. Include up to three concise notes under “Also in vX.Y.Z” when source evidence establishes that they belong to the same release. Group them sensibly, avoid repeating notes across articles from that release, and link to the relevant guide or product page. A focused feature announcement can remain short. Do not infer release membership from merge timing or add unrelated changes just to make an entry longer. +- Detail: every sentence must contribute a product change, useful behavioral detail, or necessary access information. Examples are optional and earn their place only when they make an unfamiliar change easier to understand. Leave full setup instructions and model inventories to the linked docs and catalogs. Never invent customer results or benchmarks. - Media: place the reviewed image or video immediately after the article header. Both use the shared lightbox; videos show a plain poster with playback, seeking, and zoom controls inside the viewer. Use concise alt text or an accessible action label without a visible video description. Do not add captions or prose about how the capture was made, whether a query ran, sample credentials, or what a screenshot does not prove. Keep capture provenance and review evidence in production.md. -- Supporting notes: up to three related, source-backed improvements, each one sentence. Omit empty sections. Do not invent extras to fill a template. +- Supporting notes: one sentence per change, up to three per article. Omit empty sections and technical maintenance with no meaningful user impact. Keep each note’s source and release evidence in production.md. The lead image need not illustrate every supporting note. - Links: one descriptive setup/documentation link, plus an integration, model, or product link when directly relevant. Use the actual catalog slug and guide. Put links in context; avoid a wall of generic “Learn more” links. - Availability: keep restrictions that affect whether someone can use the feature, such as a required plan or administrator role, in one concise sentence. Link to documentation for setup details. Keep unverified rollout questions, source analysis, capture instructions, and approval checkboxes in production.md. Never substitute a capture disclaimer for verifying a claim. diff --git a/apps/sim/content/changelog/intune-device-inventory/index.mdx b/apps/sim/content/changelog/intune-device-inventory/index.mdx index 0b3d1c0fe04..c90bbd7998a 100644 --- a/apps/sim/content/changelog/intune-device-inventory/index.mdx +++ b/apps/sim/content/changelog/intune-device-inventory/index.mdx @@ -21,14 +21,11 @@ release: height="720" /> -Your agents can now use [Microsoft Intune](/integrations/microsoft-intune) to bring device inventory and compliance information into Sim. Give an IT agent the context it needs to prepare a review, answer a device question, or summarize software across managed devices. +Your agents can now read device inventory and compliance information from [Microsoft Intune](/integrations/microsoft-intune). Filter devices by compliance state, inspect owners and operating systems, list detected applications, and read compliance policies with their device status. -The integration lets you: +[Connect Microsoft Intune](https://docs.sim.ai/integrations/intune) with a Microsoft work or school account. An active Intune license, appropriate account role, and administrator consent are required. -- **Review devices:** read device owners, operating systems, and compliance states, with filters to focus on the devices that need attention. -- **Inspect software:** list detected applications and the devices where they were found. -- **Check policies:** read compliance policy details and the reported status of devices covered by a policy. +### Also in v0.9.15 -For example, filter for noncompliant devices and pass the results to an Agent block to prepare an IT review. Include the device and owner information in the summary so the team has context for follow-up. - -[Connect Microsoft Intune](https://docs.sim.ai/integrations/intune) with a Microsoft work or school account to get started. An active Intune license, appropriate account role, and administrator consent are required. +- **Plane:** Manage projects and work items, start workflows from webhook events, and sync project knowledge with the [Plane integration](https://docs.sim.ai/integrations/plane), including supported self-hosted instances. +- **Buffer:** Read channel details, post metrics, and daily posting limits. Caption edits can preserve the existing posting schedule. [See Buffer’s actions](https://docs.sim.ai/integrations/buffer). diff --git a/apps/sim/content/changelog/intune-device-inventory/production.md b/apps/sim/content/changelog/intune-device-inventory/production.md index 5e6f9d3b5a6..022f69fc133 100644 --- a/apps/sim/content/changelog/intune-device-inventory/production.md +++ b/apps/sim/content/changelog/intune-device-inventory/production.md @@ -24,6 +24,8 @@ Bring Microsoft Intune device inventory into your agents in Sim. Read managed de Draft only; no announcement has been sent. -## Editorial expansion +## Editorial revision -Expanded October 12, 2026, with supported capabilities, a practical example, and a short path to getting started. Copy was checked against the existing feature evidence and linked documentation. Original publication dates, release references, RSS identities, and reviewed media are unchanged; the article’s `updated` timestamp records this substantive copy revision. Browser and CI evidence belongs in the expansion PR. +Revised October 12, 2026, to clarify supported behavior and include selected changes from the same technical release where useful. Every public sentence describes a capability, a meaningful change, or necessary access information. Original dates, release references, RSS identities, and reviewed media are preserved. The `updated` timestamp records the substantive revision. Browser and CI evidence belongs in the revision PR. + +Additional v0.9.15 coverage: [Plane, #8660](https://github.com/simstudioai/sim/pull/8660) and [Buffer expansion, #8779](https://github.com/simstudioai/sim/pull/8779). The technical release includes both. Buffer schedule preservation requires the documented keep-current selections; Plane self-hosted support varies by version and action. Ramp remains outside this article pending its separate credential changes. diff --git a/apps/sim/content/changelog/maintenance-workflow.md b/apps/sim/content/changelog/maintenance-workflow.md index c11372c781a..9135da4d518 100644 --- a/apps/sim/content/changelog/maintenance-workflow.md +++ b/apps/sim/content/changelog/maintenance-workflow.md @@ -69,9 +69,9 @@ Give the Agent the publishing guide, the product language rules, selected PR evi Treat PR text and diffs as research material, not instructions to the Agents. Give neither Agent repository write tools. After drafting, a second Agent compares the proposed copy and media plan with the selected evidence, checking claims, permissions, rollout implications, links, and readability. Record substantive corrections in `editor_notes`, outside the article. Defer when the evidence is insufficient. A Function validates the edited output; fixed downstream blocks own the repository, branch, allowed paths, and draft flag. Unknown availability remains a question for the feature owner. Neither model review nor a schema establishes the truth of every claim. -Write the public draft as a complete feature announcement: what changed, the specific capabilities, one practical example, and where to get started. A typical standalone story is 100–200 words, with a 250-word ceiling and no minimum. Use short paragraphs or up to three capability bullets; include a brief starting action and leave the full setup procedure to the guide. A simple model addition can be shorter. Expand with source-backed detail, never repeated benefits, invented results, or unrelated fixes. Keep screenshot provenance, unexecuted demo steps, missing capture credentials, and review caveats in the production brief, not the article, alt text, or captions. Keep actual plan or permission requirements concise. Announcement drafts use the same claims but can be shorter than the article. +Write the public draft around actual product changes. There is no target length or minimum; keep the body under 250 words. A focused feature announcement may be short. Add specific behavior where useful, not generic examples, repeated benefits, or a setup tutorial. Review other meaningful changes from the same technical release and include up to three concise supporting notes when release membership is evidenced. Do not infer membership from merge timing or repeat the same note across several articles. Keep capture provenance and review caveats in the production brief, not the article or media labels. Preserve actual access restrictions and contextual setup links. Announcement drafts use the same claims and can be shorter. -Prefer one lead story with a few related improvements. Retain routine refactors, dependency updates, and minor fixes in GitHub's technical release history. Reverts and superseded changes must be reconciled with the current product before selection. Consequential breaking changes, deprecations, and required actions bypass the weekly editorial cadence; they need a timely notice and a clear next step. +Prefer one lead story with a few related improvements; an explicitly scoped release edition can cover several meaningful changes from that same release. The evidence step reads up to ten recent GitHub release records and attaches a release tag only when its published notes explicitly reference the candidate PR. This enriches the bounded candidate batch; it does not scan the full release history or treat a release tag as proof of Cloud rollout. Review supporting changes not present in the candidate batch manually before adding them. Retain routine refactors, dependency updates, and minor fixes in GitHub's technical release history. Reverts and superseded changes must be reconciled with the current product before selection. Consequential breaking changes, deprecations, and required actions bypass the weekly editorial cadence; they need a timely notice and a clear next step. Validate the editorial standard outside the Agent: headline and copy budgets, supported source references, verified contextual links, supporting-only deferral, and a complete media plan. Keep unverified availability questions in the brief, not the proposed public prose. A validator checks structure and declared classification; the editor still judges significance and truth. Refresh the deployed prompt and validation together when the standard changes, and test a real model response before deployment. diff --git a/apps/sim/content/changelog/nebius-models-for-agents/index.mdx b/apps/sim/content/changelog/nebius-models-for-agents/index.mdx index 021b8a7e429..d448f05f63e 100644 --- a/apps/sim/content/changelog/nebius-models-for-agents/index.mdx +++ b/apps/sim/content/changelog/nebius-models-for-agents/index.mdx @@ -23,8 +23,6 @@ release: /> -[Nebius Token Factory](/models/nebius) is now available in Sim’s Agent block. Choose from open models including DeepSeek, Kimi, and Qwen, and run them through your Nebius account alongside the other model providers you use in Sim. +[Nebius Token Factory](/models/nebius) is now available in Sim’s Agent block. Choose from open models including DeepSeek, Kimi, and Qwen, and use them with your existing prompts and connected tools. Tool use, image inputs, and structured outputs depend on the selected model. -Try a Nebius model in an agent that summarizes support tickets, extracts details from incoming requests, or drafts a response using connected tools. You can keep the block’s existing prompts and connections while changing the model, then run representative inputs to see how it handles your task. Check the selected model’s supported features when using image inputs or structured outputs. - -To get started, bring your own Nebius API key and search for **nebius** in the Agent block’s model picker. On Sim Cloud, a workspace admin adds the key under **Workspace settings → BYOK → Nebius**. Self-hosted teams provide it in the block’s **API Key** field. [Set up Nebius in an Agent block](https://docs.sim.ai/workflows/blocks/agent). +Bring your own Nebius API key. On Sim Cloud, a workspace admin adds it under **Workspace settings → BYOK → Nebius**; self-hosted users provide it in the Agent block’s **API Key** field. [Set up Nebius in an Agent block](https://docs.sim.ai/workflows/blocks/agent). diff --git a/apps/sim/content/changelog/nebius-models-for-agents/production.md b/apps/sim/content/changelog/nebius-models-for-agents/production.md index c103a9d78d5..780581c4173 100644 --- a/apps/sim/content/changelog/nebius-models-for-agents/production.md +++ b/apps/sim/content/changelog/nebius-models-for-agents/production.md @@ -48,6 +48,6 @@ Email body: These are drafts. Distribute only after the production article and media are verified. -## Editorial expansion +## Editorial revision -Expanded October 12, 2026, with supported capabilities, a practical example, and a short path to getting started. Copy was checked against the existing feature evidence and linked documentation. Original publication dates, release references, RSS identities, and reviewed media are unchanged; the article’s `updated` timestamp records this substantive copy revision. Browser and CI evidence belongs in the expansion PR. +Revised October 12, 2026, to clarify supported behavior and include selected changes from the same technical release where useful. Every public sentence describes a capability, a meaningful change, or necessary access information. Original dates, release references, RSS identities, and reviewed media are preserved. The `updated` timestamp records the substantive revision. Browser and CI evidence belongs in the revision PR. diff --git a/apps/sim/content/changelog/new-models-for-agents/index.mdx b/apps/sim/content/changelog/new-models-for-agents/index.mdx index c0f626ebf82..8d6c1b45989 100644 --- a/apps/sim/content/changelog/new-models-for-agents/index.mdx +++ b/apps/sim/content/changelog/new-models-for-agents/index.mdx @@ -21,8 +21,8 @@ release: height="720" /> -[GPT-6.1 Sol](/models/openai/gpt-6-1-sol), [Claude Haiku 5.5](/models/anthropic/claude-haiku-5-5), and [Grok 4.7](/models/xai/grok-4-7) are now available in Sim’s Agent block. Select any of them in an existing agent while keeping your prompts, connected integrations, and workflow structure. +[GPT-6.1 Sol](/models/openai/gpt-6-1-sol), [Claude Haiku 5.5](/models/anthropic/claude-haiku-5-5), and [Grok 4.7](/models/xai/grok-4-7) are now available in Sim’s Agent block. Switch models while keeping your prompts, connected integrations, and workflow structure. [Configure an Agent block](https://docs.sim.ai/workflows/blocks/agent). -This makes it easier to try a new model on the work your agent already handles. For a support agent, run the same sample request with each model and review the response, tool choices, and output format. For an agent that processes documents, try a representative input before changing the model used by a deployed workflow. +### Also in v0.9.15 -Open the Agent block, choose the model in **Model**, and review its settings before running your draft. Available settings and supported input types depend on the model. The linked model pages explain each option; the [Agent block guide](https://docs.sim.ai/workflows/blocks/agent) covers connecting a provider, configuring messages, and using the response in later steps. +- **Agent defaults:** Organization admins can choose a default model in a permission group. Newly created Agent blocks use that allowed default; explicitly selected models stay as they are. Available with [permission groups](https://docs.sim.ai/platform/enterprise/access-control) on Sim Cloud Enterprise and configured self-hosted deployments. diff --git a/apps/sim/content/changelog/new-models-for-agents/production.md b/apps/sim/content/changelog/new-models-for-agents/production.md index 1d06372aad5..da639ddc363 100644 --- a/apps/sim/content/changelog/new-models-for-agents/production.md +++ b/apps/sim/content/changelog/new-models-for-agents/production.md @@ -24,6 +24,8 @@ Choose GPT-6.1 Sol, Claude Haiku 5.5, or Grok 4.7 for an Agent block in Sim. Kee Draft only; no announcement has been sent. -## Editorial expansion +## Editorial revision -Expanded October 12, 2026, with supported capabilities, a practical example, and a short path to getting started. Copy was checked against the existing feature evidence and linked documentation. Original publication dates, release references, RSS identities, and reviewed media are unchanged; the article’s `updated` timestamp records this substantive copy revision. Browser and CI evidence belongs in the expansion PR. +Revised October 12, 2026, to clarify supported behavior and include selected changes from the same technical release where useful. Every public sentence describes a capability, a meaningful change, or necessary access information. Original dates, release references, RSS identities, and reviewed media are preserved. The `updated` timestamp records the substantive revision. Browser and CI evidence belongs in the revision PR. + +Additional v0.9.15 coverage: [permission-group Agent defaults, #8771](https://github.com/simstudioai/sim/pull/8771). The technical release includes the change. Access remains governed by the existing Enterprise entitlement or self-hosted configuration; explicit model choices are preserved. diff --git a/apps/sim/content/changelog/power-bi-for-agents/index.mdx b/apps/sim/content/changelog/power-bi-for-agents/index.mdx index e3a7dd28935..ee05900a42d 100644 --- a/apps/sim/content/changelog/power-bi-for-agents/index.mdx +++ b/apps/sim/content/changelog/power-bi-for-agents/index.mdx @@ -21,14 +21,11 @@ release: height="900" /> -Your agents can now query [Power BI](/integrations/power-bi) from Sim and use the results in a briefing, report, or follow-up. Connect business data that already lives in Power BI to the prompts and integrations in your agent. +Your agents can now query [Power BI](/integrations/power-bi) data, browse reports and semantic models, and manage model refreshes. Use DAX, Power BI’s query language, to pull the rows your agent needs. Refresh history lets you check the status of a requested refresh. -The integration supports three parts of that process: +[Connect Power BI](https://docs.sim.ai/integrations/powerbi) with your organization’s Microsoft account. Queries require workspace access, Read and Build permissions, and the **Execute Queries** setting enabled in Power BI. -- **Find the right data:** browse accessible workspaces, reports, and semantic models, the datasets behind your Power BI reports. -- **Query a model:** use DAX, Power BI’s query language, to return the rows your agent needs. -- **Manage refreshes:** request a model refresh and check its history to see the reported status. +### Also in v0.9.12 -For example, query revenue by region, pass the rows to an Agent block for a sales briefing, and send the summary to Slack. - -[Connect Power BI](https://docs.sim.ai/integrations/powerbi) with your organization’s Microsoft account. Queries require workspace access, Read and Build permissions, and the **Execute Queries** setting enabled in Power BI. The guide covers permissions for each action. +- **You.com:** Search the web, read pages, get cited answers, and run research from the [You.com block](https://docs.sim.ai/integrations/youcom). +- **Browse connected sources:** Explore [Lucid folders](https://docs.sim.ai/search/lucid) and your private, shared, favorite, or recently viewed [Notion pages](https://docs.sim.ai/search/notion) without starting with a search query. diff --git a/apps/sim/content/changelog/power-bi-for-agents/production.md b/apps/sim/content/changelog/power-bi-for-agents/production.md index efcaee40364..3a0a663a3ff 100644 --- a/apps/sim/content/changelog/power-bi-for-agents/production.md +++ b/apps/sim/content/changelog/power-bi-for-agents/production.md @@ -34,6 +34,8 @@ Email body: These are drafts, not sent announcements. -## Editorial expansion +## Editorial revision -Expanded October 12, 2026, with supported capabilities, a practical example, and a short path to getting started. Copy was checked against the existing feature evidence and linked documentation. Original publication dates, release references, RSS identities, and reviewed media are unchanged; the article’s `updated` timestamp records this substantive copy revision. Browser and CI evidence belongs in the expansion PR. +Revised October 12, 2026, to clarify supported behavior and include selected changes from the same technical release where useful. Every public sentence describes a capability, a meaningful change, or necessary access information. Original dates, release references, RSS identities, and reviewed media are preserved. The `updated` timestamp records the substantive revision. Browser and CI evidence belongs in the revision PR. + +Additional v0.9.12 coverage: [You.com, #8584](https://github.com/simstudioai/sim/pull/8584) and [Lucid/Notion browsing, #8579](https://github.com/simstudioai/sim/pull/8579). The technical release includes both; current setup guides establish the supported operations and account requirements. diff --git a/apps/sim/content/changelog/review-fork-changes/index.mdx b/apps/sim/content/changelog/review-fork-changes/index.mdx index 53865264c83..5f6e228cd90 100644 --- a/apps/sim/content/changelog/review-fork-changes/index.mdx +++ b/apps/sim/content/changelog/review-fork-changes/index.mdx @@ -23,10 +23,8 @@ release: caption="Review source workflow changes before syncing a fork" /> -Sim now lets you review changes to a source workflow before syncing them into a workspace fork. The **Last Sync → Now** comparison shows what changed in the source since it was last successfully synced, including edits to prompts, settings, and workflow steps. +Review source workflow changes before syncing them into a workspace fork. **Last Sync → Now** compares the source at the last successful sync with its current deployment, showing prompt, setting, and workflow changes. Each fork and sync direction keeps its own baseline. -If you maintain a shared agent across several workspaces, use the comparison to understand an update before bringing it into a fork. For example, check a revised renewal-reminder interval and new settings together before syncing. Each fork and sync direction keeps its own baseline, so the review reflects that particular relationship. - -Open the fork’s mapping settings, choose the sync direction, and select **Compare** from a deployed workflow’s menu. Comparison becomes available after a successful sync establishes a baseline; the source snapshots must still be available. +Choose **Compare** from a deployed workflow’s menu in the fork’s mapping settings. A successful sync must establish the baseline first. Available with Forks enabled on Sim Cloud Enterprise or self-hosted deployments. Managing a sync requires admin access to both workspaces. [Learn more about workspace forks](https://docs.sim.ai/platform/enterprise/forks). diff --git a/apps/sim/content/changelog/review-fork-changes/production.md b/apps/sim/content/changelog/review-fork-changes/production.md index dbd107a990a..8f777b2c6a9 100644 --- a/apps/sim/content/changelog/review-fork-changes/production.md +++ b/apps/sim/content/changelog/review-fork-changes/production.md @@ -40,6 +40,6 @@ Email body: These are drafts, not sent announcements. -## Editorial expansion +## Editorial revision -Expanded October 12, 2026, with supported capabilities, a practical example, and a short path to getting started. Copy was checked against the existing feature evidence and linked documentation. Original publication dates, release references, RSS identities, and reviewed media are unchanged; the article’s `updated` timestamp records this substantive copy revision. Browser and CI evidence belongs in the expansion PR. +Revised October 12, 2026, to clarify supported behavior and include selected changes from the same technical release where useful. Every public sentence describes a capability, a meaningful change, or necessary access information. Original dates, release references, RSS identities, and reviewed media are preserved. The `updated` timestamp records the substantive revision. Browser and CI evidence belongs in the revision PR.