What’s new in Duct.

Models & agents

• Three tiers, one job map. Choose a Heavy, Standard and Light model in settings. Every agent job picks the tier it needs, so you are not selecting a model feature by feature.
• OpenRouter is a first-class provider. One key, and the tier map you already set applies to everything behind it.
• A ChatGPT subscription can drive the OpenAI slot — useful if you pay for the seat but not the API.
• Hosted runs use your keys, not ours. The hosted deployment stopped quietly falling back to Duct’s own provider credentials.

Workspace

• A command palette. One shortcut to jump between projects, connectors and agents — and you can bind your own shortcuts to the actions you repeat.
• Insights opens on what changed instead of an empty prompt box waiting for you to think of a question.
• Duct remembers the project you were in instead of resetting to the first one on every visit.
• Named controls, announced states, visible focus across the app, for anyone driving Duct by keyboard or screen reader.

Connectors

• The connector list now matches what a project can actually reach. Duct asks the server, rather than inferring availability from whichever keys happen to be saved.
• Every connected source is counted — the “sources connected” figure had been counting two of them.

Desktop

• Credentials a self-host build stores on your machine are encrypted with a key the app mints into your OS keychain.
• Connecting through the browser reports success as success — it had been calling a completed connection expired.

Memory

• Duct remembers per project. Positioning, competitors, what you corrected last week — carried into the next brief instead of pasted in again.
• Every recalled fact shows where it came from, as a chip you can dismiss when it is wrong.
• An off-switch per session for the times you want the agent working from a blank slate.
• Consolidation keeps memory from growing into noise, and a timeline shows what Duct learned and when.
• Seed a project from a file — drop in a positioning doc or competitor list and skip the cold start.

Desktop

• Windows and Linux builds, with self-update on all three platforms.
• Connect a data source in your own browser, where your password manager and existing Google session already are — not in a stripped-down app window.
• Sign-in failures explain themselves rather than returning a blank server error.

Reliability

• Crash capture, and outage explanations per platform, so “the brief is late” comes with a reason attached.

Execution

• Agent-proposed change sets. Propose, preview against a guardrail, approve, apply, roll back — every step visible before anything touches a live account.
• A three-rung autonomy ladder. Suggest only, approve each change, or let a narrow class apply itself. Raising a rung never widens what a proposal is allowed to touch.
• A review queue you can work through, with a detail drawer and approval of part of a change set rather than all of it.
• A structured activity log — the per-project audit trail of what was proposed, by whom it was approved, and what actually applied.

Connectors

• Google Ads, across five read connectors, plus executors for the changes teams make most often.
• Mixpanel, Microsoft Clarity and GrowthBook joined the catalogue.
• Per-project connector-to-account mapping, so one workspace can point each connector at the right ad account or property.
• Server-side connector credentials, and a Google Tag Manager connector for teams who would rather not hand out keys.

Artifacts

• Briefs and reports that outlive the session. A versioned store with stable links, agent edits, version history and exports — so a report you liked is still there next month.

Desktop

• A local backend the shell can bundle and supervise. A self-host build ships the server and database inside the app, so a project runs with nothing behind it. The published build leaves it out and uses the hosted API.
• macOS builds are signed with Developer ID and notarized — the DMG opens without a fight with Gatekeeper.
• The app finds its own API address at runtime, so one build works against the local sidecar or a hosted backend.

Insights

• A second audit engine you can select per request, with the existing one still the default — useful on the day a provider is having a bad time.

Workspace

• Invite teammates to a project as collaborators.

Security

• The security audit and secret-leak scan now block a release instead of reporting on one that already shipped.
• Every open dependency advisory in the app cleared.

Desktop

• Sign in through the system browser, with a deep link that hands you back to the app when you are done.
• macOS builds reach TestFlight for internal testers.

Connectors

• Google Ads with your own developer token. Bring one and connect today rather than waiting on ours to clear review.

Models & agents

• Bring your own provider API keys, sent with the request rather than parked on a server.
• A Providers tab that keeps them in one place instead of scattered through settings.

Desktop

• The first desktop app, storing your keys in the macOS keychain instead of a browser.

Insights

• Conversations survive the page. A streaming session is saved as it runs, so a refresh no longer costs you the thread.

Workspace

• Plan a month at a time — a calendar, a kanban board and an inline plan board over the same set of posts.
• Channels and linked social accounts, so a post knows where it is going before you approve it.

Workspace

• A content agent, end to end. Plan the week, draft the posts, publish them through your connected accounts.
• Image generation with multiple reference images per prompt, so a brand’s look carries from one post to the next instead of drifting.
• A bundled reference library the agent reads before drafting, rather than inventing a house style each time.
• TikTok discovery by keyword and hashtag, for seeing what already works before planning around it.

Connectors

• Connect Google Ads over OAuth and choose which account Duct reads.
• Sign in with Google, with privacy policy and terms in place from day one.

Insights

• A goal-driven flow. Pick the question you are trying to answer and Duct assembles the queries for it, instead of asking you to build them.
• Reports carry their evidence. Every claim ties back to the connector rows behind it, so you can check the working rather than trust it.