# General Input changelog

> Everything new in General Input, newest first, and what each change means for your work.

## Agents can use your saved browser from their first step

> The browser is now a tool every agent starts with, so workflows with a saved browser no longer fail because the agent never set the browser up.

Oct 13, 2026. Topics: Agents, Workflows. https://www.generalinput.com/changelog/2026-10-13-browser-ready-from-first-step

We made the browser one of the tools every agent starts with, like running code or reading files. Until now, an agent had to load the browser guide before it could open a browser at all. Most runs did, but a scheduled workflow with a [saved browser](/changelog/2026-09-25-saved-browsers-power-button) would sometimes skip that step, decide it had no browser, and stop without opening a page, even though the browser and its saved logins were fine. That failure is gone: a workflow that follows a script now goes straight to opening the browser.

### How it works

- **Workflows with a saved browser** have the browser from their first step, whether they run on a schedule, from a trigger, or by hand.
- **Conversations with a [specialist](/templates/specialists)** always have the browser, for any site behind a login or without an API.
- **Workflows without a saved browser** don't see the browser at all, since they could never open one. To give a workflow a browser, attach one where you connect its other accounts.
- **The browser guide** is still there for agents to read before they drive an unfamiliar site by hand: keeping track of what was asked, checking each step, handling sign-in pages, and recovering from errors.

## Clear no-access messages, and admins can view any specialist

> Pages you can't open now say so right away, admins can view every specialist and skill, and every share dialog uses one clear layout.

Oct 12, 2026. Topics: Collaboration, Security. https://www.generalinput.com/changelog/2026-10-12-access-messages-and-admin-view

Opening another member's private specialist used to retry for about seven seconds, then show a raw "not found" error. Detail pages now tell the difference between something you can't open and something that doesn't exist, and they say so right away.

### How it works

- **Access versus missing.** Specialists, workflows, apps, skills, and connections show "You don't have access" at once, with no retries, when the item exists but isn't shared with you. Anything deleted, missing, or in another workspace says it isn't available. The dashboard and iPhone app use the same wording.
- **Admins can view every specialist and skill.** Workflows and apps already had an admin view; now Owners and Admins can open any specialist or skill in their workspace by link, as a viewer. Nothing is added to their own lists, and chatting in another member's specialist still needs a share, so the chat entry explains why it's disabled.
- **Links that work.** Specialist links in Analytics and on member profiles open the specialist's page.

### Also shipped

- One share dialog for everything (specialists, workflows, apps, skills, databases, storage, connections, and browsers) on the web and iPhone: invite people as chips, see who has access, switch between invited-only and everyone in the workspace, copy a link, or transfer ownership.
- Sharing now says "Private" instead of "Restricted."

## Decision API: classify and score items with probabilities

> A hosted decision service answers choice, score, and yes-or-no questions about any item with a probability for each answer, for workflows and apps.

Oct 12, 2026. Topics: Developers, Workflows. https://www.generalinput.com/changelog/2026-10-12-decision-service

Many automations hinge on a judgment call: which team should get this ticket, is this lead a good fit, does this email need a reply. The new decision service answers questions like these with a probability for every possible answer, so your workflow can act only when it's confident enough. Like every built-in service, it needs no API key of your own and bills to your workspace.

### How it works

- **Three kinds of question.** A choice among up to 255 options, a score on up to 10 ordered levels, or a yes or no. One request can ask several questions about the same item.
- **Any item.** Send text or JSON, up to 32,000 input tokens.
- **Thresholds you control.** A new decisions skill teaches specialists how to phrase questions and set a confidence threshold for each action.
- **Stable models.** A request always names its model and is never silently moved to a newer one, because thresholds are tuned per model. At launch the model is TypeSafe's Jev, and you can bring your own TypeSafe key.
- **Clear failures.** Errors come back as one of six codes, and a provider's raw error never reaches you.
- **Proven in-house.** Our own Auto model routing and New task routing run on the same service.

### Also shipped

- Calls to our chat completion service can now name an exact model, such as Claude Haiku 5.5, Sonnet 5.5, Opus 5.5, or Gemini 3.8 Flash.

## Meta Muse Wonder arrives, and Muse Code joins Token Tunnel

> Meta's Muse Wonder is available as a hosted agent model with a 1M-token window, and Muse Code is the fifth subscription Token Tunnel connects.

Oct 12, 2026. Topics: Models. https://www.generalinput.com/changelog/2026-10-12-muse-wonder-and-muse-code

Meta released Muse Wonder on October 12, and it's in General Input the same day. You can also connect a Muse Code subscription through [Token Tunnel](/token-tunnel), alongside Claude, ChatGPT, Gemini, and Grok, and run Muse models on the plan you already pay for. Read about [Meta's earlier open-source Muse release](/blog/meta-open-sources-muse-spark-1-2).

### Muse Wonder

- A 1M-token context window, $4 input and $20 output per million tokens, $0.20 per million cached input tokens, and effort from minimal to xhigh.
- A default agent model, so specialists can run on it.
- Served through Vercel AI Gateway and OpenRouter. When it's overloaded, runs fall back to Claude Opus 5.5, then GPT-6.1 Sol, both in the same price tier.

### Muse Code on Token Tunnel

- Sign in with a device code from Meta, the same flow Grok uses.
- The tunnel offers Muse Wonder and Muse Spark 1.3. Muse Code's contributor variants, which train on your data, are never offered, and a test enforces it.
- Muse follows instructions reliably only when they arrive as a real system prompt (5 in 5 runs, versus 1 in 5 otherwise), so the tunnel sends them that way. Our tunnel test suite caught this before release.

### Also shipped

- Claude Haiku 5.5 on a Claude subscription now reliably answers as your specialist, held 10 of 10 times in testing.

## Real-time sync across web and iPhone with one sync engine

> Every list on the dashboard and iPhone now draws from one sync engine: your actions show instantly, others' changes arrive in about two seconds.

Oct 12, 2026. Topics: Platform, Mobile. https://www.generalinput.com/changelog/2026-10-12-one-sync-engine-for-every-list

The dashboard and the [iPhone app](/mobile) held the same lists (specialists, Home, Activity, conversations, resource cards, pins, badges) in about a dozen separate caches, and every send, stop, read, and live event had to remember to update each one. When one was missed, a specialist looked idle while it worked, or a finished run still looked busy. Both apps now draw every list from one sync engine per workspace, kept in step by a server change feed.

### How it works

- **A numbered change feed.** For each member, the server rebuilds what their lists show, records what changed under a sequence number, and clients pull everything past the number they have, with live updates in between. It follows Replicache's client-view approach.
- **Your actions draw at once.** Sends, stops, reads, pins, renames, and moves appear immediately and stay put until the server confirms them; only a refusal undoes one.
- **Opens already drawn.** The iPhone keeps the engine on the device and each browser tab keeps a copy locally, so the app draws before any network response.
- **Force-quit included.** When a push arrives, the iPhone fetches changes in the background, so even a force-quit app opens with the right run status.
- **Shared resources follow.** A change to a shared workflow or specialist reaches everyone whose lists show it, within about two seconds.
- **Tested hard.** A lifecycle harness runs 300 randomized sessions against a fake iPhone and a network that delivers answers in any order.

### Also shipped

- Send videos from your iPhone, up to 512 MB.

## Transcription API: turn audio and video into text

> A hosted transcription service turns audio and video files up to 1 GB into text, with speaker labels, word timings, and no charge for failed jobs.

Oct 12, 2026. Topics: Developers, Workflows. https://www.generalinput.com/changelog/2026-10-12-transcribe-service

Workflows and apps can now turn recordings into text with a built-in transcription service: meeting recordings, voicemails, interviews, podcast episodes, or any audio or video file. Like every built-in service, it needs no account of your own and bills to your workspace.

### How it works

- **Start a job.** Send a link to the audio, or upload the file itself (audio or video, up to 1 GB), and you get back a job ID.
- **Get the transcript.** Check the job for its status, full text, detected language, and audio length, plus speaker turns when speaker labels are on and word-level timings when you ask for them.
- **Better accuracy on your vocabulary.** Pass key terms, such as product names or industry jargon, to bias recognition: up to 1,000 on the most accurate model and 200 on the other.
- **Two models.** Choose between two AssemblyAI models, with the provider kept behind a seam so more can be added.
- **Fair billing.** The price is locked when a job starts, each job is billed once, and a failed job is free.

Use it from code workflows, app handlers, and sandbox scripts, and pair it with the [decision service](/changelog/2026-10-12-decision-service) to route calls by what was said.

## Agent Firewall blocks now say who can lift them and where

> When the Agent Firewall blocks an action, the agent now names the rule, links the setting that allows it, and says exactly who can change it.

Oct 11, 2026. Topics: Security. https://www.generalinput.com/changelog/2026-10-11-agent-firewall-block-messages

When the [Agent Firewall](/agent-firewall) blocked a request, the agent used to be able to say only "ask the workspace owner," which left people guessing. Every firewall refusal now explains itself: which firewall stopped the action, where it can be allowed, and who is allowed to change it.

### How it works

- **One shared answer.** For each firewall that denied an operation (the workspace's, the connection's own, or both), the refusal names the page that allows it: Settings, Agent Firewall for workspace rules, or the connection's own page.
- **Who can lift it.** The refusal says whether you can change the rule yourself, whether it takes a workspace Owner or Admin, or names the connection's owner. Only a connection's owner can change that connection's firewall; a workspace admin can't.
- **Everywhere agents run.** The same answer comes from the sandbox's outbound proxy, the `geni exec` command, and the integration relay, and the agent relays it with a link.
- **Warned before trying.** When an agent looks up an API operation that's blocked for a connection, the docs say so before it makes the call.
- **Never fails open.** Older sandboxes ignore the new details, and an unreadable policy falls back safely, so a version mismatch can't switch enforcement off.

## Zero-downtime app updates and faster cold starts

> An open app keeps running while a new build lands, sessions survive long calls, and a cold app's first request answers without polling delays.

Oct 11, 2026. Topics: Apps, Platform. https://www.generalinput.com/changelog/2026-10-11-apps-stay-up-through-publishes

When someone published a new version of an app you had open, the dashboard unmounted it for every build, failed builds included, and the iPhone app could run old screens against new server code for up to a minute. Viewers refreshing at once could also restart the app's server in parallel and disrupt each other. We rebuilt the session model under apps.

### How it works

- **The served build.** Each app records which build its viewers get, and that pointer moves only when a build succeeds. On the dashboard and iPhone alike, the running app stays up until the next build's server is ready, then reloads on the same page. A failed build never takes down the version you're using.
- **One restart.** After a publish, the first caller claims the server restart and everyone else waits for it.
- **Session identity.** Every server session gets a new ID that guards its writes, so a stale caller can't overwrite its replacement, and an unusable session is replaced in place.
- **Leases cover the longest call.** Calls in flight are counted, so a long export is no longer cut off when a short call ends.
- **Faster cold starts.** The app server starts and passes its health check in one step, and a first call that lands while it boots waits up to 10 seconds and returns directly.

### Also shipped

- App JavaScript and CSS are compressed, 68 to 78% smaller: a minimal app's first-paint bundle dropped from about 283 KB to 85 KB.

## Reliable conversation compaction for long AI chats

> Compaction now always lands a checkpoint, falling back to another model or a labeled excerpt, so one failed summary can't break a conversation.

Oct 11, 2026. Topics: Agents, Workflows. https://www.generalinput.com/changelog/2026-10-11-compaction-always-checkpoints

When a conversation outgrows its model's context, a summarizer writes a checkpoint and the conversation continues from there. In production, the default utility model could spend its whole output budget on hidden reasoning and stop before the summary was complete. Compaction then failed the run, and every later message in that conversation failed the same way. Compaction now always lands a checkpoint, and never writes a partial one.

### How it works

- **Bounded summaries.** The summarizer runs at its lowest thinking setting with a 16K-token output cap and a prompt asking for under 4,000 words.
- **A fallback chain.** If the utility model's summary errors, is cut off, or comes back empty, the run's own model writes it instead, and a context overflow retries once with half the input.
- **A last resort.** If no summarizer finishes, the checkpoint is a word-for-word excerpt of the start of the conversation and the latest work, clearly labeled, so the conversation keeps working.
- **Clean interruptions.** Cancel, timeout, and handoff abort the summary without writing anything, and Stop now interrupts a compaction in progress.

### Also shipped

- **Long workflows keep platform access.** A code workflow's platform key now lasts as long as the run itself, instead of expiring after 10 minutes.
- **Viewing a workflow never turns it off.** Opening a workflow's page mid-edit could disable it; reads no longer change anything.
- Fixes from our latest build eval: 22 builds on Claude Sonnet 5.5, all goals met.

## Phone trackpad control for live browsers, plus a watch mode

> Phone takeovers gain pinch zoom, tap to click, drag, right-click, and a clipboard, and every live browser gets real browser controls and a watch mode.

Oct 11, 2026. Topics: Agents, Mobile. https://www.generalinput.com/changelog/2026-10-11-live-browser-trackpad-and-chrome

Sign-in cards and AI connection sign-ins hand you a live browser so you can log in to a site yourself. On a phone, text sent into that page was typed key by key, which was slow and failed past 1,024 characters. The phone is now a trackpad over a zoomable page, and every live browser, on any screen, is framed in the same browser controls.

### Phone takeover

- Pinch to zoom up to 5x the fitted page, and pan or scroll with two fingers.
- Tap clicks and a quick second tap double-clicks. Tap then drag holds the button down for selecting text, sliders, and maps. A two-finger tap or long hold right-clicks.
- A clipboard menu copies the page's selection to your phone or pastes text from it in one step.
- A help sheet explains every gesture.

### Browser controls everywhere

Tabs, back, forward, reload, and the address bar frame the page wherever a browser appears, at one of three levels of access:

- **Drive:** your own browser, fully usable.
- **Drive in place:** an AI connection's sign-in, where the address is visible but can't be edited.
- **Watch:** an agent's browser inside a conversation or run. Everything is visible and nothing is pressable.

Watch mode is new: anyone who can read the conversation can see the agent's browser, and watching never affects the agent's session.

## Claude Haiku 5.5 becomes the default fast model

> Claude Haiku 5.5 replaces Haiku 4.5 with a 1M-token window and an effort setting, becomes a default agent model, and leads Auto's Fast tier.

Oct 8, 2026. Topics: Models. https://www.generalinput.com/changelog/2026-10-08-claude-haiku-5-5

Anthropic released Claude Haiku 5.5 on October 7, and it reached General Input on October 8. It replaces Haiku 4.5 everywhere, and it's the first Haiku to be a default agent model rather than opt-in, so specialists can run on it. It appears in the model picker, the hosted API catalog, and the Subscription group when you connect a Claude plan through [Token Tunnel](/token-tunnel). See the [models page](/models).

### How it works

- **The model.** A 1M-token context window (Haiku 4.5 had 200K) and adaptive thinking with an effort setting that defaults to medium. Anthropic lists it at $0.10 input and $0.50 output per million tokens for prompts up to 100K tokens, and five times that above.
- **Saved selections move over.** Any workflow, specialist, or setting that named Haiku 4.5 now runs on Haiku 5.5.
- **Auto, hosted.** The Fast tier now tries Claude Haiku 5.5 first, then GPT-6 Luna, Gemini 3.8 Flash, and Grok 4.7.
- **Auto on your subscriptions.** When Auto can use a model you've connected through Token Tunnel, each tier now runs one class above its hosted counterpart, because subscription usage isn't billed per token: Fast uses Claude Sonnet 5.5 or GPT-6.1 Sol, Balanced uses Opus 5.5 or GPT-6 Astra.

### Also shipped

- A connected device that only serves Haiku 4.5 is no longer presented as Haiku 5.5.

## Lazy-loading agent workspaces with a real filesystem

> A cold sandbox now restores only file metadata and fetches file contents as the agent reads them, so large workspaces no longer delay the first command.

Oct 8, 2026. Topics: Agents, Platform. https://www.generalinput.com/changelog/2026-10-08-lazy-workspace-filesystem

Every conversation gives its specialist a persistent work folder in its sandbox. Until now, a cold sandbox fetched that folder's contents before the agent could act, so the bigger the workspace, the longer the wait. As of October 8, the work folder is a real filesystem, built on open-source JuiceFS, that restores only names and metadata when the sandbox starts and fetches each file's data the first time something reads it.

### How it works

- **Lazy restore.** Metadata is restored with the sandbox, file data is fetched from storage on first access and cached, and small files are prefetched in the background so a full scan doesn't pay a round trip per file.
- **As fast as a native sandbox.** A restore is ready in about the time a fresh sandbox takes to boot, for workspaces up to 5,000 files and 128 MiB.
- **Real filesystem behavior.** Large files, random reads, memory mapping, permissions, and links behave as on a local disk, so shell and file tools need no changes.
- **Safe checkpoints.** Checkpoints run periodically and when a run pauses, completes, or hands off; a failed checkpoint keeps the previous one and retries.
- **Isolation.** A sandbox never holds our storage keys. It gets credentials for its own workspace only, valid for at most 24 hours, and a storage gateway checks every request.
- **Limits.** A workspace holds roughly 190,000 files; past that, the agent is told to remove rebuildable folders like node_modules.

## New task: describe the work and General Input routes it

> Start with the task, not a specialist. Your specialists are ranked against what you need, and the work goes to the best fit or a new specialist.

Oct 8, 2026. Topics: Specialists. https://www.generalinput.com/changelog/2026-10-08-new-task-routing

Starting a conversation used to mean choosing a specialist first. Now you start with the work. New task, in the sidebar, the Home menu, and the specialist list, opens the full chat composer. When you send, General Input ranks the specialists you can access and asks where the task should go: pick the recommended specialist, another one, or a new specialist that's created, named, and described from your message and starts on the task right away. The same flow ships on iPhone.

### How it works

- **Ranking.** A decision model (Jev, from TypeSafe) classifies your message against up to 40 of your most recently active specialists plus a "needs a new specialist" option, weighting each specialist's name as the main signal of its scope.
- **Nothing hidden.** Most tasks get one featured pick, but every specialist with a reasonable chance is listed too, and Browse all specialists is always there.
- **Never blocking.** Ranking has a 2.5-second budget; if it's slow or unavailable, you see your recent specialists instead.
- **Onboarding.** New workspaces end onboarding on the same composer: "What do you want to tackle first?"

### Also shipped

- Specialists can [read your other conversations](/changelog/2026-10-08-read-other-conversations) when it helps.
- Redesigned specialist pages, and a sidebar that shows only the specialists worth a glance.

## Specialists can read your other conversations for context

> A specialist can now look up what you've discussed with your other specialists, reading only your own chats, so you don't have to repeat yourself.

Oct 8, 2026. Topics: Specialists, Agents. https://www.generalinput.com/changelog/2026-10-08-read-other-conversations

You shouldn't have to repeat yourself to every specialist. Since October 8, a specialist can check what you've been discussing elsewhere: if you worked out a plan with your Chief of Staff on Monday, the specialist that carries it out on Tuesday can read that conversation instead of asking you again.

### How it works

- **Two tools.** One lists your conversations across every specialist, newest first, optionally narrowed to one specialist or filtered by title. The other loads up to 25 of them into the specialist's workspace.
- **Read on disk, not in context.** Loaded conversations are written as files the specialist can search, so a long thread doesn't flood the model's context.
- **Your chats only.** A specialist reads only the conversations of the person it's talking to, and only in runs that belong to that person, never in a background run acting for someone else.
- **Clean transcripts.** Loaded conversations include only what you and the specialist said, each line labeled with its real speaker and time, without tool calls or hidden reasoning.
- **Reference, never instructions.** Old conversations are marked as reference material, so text quoted in an earlier chat is never treated as a new instruction.

Pairs with [New task](/changelog/2026-10-08-new-task-routing), which routes each new request to the right specialist.

## Credit spend analytics by specialist, resource, and member

> Analytics is now one spend view in credits: group by specialist, resource, activity, segment, or member, compare periods, and read every receipt.

Oct 7, 2026. Topics: Collaboration. https://www.generalinput.com/changelog/2026-10-07-analytics-spend-view

Workspace owners ask Analytics two questions: what are we spending credits on, and who is spending them? The old page spread the answers across four tabs. We rebuilt it as a single spend view measured in credits, with runtime and run counts beside spend, since spend alone doesn't measure productivity. An Overview and a Logs tab replace the old Members, Executions, Security, and Usage tabs.

### How it works

- **Toolbar.** A member filter and a rolling window from 24 hours to 90 days. The window, grouping, and filter live in the URL, so a link opens the same view.
- **Tiles.** Credits spent, executions, and AI runtime for the window, each compared with the previous window of the same length.
- **Group by.** Specialist, Resource, Activity, Segment, or Member, as a chart over time and a ranked list. Resource ranks individual workflows, apps, and skills, with a workflow's runs, builds, and upkeep collapsed into one row. Activity groups spend by kind of work and covers 100% of it.
- **Credits or usage.** Switch the unit from credits to AI runtime or operation counts, so an expensive member reads differently from an unproductive one.
- **Logs.** Itemized receipts (what, who, when, credits) right in the page.

### Access

Owners and Admins see the whole workspace; every other member sees only their own spend, enforced on the server for every endpoint behind the page.

## Offline-ready iPhone app with on-device conversations

> Chat lists and recent conversations are cached on your iPhone, notifications fetch the reply before you tap, and reopening loads only what changed.

Oct 6, 2026. Topics: Mobile, Specialists. https://www.generalinput.com/changelog/2026-10-06-mobile-device-cache

The [iPhone app](/mobile) now opens on what it already has. Chat lists and recent conversations live on the device, a notification fetches its conversation as it arrives, and coming back reads only the messages you missed. Tapping a reply notification opens on the reply, even in airplane mode.

### How it works

- **Device cache.** A local SQLite store holds your chat lists, recent conversations, and signed-in identity. Twenty conversations are restored at launch and up to 200 are kept; the rest load when opened. The cache is scoped per server, user, and workspace, and wiped on sign-out.
- **Delta reads.** Reopening a conversation fetches only messages after the last one you have, or the newest page if a lot is new.
- **Notification extension.** When a push arrives, a Notification Service Extension downloads the conversation, so the reply is already on the phone when you tap.
- **Away-time messages appear quietly.** Only messages you watch arrive live animate in; anything that landed while you were away is simply there.
- **No stale "working."** Typing indicators and Stop appear only after a fresh check confirms the run is still going.

### Also shipped

- Messages you send while a specialist works wait in a tray above the composer, where you can edit or remove them.
- Word documents preview as laid-out pages, rendered in an isolated frame.
- Links open full screen in the native Safari view.

## Accurate OAuth connection results instead of popup guesses

> The dashboard now asks the server how each connect attempt ended, so failed or abandoned connections no longer count as success.

Oct 6, 2026. Topics: Integrations. https://www.generalinput.com/changelog/2026-10-06-oauth-connect-outcomes

Connecting an integration from the dashboard, or from a connect card in chat, now reports what actually happened. The server records how every connect attempt ended, and the dashboard waits for that answer instead of inferring it from the sign-in popup.

Before this change, the dashboard learned the result through a message from the popup. The browser security policy both the dashboard and the API send cuts that link, so the message often never arrived, and the fallback treated a closed-looking popup as success. In practice, failures and abandoned popups counted as connected, and a chat connect card could resume a specialist with no credential at all.

### How it works

- **One attempt, one record.** Starting a connection returns an attempt ID alongside the sign-in link, for every kind of OAuth connection.
- **A status check.** The dashboard checks the attempt every second until it's completed (with the new credential), failed (with its error), or expired after 10 minutes.
- **Owner-only.** Only the member who started an attempt can read it.
- **Security headers unchanged.** We kept the strict browser policy and moved the source of truth to the server.

### Also shipped

- New integrations: DocuWare, with a new-document trigger, and TalentLynk, with a campaign-status trigger.

## New workspaces start with $30 in free credits

> The welcome grant for a new General Input workspace rises from 800 credits ($5) to 4,800 credits ($30), a free month of one Pro seat.

Oct 6, 2026. Topics: Pricing. https://www.generalinput.com/changelog/2026-10-06-welcome-credits-30

Every new workspace now starts with 4,800 credits, worth $30, instead of 800 credits ($5). That's exactly one Pro seat's monthly allowance, so it amounts to a free first month of one Pro seat: enough to connect your tools, build your first specialists, and run real workflows before paying anything. See what a seat includes on the [pricing page](/pricing).

### How it works

- **One source for the number.** The grant is defined once, at our fixed rate of 160 credits per dollar, and the onboarding grant, the welcome cards on the dashboard and iPhone, and the pricing page's free tier ("4,800 free credits to start") all read that value, so they can't disagree.
- **Specialists know too.** The built-in help skill specialists use to answer product questions describes the new grant.
- **Who gets it.** Workspaces that accept their welcome credits after this release receive 4,800. Workspaces that already received 800 keep their existing balance.
- **Unchanged.** The low-balance warning still triggers at 160 credits.

New to General Input? Follow the [crash course](/blog/getting-started-crash-course) to sign up, connect your tools, and build your first workflow and app.

## More reliable browser agents, measured on WebArena-Verified

> The browser agent acts on stable element references and verifies batched form edits, and every change is scored on 468 WebArena-Verified tasks.

Oct 4, 2026. Topics: Agents. https://www.generalinput.com/changelog/2026-10-04-browser-agent-webarena

We reworked how the browser agent acts on pages and how long browsing runs hold their context, and we built a harness that scores browser changes on a public benchmark. The changes target three failure modes: forms left half-filled, observations that go stale after navigation, and long runs that lose their prompt cache.

### How it works

- **Stable element references.** The agent acts on the exact element it saw instead of re-finding it by selector.
- **Checked batches.** Several form edits apply in one guarded batch: each value is read back, a page that changed underneath is detected, and a batch that stops partway reports exactly what landed.
- **Settled observations.** After each step, the runtime waits for navigation and transitions to settle, and on large pages it puts the foreground content first.
- **Cache-friendly runs.** History within a run only grows, which keeps the prompt cache valid. An earlier version that pruned old screenshots cut cache reads from 90% to 65%, so we dropped it.

### How we measure it

The harness runs WebArena-Verified through our real browser stack: 468 of the 812 official tasks across Reddit, Shopping Admin, and GitLab clones, each in a fresh container with pinned versions. An October 4 sweep with Claude Sonnet 5.5 at high effort passed 349 of 468 (74.6%), the level future changes must beat.

### Also shipped

- Specialists can read workflow run history at any time, without loading a building skill.

## Instant chat updates and durable message sends on iPhone

> Sending, starting, stopping, and reading now update every list instantly, and iPhone sends retry for up to a day without ever duplicating.

Oct 4, 2026. Topics: Specialists, Mobile. https://www.generalinput.com/changelog/2026-10-04-instant-chat-durable-sends

Sending a message, starting a conversation, stopping a run, and reading a reply now update the sidebar, conversation lists, and Home immediately on the dashboard and in the [iPhone app](/mobile), instead of waiting for a round trip to the server. On mobile, a message you send keeps trying for up to a day, through dead zones, backgrounding, and relaunches, and a retry never creates a second copy.

### How it works

- **Same rows on both sides.** The code that builds conversation rows on the server is shared with the apps, so a row drawn optimistically matches the one the server returns. A failed action rolls back only what nothing newer has replaced.
- **A persisted outbox.** Every mobile send is written to the device first, then retried with backoff on network errors, and immediately when the app returns to the foreground. Messages in one conversation go in order.
- **Deduplicated on the server.** Each send carries a request ID, and the server keeps its receipt for a day, so a retry of a send that already landed gets the original result back.
- **Preloading.** The app fetches a conversation before you open it: when its run finishes, when a push arrives, and as soon as you tap.

### Also shipped

- Notifications clear on your phone when you read the item on another device, and badges stay in step.
- Conversation rows show what each one is doing, and specialist rows count the conversations that need you.

## Share a Token Tunnel subscription with chosen workspaces

> Owners of a hosted Token Tunnel account can share it with selected workspaces, so members there run chats and workflows on it. The login stays private.

Oct 2, 2026. Topics: Models, Collaboration. https://www.generalinput.com/changelog/2026-10-02-share-token-tunnel-accounts

A hosted [Token Tunnel](/token-tunnel) account (a Claude, ChatGPT, Gemini, or Grok subscription you signed in to through General Input) used to serve only its owner. You can now share each account with specific workspaces. Every active member of a workspace you add can use that subscription in chats and workflows, on the same plan limits, and you can remove a workspace at any time.

### How it works

- **Per-account sharing.** In Settings, under AI connections, each provider account has a Share action with a workspace picker. Recipients see the provider, its status, and your display name, never the provider account's email.
- **One model pool.** Your own accounts and accounts shared into the workspace form a single pool; requests spread across it, and a rate limit or connection failure falls through to another eligible account.
- **Pinned routing.** A shared request goes only to that one account, so retries never spill onto the owner's private accounts.
- **Live permission checks.** Both members and the share itself are checked before every request, so deactivating either one takes effect on the next attempt.
- **Clean revocation.** Disconnecting an account removes its shares, and reconnecting doesn't restore them.

### Also shipped

- GPT-6.1 Sol replaced GPT-6 Sol everywhere Sol is used, with saved selections moved automatically.
- Long runs on subscription models no longer fail while condensing the conversation, because the summary now streams.

## Faster agent workspaces: content-addressed file storage

> A conversation's files are now stored as deduplicated, content-addressed objects, so large workspaces restore quickly instead of re-downloading one archive.

Oct 1, 2026. Topics: Platform, Agents. https://www.generalinput.com/changelog/2026-10-01-content-addressed-workspaces

Every conversation with a specialist has a workspace: the files it keeps between turns. We used to save that folder as a single archive, so every cold start downloaded, unpacked, and later re-uploaded the whole thing. That scaled badly: one design conversation with 175 files and 260 MB of images saw its sandbox start climb from 2 to 15 seconds to more than 200 before it failed outright. Workspaces are now stored the way Git stores a repository, as content-addressed objects plus a manifest, synced incrementally.

### How it works

- **Stored once.** Each file is stored once by its content hash, and small files are grouped into packs, so a project with thousands of tiny files doesn't become thousands of requests. Unchanged files are never uploaded twice.
- **No lost work.** A new manifest is published only if the previous one is still current, so a late or stale save can't overwrite newer work or bring back deleted files.
- **Restores straight to the sandbox.** Files over 25 MiB upload from the sandbox itself instead of passing through our servers.
- **Migrated automatically.** Older workspaces convert the next time they're used.

### Also shipped

- When a workspace grows past 25 MiB in one file or 128 MiB in total, the agent sees the largest files and is guided to archive inactive ones to storage you've connected.
- Vercel joined E2B as a supported sandbox provider for deployments that configure it.

## Reliable image uploads in chat: no overwrites or file cap

> Same-named photo uploads no longer collide, the 20-file attachment cap is gone, images are resized for AI models, and oversized requests compact.

Sep 30, 2026. Topics: Agents. https://www.generalinput.com/changelog/2026-09-30-image-heavy-chats

Image-heavy conversations could go wrong four separate ways. Pasted phone photos could replace or corrupt each other, a large folder hit a fixed attachment cap, a request with many big images was rejected outright, and a request over a size limit ended the run. Between September 26 and 30 we fixed each one where it happened.

### How it works

- **Every upload gets its own path.** Phone photos are all called image.png, and paths came from the filename alone, so small uploads replaced each other and two large ones could write into the same file, leaving the agent with an image that was black below its top fifth. Your preview was always right; only the agent's copy was damaged. Each upload now lands in its own folder derived from its storage key.
- **No 20-file cap.** Attachments are planned against separate budgets for disk and for what's held inline, so a large folder works without flooding storage.
- **Images resized before sending.** Anthropic rejects a whole request when it carries more than 20 images and any is over 2,000 pixels on a side, so every outbound image is scaled to at most 2,000 pixels. For Claude this costs no quality.
- **Too big means compact, not fail.** A request over a size limit, such as 18 screenshots in one turn, now condenses the conversation and retries.

### Also shipped

- Condensed conversations keep your latest message word for word.

## Sign in with Apple on the web and iPhone

> Sign up, sign in, and accept invitations with your Apple ID, next to Google, and link or unlink Apple from your account settings.

Sep 30, 2026. Topics: Security, Mobile. https://www.generalinput.com/changelog/2026-09-30-sign-in-with-apple

You can now sign up, sign in, and accept invitations to a workspace with your Apple ID, alongside Google. Existing members can link Apple to their account, or unlink it, from account settings. The [iPhone app](/mobile) uses the same browser sign-in and device approval it already had.

### How it works

- **Fresh credentials every time.** The server signs a new, short-lived Apple client secret for every token exchange and refresh, so a long-running server never presents an expired one.
- **Strict origins.** Apple's sign-in callback is accepted only on its dedicated endpoint.
- **Clean unlinking.** Apple tokens are revoked before you unlink Apple or delete your account. If Apple fails temporarily, nothing is removed and you can retry.

### Also shipped

- Copying a pending invite's link always creates a fresh seven-day link.
- Google sign-in shows its account chooser, so you can switch Google accounts.
- Mobile sign-in stays open through brief network failures instead of closing midway through a password or two-factor prompt.

## General Input for iPhone, now in public beta on TestFlight

> Chat with your specialists, approve runs, and get push notifications on iPhone. The native app is open to everyone through a public TestFlight beta.

Sep 29, 2026. Topics: Mobile, Specialists. https://www.generalinput.com/changelog/2026-09-29-iphone-app-public-beta

General Input is on iPhone. The native app, open to everyone through a public TestFlight beta linked from the [mobile page](/mobile), puts your specialists in your pocket: chat with them, answer their questions, approve paused runs, and check on your workflows from anywhere.

### What's in the app

- **Home and Activity.** Your pinned work, conversations, and anything waiting on you, matching the dashboard.
- **Native chat.** Streaming replies, attachments, model selection, voice dictation, @-mentions, and answer cards for an agent's questions and approvals.
- **Your specialists and resources.** Browse specialists and their workflows, apps, and skills; open apps full screen; and launch, cancel, continue, or retry runs.
- **Push notifications** for runs that finish, fail, or need your input.
- **Easy sign-in.** Sign in through your browser with a quick device approval.
- **Built for iOS.** Native tabs with Liquid Glass on iOS 26, plus native menus and sheets.

The app keeps improving every week: since launch it gained [offline conversations](/changelog/2026-10-06-mobile-device-cache) and [real-time sync with the web](/changelog/2026-10-12-one-sync-engine-for-every-list).

## Introducing specialists: AI workers that each own one job

> Projects are now specialists: AI workers that own one job and build and run its workflows, apps, and skills. Every member gets a Chief of Staff.

Sep 27, 2026. Topics: Specialists, Collaboration. https://www.generalinput.com/changelog/2026-09-27-introducing-specialists

General Input now runs on specialists. A specialist is an AI worker that owns one job in your business, such as weekly reporting or lead follow-up. You describe the outcome in your own words, it asks what it needs to know, and it builds and runs the skills, workflows, and apps the job takes. Projects became specialists and kept everything they held. Read [why we made the change](/blog/introducing-ai-specialists).

### The model

- **A Chief of Staff for every member.** It answers questions across every connected tool, knows what each specialist owns, handles one-off work, and sets up new specialists for anything recurring.
- **Every resource has one home.** Each workflow, app, skill, file, and conversation lives in exactly one specialist.
- **One page per specialist,** holding its conversations, workflows, apps, skills, files, memory, and connected accounts.
- **Memory and files.** Each specialist keeps a plain-language memory of up to 12,000 characters for its rules and methods, and it never overwrites an edit it hasn't seen.
- **Members and privacy.** Sharing a specialist shares its resources, memory, and files; each member's conversations stay private.

### Starting a specialist

Start from a setup conversation, or from one of 65 [specialist templates](/templates/specialists), each built around a single job with its memory, sample files, skills, workflows, apps, and tests. Twenty-eight are workstream specialists for specific industries.

Nothing was deleted or turned off: each project became a specialist with the same contents, and loose work moved to each member's Chief of Staff.

### Also shipped

- A Chat command palette in the sidebar: pick a specialist, then one of its conversations.

## Self-serve account deletion on web and iPhone

> Delete your General Input account yourself from the dashboard or iPhone app, choosing who takes over your work in each workspace first.

Sep 25, 2026. Topics: Security, Collaboration. https://www.generalinput.com/changelog/2026-09-25-account-deletion

You can now delete your own General Input account, from the dashboard or the [iPhone app](/mobile), without contacting support. Before anything is removed, you see every workspace you belong to and everything you own in each one, and you decide what happens to it.

### How it works

- **A full inventory.** Settings lists each workspace and what you own there: specialists, workflows, apps, skills, connections, databases, file stores, and browsers.
- **Choose a successor, or delete.** For each shared workspace, pick who owns your work after you, or delete it all. If you're the workspace's owner, you also pick its next owner.
- **Solo workspaces go with you.** A workspace where you're the only member is deleted with your account and erased within 30 days.
- **Preview first.** You see everything affected before confirming, and nothing is removed until you do.
- **Leave without deleting.** Leaving a single workspace offers the same choices for that workspace while keeping your account.

To remove an entire workspace instead, see [workspace deletion](/changelog/2026-08-05-workspace-deletion).

## Business plans now start at one seat

> The five-seat minimum on Business Pro and Max is gone. Buy seats for exactly the members you have, from one to 50, with prorated additions.

Sep 25, 2026. Topics: Pricing. https://www.generalinput.com/changelog/2026-09-25-business-plans-one-seat

The Business plan used to require at least five seats, so a team of two paid for five. That minimum is gone. Choose a seat count starting from one, and each seat adds its credits to the workspace's monthly allowance plus a spot for one member. See plans on the [pricing page](/pricing).

- **Pro:** $30 per seat per month, with 4,800 credits per seat.
- **Max:** $100 per seat per month, with 16,000 credits per seat.

Both tiers cover up to 50 members, and seats added later are prorated.

### How it works

- **One upgrade screen.** Choosing a plan moved out of onboarding into a dedicated upgrade screen with a seat picker that prices each plan at the count you choose. The public pricing page renders the same plan cards.
- **Onboarding starts with credits.** The plan question became a welcome-credits step: a new workspace starts with credits to build and run with, and no card is needed.
- **One page when the balance runs out.** A workspace with nothing left to spend sees a single screen offering pay-as-you-go credits, a plan, or a call with us, then returns to where it was headed.
- **Billing on the web.** The iPhone app shows your plan and balance without asking you to pay; low-balance reminders go by email and Slack.

## geni CLI and MCP server now manage specialists and runs

> geni CLI 0.19.0 and the MCP server gain specialist, file, template, sharing, credential, version, and run-control operations for coding agents.

Sep 25, 2026. Topics: Developers. https://www.generalinput.com/changelog/2026-09-25-cli-mcp-specialists-sharing-runs

With specialists, the `geni` CLI and the MCP server picked up a long list of operations that used to need the dashboard. Agents inside General Input got the same operations as tools, so an outside coding agent, the CLI, and a specialist all work through one set of actions. The developer docs were audited against the deployed tools and every `/v1` route in the same release. See the [developer page](/developers).

### What's new

- **Specialists.** List, create, update, delete, and pin specialists, and move resources between them.
- **Specialist files.** List, pull, push, and remove files. Every write must present the version it read, so a stale write is refused instead of overwriting someone else's change.
- **Export, import, and templates.** Export a specialist as a ZIP with chosen files and memory, import one, and install or publish specialist templates.
- **Sharing.** Inspect, grant, and revoke access for one member or the whole workspace.
- **Credential maintenance.** Check health (status, expiry, and scopes, never secrets), refresh, rename, annotate, and see what depends on a credential.
- **Run control.** Resume a paused run, follow up on a finished one, cancel, or retry with the original input, and inspect or replay trigger activity.
- **Versions.** List and revert resource versions, enable or disable resources, and capture app screenshots at phone and desktop widths.

### Breaking changes

MCP tools named for projects were renamed for specialists, for example `list_projects` to `list_specialists`.

## Home inbox notifications and iPhone push alerts for runs

> Notices now live in the Home inbox beside conversations and paused runs, the iPhone app gets push notifications, and failed runs alert you once.

Sep 25, 2026. Topics: Workflows, Mobile. https://www.generalinput.com/changelog/2026-09-25-inbox-and-push-notifications

Notices used to sit behind a bell, apart from the conversations and runs they were about. They're now rows in the Home inbox: unread ones appear in Unread on the dashboard and in Activity on the iPhone app, next to conversations and paused runs, and every notice is kept in History. Alongside the move, the [iPhone app](/mobile) gained push notifications, and workflows learned to tell you when a live run fails or stops to ask you something.

### How it works

- **Per-member channel switches.** Settings has one switch per event and channel (email, Slack, push), grouped into Specialists, Operations, Billing, Digests, and Sharing, the same on the dashboard and the phone.
- **Push that respects what you've seen.** A push waits five seconds and is sent only if the item is still unread, so a conversation you're watching never buzzes your phone.
- **Failed runs, announced once.** When a live workflow run fails, its owner gets an inbox notice, email, and push linked to the run. Notices stop at five per workflow per day, and failures caused by our own deploys don't notify.
- **Paused runs reach every channel.** A paused run notifies on every connected channel by default; email and Slack wait a minute, so a question you answer right away never reaches your inbox.

### Also shipped

- Emails about a run name its specialist as the sender, like "General Input - Invoice Chaser."

## Saved cloud browsers with a power button and lasting logins

> Your saved browser is now a cloud computer you switch on. Sign-ins are refreshed every three days, and agents try single sign-on before asking you.

Sep 25, 2026. Topics: Agents. https://www.generalinput.com/changelog/2026-09-25-saved-browsers-power-button

Signing an agent into a website used to run through a guided flow where an agent checked and steered each sign-in. It was slow and brittle, so we replaced it with something plainer. On the Browser page (in beta), your saved browser is a computer with a power button: switch it on, browse and sign in to anything the way you would on your own machine, and switch it off. Agents, workflows, the CLI, and the MCP server reuse whatever you signed in to.

### How it works

- **Saves as you go.** The browser saves its state on each page load and every five seconds, so a dashboard refresh reconnects to the same session. It powers off after two minutes with nobody watching, or 15 minutes of inactivity.
- **Real logins only.** A site appears in your saved logins only when a sign-in cookie or token actually appears, not just because you visited.
- **Sign-ins kept fresh.** Every three days a background visit reopens each active login's site so it reissues its cookies before common one- and two-week timeouts.
- **Single sign-on first.** A saved login remembers its provider, like "signed in with github.com." At a sign-in wall, an agent clicks that provider's button once; anything beyond that waits for you.
- **Handing a sign-in back.** When an agent hits a wall it can't pass, it sends you a card that opens your browser on that exact page.

## Capacity: per-workspace rate limits and smoother schedules

> An audit of what would break at ten times our usage lifted three limits: per-workspace rate limits, non-blocking token refreshes, and spread-out schedules.

Sep 24, 2026. Topics: Platform. https://www.generalinput.com/changelog/2026-09-24-capacity-improvements

We audited what would break if usage grew tenfold, sized each fix from measured numbers, and lifted three limits that were already slowing busy workspaces down. The result is steadier performance at the moments workspaces are busiest, like the top of the hour when many schedules fire at once.

### How it works

- **Per-workspace rate limits.** Calls from workflows to our built-in services shared one rate limit across every workspace. Each workspace now gets its own 1,000 requests a minute, so one busy workspace can't slow down another.
- **Token refreshes no longer block the database.** Refreshing a connected account's token used to hold a database connection during the provider's response. A token that's still valid now skips the lock entirely, waiting requests release their connection while they wait, and provider calls time out after 30 seconds.
- **Schedules spread out.** Each scheduled trigger starts at a small, stable offset, so a burst of runs on the hour no longer spills past the pool of warm sandboxes.
- **Faster long conversations.** Looking up the latest message in a long conversation dropped from 67 ms to 0.4 ms.

### Also shipped

- Saving an unchanged schedule no longer rewrites it, which used to drop its next pending run.
- 31 read-only triggers now retry temporary server errors.

## Real Postgres, MySQL, and SQL Server errors for AI agents

> Agents now see the database's own error message instead of a generic failure, so they can fix their own SQL queries on Postgres, MySQL, and SQL Server.

Sep 24, 2026. Topics: Integrations, Agents. https://www.generalinput.com/changelog/2026-09-24-database-error-messages

When a query against your [PostgreSQL](/apps/postgresql), [MySQL](/apps/mysql), or SQL Server database failed, agents used to get a generic "Database query failed" with no detail. That hid real SQL mistakes, like a misspelled column or a missing join, from the agents that could have fixed them. Now the agent sees the database's own message and corrects the query itself.

### How it works

- **Classified at one boundary.** A rejected query returns the database's own message, a statement timeout and an unreachable server each get their own status, and a refused login is reported as such.
- **Clear connection errors.** When you connect a database that refuses or can't be reached, you see the server's own reason instead of a generic failure.
- **Platform faults read as platform faults.** Internal errors and overloads in our hosted databases are reported as service problems, not as mistakes in the agent's query.

Your hosted [workspace databases](/changelog/2026-03-26-workspace-databases) get the same treatment.

## Hosted Token Tunnel: your AI plan, no desktop app needed

> Sign in to your Claude, ChatGPT, Gemini, or Grok subscription once in Settings and use it in every workspace, with no computer left running.

Sep 22, 2026. Topics: Models, Security. https://www.generalinput.com/changelog/2026-09-22-hosted-token-tunnel

Running agents on your own AI subscription used to mean keeping General Input Desktop open on a computer that stayed online. The hosted [Token Tunnel](/token-tunnel) runs that connection in our cloud instead. In Settings, under AI connections, sign in to Claude, ChatGPT, Gemini, or Grok once, and those models appear in the model picker in every workspace where you're an active member. New members can connect a subscription during onboarding, and the iPhone app has the same page.

### How it works

- **Sign in on the provider's own pages.** Sign-in runs in a hosted browser framed by the dashboard, using the provider's standard secure flow, and only the provider's own pages can open.
- **One isolated connection per person.** Each person's connection runs in its own isolated environment, walled off from everyone else's, with credentials encrypted and bound to their owner.
- **Several subscriptions stack.** Requests rotate across every account you connect for a provider, and a rate-limited account fails over to another within the same request. When all are limited, the error says when they reset, and Auto routes to another model.
- **Accounts leave only on the provider's word.** An account is removed only when the provider rejects it, and you get an email.
- **Updates don't cut streams.** In-flight chats finish before a host is replaced, and every proxy update must answer a real chat on all four providers before it ships.

## Claude Opus 5.5, GPT-6 Sol and Luna, and Grok 4.7 arrive

> Opus 5.5 and GPT-6 replace Opus 5 and GPT-5.6 at lower per-token prices, Grok 4.7 replaces 4.6, and Auto tiers span four providers.

Sep 22, 2026. Topics: Models. https://www.generalinput.com/changelog/2026-09-22-opus-5-5-gpt-6-grok-4-7

We moved the catalog to the newest generation of each frontier model family, and saved selections followed on their own: a workflow, app, or specialist that names a retired model now runs on its successor, so nothing had to be re-saved. Subscription models through Token Tunnel follow the same upgrades. Compare everything on the [models page](/models).

### What changed

Prices are per million input and output tokens.

- **Claude Opus 5.5** replaces Opus 5 and 4.8 at $4 / $20, down from $5 / $25, with a 1M-token context.
- **GPT-6 Sol** replaces GPT-5.6 Sol at $2 / $10, down from $5 / $30.
- **GPT-6 Luna** replaces GPT-5.6 Luna at $0.10 / $0.50, down from $0.20 / $1.20. Both GPT-6 models have a 1.05M-token context.
- **Grok 4.7** replaces Grok 4.6 and 4.5 at the same $2 / $6, with a 500K context and a new xhigh effort level.
- **Claude Sonnet 5.5** replaced Sonnet 5 on September 28.
- **Default effort per model.** Every model used to default to medium; each now has its own default within its supported range.

### Auto

Each tier starts cheap on the cost-to-intelligence frontier and falls back across four providers (OpenAI, Anthropic, Google, xAI), so one provider's outage can't take a tier down. When one of your own subscription models is online, Auto uses it in place of the tier's cloud model.

## Token Tunnel detects a sleeping computer in seconds

> Runs on a subscription model served from General Input Desktop now move on in about a second when the computer sleeps, instead of up to 4 minutes.

Sep 16, 2026. Topics: Models, Platform. https://www.generalinput.com/changelog/2026-09-16-token-tunnel-fault-detection

When a run used a model served from your own computer through [Token Tunnel](/token-tunnel) and that computer slept or lost its network, the run could wait 90 seconds to 4 minutes before failing. Fallback then tried every other model on the same unreachable machine before reaching a cloud model. In a typical week, about 96% of device disconnects were only caught by a server ping, mostly computers that fell asleep with the tunnel still marked connected.

### How it works

- **Faster detection.** The desktop app closes its connection before the computer sleeps, which fails open requests in about a second, and a dropped connection is detected within 15 seconds instead of 30 to 45.
- **Disconnects aren't model faults.** Timers are tuned per provider and can never fire before dead-connection detection, so an unreachable computer is always reported as a disconnect.
- **No retrying a dead machine.** When the device is unreachable, fallback skips every other model it serves and goes straight to the next option.
- **Native endpoints.** Claude runs over the Messages API and ChatGPT's Codex models over the Responses API, with tool inputs streamed as they're written. A 32 KB file write used to mean 99 seconds of silence; the longest gap is now 1.6 seconds.
- **Thinking isn't a stall.** The desktop proxy sends a keepalive while a model thinks quietly, so long reasoning is no longer cut off.

### Also shipped

- Workflows pinned to a subscription model are no longer disabled when one account hits a rate limit.

## GPT-6 Astra and Claude Fable 5.1 available on hosted keys

> GPT-6 Astra and Claude Fable 5.1 join the hosted catalog for every workspace, GLM 5.3 and DeepSeek V4.1 Flash arrive, and long-context pricing ships.

Sep 15, 2026. Topics: Models, Pricing. https://www.generalinput.com/changelog/2026-09-15-gpt-6-astra-claude-fable-hosted

GPT-6 Astra and Claude Fable 5.1 are now hosted models: any workspace can run them on General Input's provider keys without connecting a subscription. Until now both were reachable only through [Token Tunnel](/token-tunnel). Compare them on the [models page](/models).

### What changed

- **GPT-6 Astra:** a 1,050,000-token context, at $10 per million input tokens and $50 output, with cache reads at $1. Above 272,000 input tokens, input bills at 2x and output at 1.5x.
- **Claude Fable 5.1:** a 1,000,000-token context and up to 128,000 output tokens, at $10 input and $50 output, with cache reads at $0.25.
- **Same-model failover.** Both are also served through Vercel AI Gateway and OpenRouter, so an overload moves the same model to another route before any fallback.
- **Long-context pricing** is now a catalog field: an input threshold plus multipliers. Each request in a long run is priced against its own context size.

### Also shipped

- GLM 5.3 replaces GLM 5.2, and GLM 5.3 Flash joins with a 1M-token context.
- DeepSeek V4.1 Flash replaces V4 Flash, adds vision, and costs half as much: $0.22 input and $0.66 output per million tokens.
- Token Tunnel now delivers instructions to Claude and ChatGPT subscriptions as a real system prompt.

## Transfer ownership and offboard members without orphans

> Owners can hand any workflow, app, skill, project, or credential to another member, and deactivating someone transfers or deletes what they own.

Sep 15, 2026. Topics: Collaboration. https://www.generalinput.com/changelog/2026-09-15-ownership-transfer

Every resource in a workspace can now change hands, and deactivating a member can no longer strand what they built. An owner can give a workflow, app, skill, project, credential, database, store, or browser to any active member. When someone leaves, an admin moves everything they own to a successor, or deletes it, in the same step as the deactivation.

### How it works

- **Three kinds of move.** A transfer gives one resource away, a handoff moves everything a member owns to a successor, and an adopt lets an admin take over resources whose owner is already inactive.
- **Workflows move with their wiring decided.** For each connection the giver owns, they choose share or disconnect. Transfer stays disabled until every choice is made, because a workflow wired to something its new owner can't see breaks on its first run.
- **Projects move with their contents**, with a preview of what will move. Other members' resources in the project stay theirs.
- **No lost races.** Every owner change checks the expected current owner first.
- **Deactivation takes a policy.** Transfer everything, delete everything, or neither only when the member owns nothing, all in one transaction.

### Sharing surfaces

- Every resource names its owner, and sharing reads as Private or Shared.
- Controls you can't use are disabled with a tooltip that says why, never hidden.

### Also shipped

- Enable or disable a workflow or skill from the agent, the API, or `geni resource enable`.

## Exactly-once triggered runs, and cancels that keep output

> Run starts go through a transactional outbox, cron and webhook firings are deduplicated, and cancelling a run keeps the step the agent was writing.

Sep 14, 2026. Topics: Workflows, Platform. https://www.generalinput.com/changelog/2026-09-14-exactly-once-triggers

Three gaps at the edges of a run are closed. A run that exists in the database is always handed to a worker, a redelivered schedule or webhook can no longer execute twice, and stopping a run no longer throws away the text the agent was in the middle of writing.

### How it works

- **Durable starts.** Starting, resuming, or continuing a run writes its queue job in the same database transaction as the run itself, through an outbox. A publisher sends committed jobs immediately and a one-second sweep repairs anything it missed. If publishing keeps failing, the run fails with that reason instead of sitting queued forever.
- **One run per firing.** Every triggered run carries a key unique to its trigger firing, so a redelivered event finds the existing run instead of starting a second one.
- **Cancel keeps output.** A worker saves its partial step before reporting cancelled, and a run that finished in the meantime isn't overwritten.

### Also shipped

- Rerun and Test are no longer disabled while another run of the same workflow is in progress.
- Apps queue requests during busy moments (up to 256 in flight and 2,048 waiting) instead of rejecting anything past 16.

## Full-screen file viewer for PDFs, images, and spreadsheets

> Files in chats and workflow runs open in a full-screen viewer: zoomable images, continuous PDFs, spreadsheets with sheet tabs, and playable media.

Sep 14, 2026. Topics: Agents, Workflows. https://www.generalinput.com/changelog/2026-09-14-file-viewer

Agents produce and read a lot of files: reports, spreadsheets, screenshots, recordings. Opening one now fills the screen with the file itself, on a black backdrop with just a close button and a download button, on the dashboard and in the iPhone app alike.

### How it works

- **Images** fit the screen; double-click to zoom and drag to pan.
- **PDFs** scroll continuously as white pages and render only the pages near what you're reading, so a long document stays fast.
- **Spreadsheets** keep their grid, with tabs for each sheet.
- **Word documents** sit on a white page, and **HTML files** render as themselves, so an email draft looks the way it will in an inbox.
- **Markdown, code, slides, and archives** each get a clean page, and **audio and video** play straight from storage.
- **Run inputs and outputs too.** The files a workflow run received and produced open in the same viewer from the run's side panel, with the preview chosen by file type.

## Request protection, run-scoped credentials, and new roles

> Requests from untrusted origins are rejected, runs reach only the credentials they declare, and model and billing management get their own permissions.

Sep 14, 2026. Topics: Security, Collaboration. https://www.generalinput.com/changelog/2026-09-14-request-and-credential-hardening

A security review of the request surface, and of how runs reach credentials, shipped as a set of protections. None of them change how a workflow is written; they narrow what a request or a run can reach.

### How it works

- **One trusted-origin list.** Cross-origin settings, sign-in, file storage, the OAuth popup, session handling, and live connections all read the same list. A state-changing request from an untrusted origin is rejected.
- **Run credentials bound to the declaration.** A run can use only the credentials, databases, and stores its own slots declare, and the database proxy checks that a credential belongs to the run before connecting.
- **Validated connection fields.** An OAuth connection accepts only the fields an integration declares, such as an instance URL, each checked against its allowed pattern before anything is stored.
- **Retry-safe top-ups.** A credit purchase carries a request ID, so a retried submit can't charge twice.
- **Clearer connect links.** The hosted page that completes a connection names the workspace and the person who asked.

### New permissions

Manage workspace models, and Manage subscription and seats. Both default to Admins and Owners and are enforced on the server as well as in settings.

## New dashboard Home with pins, one feed, and a Resources page

> The dashboard opens on Home: pinned work in the sidebar, one feed of chats and runs waiting on you, and one Resources grid instead of four lists.

Sep 10, 2026. Topics: Specialists, Workflows. https://www.generalinput.com/changelog/2026-09-10-home-and-resources

The dashboard is rebuilt around what you come back to. The new Home became the dashboard for every workspace in early September: one feed of your work, your pins in the sidebar, and every workflow, app, and skill in a single Resources grid, so you no longer need to remember which list page something is on. (Projects here are what we now call specialists.)

### How it works

- **Pins.** The sidebar holds pinned workflows, skills, apps, projects, and chats in an order you drag. A pinned workflow opens to its launch form and runs, a pinned skill to a chat with that skill attached, and a pinned app to the app itself.
- **One feed.** Home lists chats, editing sessions, and runs waiting on your answer, newest first, built once on the server. The unread count and the inbox are the same list filtered, so the number and the list can't disagree.
- **One Resources page.** Every workflow, app, and skill in one grid, with kind, ownership, and sort filters plus search. Old links redirect.
- **Resource art.** Listings draw each resource's own art: an app's thumbnail, or a workflow's trigger and the integrations it calls.

### Also shipped

- One actions menu per resource kind (enable, rename, copy, export, move, pin, delete), shared everywhere the resource appears.

## Version-checked publishing stops overwritten workflows

> Every publish from an agent, the geni CLI, or MCP is checked against the version it started from, so a stale draft is refused instead of reverting work.

Sep 10, 2026. Topics: Workflows, Developers, Collaboration. https://www.generalinput.com/changelog/2026-09-10-publish-conflict-checks

Two chats editing the same workflow could silently revert each other: a conversation holding a draft from days earlier could publish it and wipe out changes another chat had made since. Every publish from an agent, the `geni` CLI, or an MCP client is now conditional on the version its working copy was taken from. A stale copy is refused with instructions to re-read and merge, never applied.

### How it works

- **Every working copy knows its base.** A chat's draft or a CLI directory records the version it came from, and one rule decides the check for every publish path.
- **No bypass.** Holding no working copy doesn't skip the check, and the only override is an explicit force by a person.
- **The winner's files are safe.** The version is claimed before files are written, so a losing publish can never clobber the winner.
- **Unpublished work is kept.** An untouched draft refreshes itself when a run starts; a draft with edits is kept and its publish is checked instead.
- **Refusals are recovery steps.** Read what's live, combine both sets of changes, publish again.

### How we tested it

344 tests cover the change, including an end-to-end replay of the original incident against a real database and real stored files, with the key checks mutation-tested.

Older versions of the `geni` CLI are asked to upgrade.

## Multi-provider model routing with same-model failover

> A model can now be served by several ranked provider routes. On overload, runs move the same model to its next route before switching models.

Sep 8, 2026. Topics: Models, Platform. https://www.generalinput.com/changelog/2026-09-08-model-route-failover

Model routing now lives in one engine, and a model can be served by more than one route. Every chat model in the catalog has its native provider plus routes through Vercel AI Gateway and OpenRouter. When a provider is overloaded, a run first moves the same model to its next untried route, and only then falls back to a different model, so a provider incident doesn't have to change which model is doing your work.

### How it works

- **Ranked routes.** Native lab APIs (Anthropic, Vertex, OpenAI, xAI, Fireworks) first, then Vercel AI Gateway, then OpenRouter.
- **Route hops are free.** A run tracks the routes and the models it has tried separately, so switching routes doesn't use up a model fallback.
- **Caching follows the route.** Each route declares how it handles prompt-cache breakpoints, reasoning effort, and session affinity, so a Claude request through a gateway keeps its cache discounts.
- **Embeddings too.** Embedding requests use the same routes, and a route returning vectors of the wrong size is rejected so stored vectors stay comparable.

### How we verified it

Live suites run every route of every model at every effort level, plus streaming with tools, vision, and cache reads. They caught a provider alias that had started returning errors in production, which is now pinned to its dated version.

### Also shipped

- Muse Spark 1.3, the first model served only through a gateway.

## Scoped API keys and platform keys for the General Input API

> Every /v1 route now requires one named scope. Personal keys act as you; workspace platform keys let outside agents use docs, credentials, and services.

Sep 3, 2026. Topics: Developers, Security. https://www.generalinput.com/changelog/2026-09-03-scoped-api-keys

The public `/v1` API now has two kinds of key with separate, explicit scopes, and every route checks exactly one. A personal key acts as you and manages your workflows, skills, memory, projects, and triggers. A platform API key, now available to every workspace, acts for the workspace: it can search the integration catalog, hand out credential tokens, and call hosted services, but can never start a run or touch members' resources. That split lets you give an outside agent, such as Claude Code, Codex, or your own, exactly the access it needs. See the [developer page](/developers).

### How it works

- **No wildcards.** Platform keys hold docs, vault, and platform scopes; personal keys hold workflow, skill, memory, project, and trigger scopes.
- **Hosted services.** A single endpoint reaches internet search, scraping, email, image generation, and chat completion, billed to the workspace.
- **Credentials.** List the credentials a key's member can use (field names, never values), or issue a fresh access token through the same audited path runs use. Refresh tokens are never returned.
- **Connections.** Open a pending connection that a person completes through the regular sign-in flow.
- **Tied to a person.** If the member who created a platform key leaves, the key stops working.

### Also shipped

- A full `/v1` reference in the developer docs, including scopes, errors, and rate limits.

## Workflow filters skip irrelevant events before agents run

> An optional filter.ts runs before a workflow, decides in code whether a run happens, and ends rejected events as filtered instead of waking an agent.

Sep 3, 2026. Topics: Workflows, Agents. https://www.generalinput.com/changelog/2026-09-03-workflow-filters

Any code or agent workflow can now carry an optional `filter.ts`: a cheap, deterministic check that decides whether a run happens at all, and on what input. A busy webhook or poll trigger no longer wakes an agent for every event. A code check costs roughly a tenth of a cent; an agent run costs 40 to 250 times that before it does any work, so on a noisy trigger the filter decides most of the bill.

The same mechanism is also a custom trigger: paired with a schedule, a filter can poll any source that has no built-in trigger, skip what it has already seen, and run only on new items. The trigger picker has a new Custom option that writes the schedule and filter for you.

### How it works

- **Same context as the workflow.** The filter runs in the sandbox with the workflow's credentials, settings, databases, and firewall rules, and returns skip with a reason, or run with an input.
- **Filtered is a success.** Skipped events end with a filtered status, never count toward auto-disable, and show their reason in history.
- **Fails open.** An error, a 60-second timeout, or no decision means the workflow runs anyway; a filter is an optimization, never access control.
- **Evidence in the document.** The filter block shows 7-day counts, the last five rejections, and a "too strict?" warning after 25 events with no passes.

## Integration docs tested against live APIs every day

> A test suite per service checks what our integration docs claim against the real API daily, so agents hit fewer failed calls. Plus August's new apps.

Aug 31, 2026. Topics: Integrations, Platform. https://www.generalinput.com/changelog/2026-08-31-integration-docs-verified-live

Agents call your integrations from our documentation of each API, so a wrong field name or a retired endpoint becomes a failed run. We now check that documentation against the live APIs. Each service gets a test suite whose probes encode what our docs claim, and a daily run replays them. The finding we care about is a faithful probe failing because the API disagrees with the docs.

### How it works

- **Two modes.** Verify replays the committed suite deterministically, with no model involved, so it's cheap enough to run daily. Author runs a maintainer agent to write or repair a suite, but never in response to a failure, which would hide real drift.
- **Evidence, not status codes.** A 200 can carry an error body and a 403 can mean a higher plan tier, so each result is classified as passed, failed, needs a human, or requires a paid plan.
- **Safe test data.** Probes may create the records they need, but never spend money, message a person, or touch data they didn't create.
- **Scope today.** The catalog documents 34,054 operations across 557 services, and 201 services with test accounts put 11,169 operations in reach.

### Also shipped

- New integrations in August include 1Password, Bitwarden, SignWell, DocuSeal, Hootsuite, Sprout Social, GoHighLevel, Paylocity, Snowplow, and Circleback, 16 with polling triggers. See the [catalog](/apps).

## Team roles: custom member roles that your apps enforce

> Define your own roles, like Sales Rep or Finance, assign them to members, and apps you build show or allow things based on each person's roles.

Aug 31, 2026. Topics: Collaboration, Apps. https://www.generalinput.com/changelog/2026-08-31-team-roles

Workspaces can now define their own team roles, such as Sales Rep, Recruiter, or Finance, and give each member one or more of them. Apps use those roles to decide what each person sees and can do, so one app can serve a whole team with the right view for each person.

### How it works

- **Your vocabulary.** Team roles are names your workspace defines. They sit alongside, and never replace, the built-in Owner, Admin, and Member roles that control workspace permissions.
- **Assigned centrally, applied by each app.** You manage who holds which role in one place; each app decides what a role means for it, for example "Finance can approve refunds."
- **Delivered to every app.** App handlers, app agents, and app screenshots all receive the viewer's roles, and an app can read the live member roster instead of keeping its own copy.
- **Built into authoring.** The app builder can see your members and their roles while it builds, so you can ask for role-based behavior in plain language.
- **Permissioned.** Changing someone's roles requires permission to update member roles.

This builds on [apps knowing who's using them](/changelog/2026-07-20-apps-warm-servers-viewer-identity).

## Projects: one home for a goal's workflows, apps, and skills

> Projects, now specialists, group the workflows, apps, skills, files, and chats behind one goal, with sharing that flows to everything inside.

Aug 28, 2026. Topics: Specialists, Collaboration. https://www.generalinput.com/changelog/2026-08-28-projects

Projects shipped to every workspace. Projects, which have since become specialists, give a goal that takes several pieces one home: a skill holding the procedure, a workflow running it on a schedule, an app where someone reads the output, and the reference files behind all three. Start a chat inside a project and everything it builds lands there. Read the [Projects announcement](/blog/introducing-projects).

### How it works

- **One home per resource.** A workflow, app, or skill lives in at most one project, and you can move work in or out at any time.
- **Chats follow the work.** A chat that creates a project moves into it, and @-mentioning a project attaches its inventory to your message.
- **Access flows down, and the narrower setting wins.** Share a project as viewer, runner, or editor and the role reaches everything inside, while a resource can still carry its own narrower setting.
- **Chats stay private.** A conversation in a shared project belongs to the person having it; what the project knows lives in its memory and files.
- **Project memory.** Each project keeps its own memory, refreshed daily from its files, workflows, runs, and chats.
- **Everywhere you work.** Sidebar, search, @-mentions, the agent's tools, the MCP server, and the CLI.

Access rules are tested in CI against a real Postgres database: 90 tests cover every role, the workspace boundary, and every way of revoking access.

## Self-updating AI memory: Memory refreshes itself every day

> The knowledge base is now Memory: skill bundles every agent loads, revised daily by a memory agent that reads what actually happened in your workspace.

Aug 26, 2026. Topics: Agents. https://www.generalinput.com/changelog/2026-08-26-memory-daily-sweep

The knowledge base is now Memory, one name across the product: a Memory page in the dashboard, and workspace and personal memory available to every agent. The bigger change is that it no longer depends on someone typing facts into it. A memory agent runs daily for each memory, reads what happened since its last run, and revises it: confirming what still holds, changing what changed, adding what's new, and removing what's now wrong.

### How it works

- **Signals, not prompts.** Each run reads the team's chats, what was built, and what ran. If nothing happened, the run is skipped.
- **Requests, not notes.** What you type into the memory form, and what agents file with the `remember` tool, becomes a request the memory agent consumes on its next run. People's requests are instructions; agents' inferences are checked against the evidence first. No agent edits memory directly.
- **Shared memory is never about a person.** Workspace memory records how the business works and never stores names, emails, or phone numbers; facts about one person belong in their personal memory.
- **It does its own research.** The workspace memory agent reads what the company has published, starting from its website, and dates every claim so later runs know what to re-check.
- **A new page.** A timeline of everything that shaped the memory sits beside the memory itself.

## Workflows declare databases and browsers as credential slots

> Workspace databases and saved browsers are chosen in credential slots like integrations, and a workflow run can reach only the resources it declared.

Aug 24, 2026. Topics: Workflows, Security, Integrations. https://www.generalinput.com/changelog/2026-08-24-databases-browsers-credential-slots

Workflows, apps, and templates declare the integrations they need as credential slots. Databases and browsers now go through the same slots: the picker lists your databases and browsers beside your integration credentials, and publishing refuses a slot nobody filled. The result is that a workflow states up front every resource it touches, and the platform holds it to that list.

### How it works

- **One decision point.** A single service decides whether a slot is backed by an integration credential or a platform resource, so pickers, validation, publishing, duplication, templates, and app handlers all treat both the same way.
- **Keys scoped to the declaration.** The short-lived key a workflow run receives carries the resources it declared. A call to a database outside that set is refused with a message naming the slot to add, so an agent can correct itself.
- **Browsers only where declared.** A saved workflow can open only the browsers it declared, so every browser session traces back to a browser someone can point at.
- **Built-in services read as ready.** Services we host, like internet search, show as usable without asking you to connect them.
- **Migrated first.** Existing workflows that used a database or browser were updated to declare it before strict scoping turned on.

## Auto runs on your Token Tunnel subscriptions first

> With Claude, ChatGPT, Grok, or Gemini connected through Token Tunnel, Auto now runs on those subscriptions first and falls back to hosted models last.

Aug 19, 2026. Topics: Models. https://www.generalinput.com/changelog/2026-08-19-auto-routes-to-token-tunnel

Auto picks the model for each request. It now considers the models you've connected through [Token Tunnel](/token-tunnel) and prefers them: when a suitable one is online, Auto runs there, on the subscription you already pay for, instead of on a hosted model billed in credits. A Default to local models switch in the Auto menu controls it; it's on by default once you have a connected model.

### How it works

- **Tiers.** Auto classifies a request as an answer, an execution, or a build, mapped to Fast, Balanced, or Max. Anything it can't classify goes to Max.
- **A ladder per tier.** Each tier has an ordered list of Token Tunnel models, and every tier includes all four providers (Claude Code, Codex, Grok, Gemini), so a single subscription is enough.
- **Never a blocker.** If the switch is off, nothing in the ladder is online, or a lookup fails, the tier runs its normal hosted fallbacks.
- **Every subscription before the cloud.** When one subscription hits its limit mid-run, the run moves to the next online one, and falls back to a hosted model only after all of them are exhausted.

### Also shipped

- Smaller models that couldn't reliably finish agent work became opt-in, and anyone defaulted to one moved to Auto.
- Gemini 3.7 Flash replaced Gemini 3.6 Flash, and Settings, Models now shows who hosts each model and where.

## Weekly digest email of your workspace's AI activity

> Every member gets a weekly digest of their workspace's activity: runs, chats, runtime, and a team leaderboard, with starter ideas for quiet weeks.

Aug 19, 2026. Topics: Collaboration. https://www.generalinput.com/changelog/2026-08-19-weekly-digest-email

Since August 19, every member gets a weekly digest of what happened in their workspace: how much work their workflows and agents did, and how they compare with the rest of the team. It arrives on Wednesdays, covers the previous Monday through Sunday, and comes once for each workspace you belong to.

### How it works

- **Your numbers.** Workflow runs, chat messages, AI runtime, and tokens for the week, calculated the same way as the [Analytics](/changelog/2026-07-29-workspace-analytics-member-reports) page so the two never disagree.
- **A team leaderboard.** In workspaces with two or more members, the digest ranks the top five by runtime and shows where you stand if you're outside them.
- **Quiet weeks get ideas instead.** If a week was light, you get a starter digest with suggestions for what to try next rather than a page of zeros.
- **A notification, not marketing.** The digest reports your own activity, so it follows your notification settings (Settings, Notifications, Digests) and also appears in the app.
- **Sent once.** Each digest is claimed before it's sent, so nobody gets the same week twice.

## Browser use: AI agents that use websites with saved logins

> Agents now drive a real hosted browser for sites without an API, reuse per-site logins you save once, and pause so you can sign in from chat.

Aug 18, 2026. Topics: Agents, Integrations. https://www.generalinput.com/changelog/2026-08-18-browser-use-saved-logins

For work that has no API (a supplier portal, an internal tool, a retailer's product page), agents can now open a real hosted browser. Every member has a browser that keeps per-site logins: sign in to a site once, and later runs open already signed in. When a run lands on a sign-in page, it pauses, you sign in through a live view in the chat, and the run picks up with the result. Agents never ask for a password and never type one.

### How it works

- **Scripts, not clicks.** The agent writes and runs a Playwright script against the hosted browser, so one step can complete a whole browsing task instead of a model round trip per click.
- **Logins you can trust.** Each browser lists its sites and whether each is signed in. Before a login is saved, it's proven by loading a page that requires an account.
- **Watch and take over.** The live browser appears in the chat while the agent works, and you can take control.
- **Unattended runs fail clearly.** Saved workflows can't request logins; an expired one reports that it needs reconnecting.
- **Ground rules.** Page text is data, never instructions. Agents buy, send, post, or delete only when you asked for exactly that, and treat a CAPTCHA as a stop.
- **Metered by the minute** on top of sandbox time.

### Also shipped

- `geni browser` brings the same hosted browser to scripts on your machine.

## General Input MCP server for Claude and ChatGPT

> Connect Claude, ChatGPT, Claude Code, or any MCP client to General Input and get the full agent toolset: every integration, a sandbox, and building.

Aug 18, 2026. Topics: Developers, Integrations, Agents. https://www.generalinput.com/changelog/2026-08-18-mcp-server-full-agent-toolset

Connect once from Settings, then MCP, and Claude, ChatGPT, Claude Code, Codex CLI, or any other MCP client can work in your General Input workspace. The connector isn't a read-only window or a short list of popular actions: it mounts the full toolset our own agent uses, so the model in your AI tool can call any operation across your connected integrations, build and edit workflows, apps, and skills, run them, and read their traces. Read the [MCP announcement](/blog/general-input-mcp).

### How it works

- **Per-person sign-in.** The server URL names your workspace, and everyone signs in with their own account through OAuth, so each person gets exactly their own access.
- **One toolset, two surfaces.** The connector registers the same tools the in-product agent runs, so the two can't drift.
- **A persistent sandbox.** Each member's connector session gets a warm Linux sandbox that keeps its files between calls and is released after five minutes idle. Read-only calls never start one.
- **Credentials stay in the vault.** Secrets are injected inside the sandbox, scrubbed from output, and every use is audit-logged with the reason the model gave.
- **Interactive cards** where the client supports MCP Apps, like a Connect button for a missing integration.
- **Billing.** Reasoning runs on your AI tool's own model; sandbox time and platform services bill to the workspace.

## Per-seat Business plan pricing: $30 Pro or $100 Max per seat

> Self-serve plans are now one per-seat Business plan: Pro at $30 with 4,800 credits per seat, or Max at $100 with 16,000. Added seats are prorated.

Aug 17, 2026. Topics: Pricing. https://www.generalinput.com/changelog/2026-08-17-per-seat-business-plan

We replaced the flat self-serve plans with one per-seat Business plan in two tiers. Pro is $30 per seat per month and funds 4,800 credits per seat. Max is $100 per seat per month and funds 16,000 credits per seat. Both started at 5 seats and go up to 50; larger teams go through Enterprise. The free tier is unchanged. See the [pricing page](/pricing) for current plans.

### How it works

- **Seats are bought, not counted.** At checkout you pick a tier and a seat count. That number sets what you pay, how many members the workspace can hold, and how many credits arrive each month.
- **Membership changes never touch the invoice.** Inviting or removing someone doesn't change what you pay. Add seats on the plan card and the prorated difference is charged immediately, with the matching credits granted right away.
- **Existing subscribers keep their terms.** Workspaces on a retired plan renew against the plan they bought.
- **A calculator on the pricing page.** Choose a tier and drag the seat count to see monthly credits and estimated capacity in runs per day and hours saved, using a conservative 500 credits per hour.

## Embedded agents: launch AI agents from buttons in your apps

> Apps can declare agents anyone using the app launches from its interface, each a full agent workflow with its own sandbox, history, and approvals.

Aug 12, 2026. Topics: Apps, Agents. https://www.generalinput.com/changelog/2026-08-12-agents-embedded-in-apps

Apps can now declare background agents that someone using the app launches from a button: a Research button on each row of a lead table, a Draft reply button on each support ticket. An app agent is not a reduced version of a workflow agent. It follows the same agent workflow spec, runs in its own sandbox, and gets the same run history, streaming, approval steps, and billing. Ask for one in the chat panel next to your app, the same way you'd ask for a new chart. Read the [launch post](/blog/agents-inside-your-apps).

### How it works

- **Same files as an agent workflow.** Each agent lives in the app bundle with its inputs (the button's variables), model and time budget, and a written procedure.
- **The interface is the trigger.** App agents have no triggers of their own, and their connections must be the app's own, so the Integrations tab shows which agent uses each.
- **Owner's access, viewer's identity.** Anyone the app is shared with can launch an agent; it runs through the owner's connections and knows who launched it.
- **Guardrails.** Every launch is confirmed, since runs spend credits, and an app can run at most 25 agents at once. Agents write results back to the app's data.
- **Tested by the builder.** The app-building agent runs its own agents and reads their traces before handing the app over.

### Also shipped

- App containers ship with more libraries preinstalled, from data tables to Excel, Word, and PDF generation.

## Send messages to an agent mid-run without stopping it

> Message an agent while it works and your note lands at its next step, so it adjusts in the same run. Undo takes it back before it lands.

Aug 11, 2026. Topics: Specialists, Agents. https://www.generalinput.com/changelog/2026-08-11-queued-messages-mid-run

You no longer have to wait for an agent to finish before you correct it. Send a message while a run is in flight and it shows up as a dimmed Queued bubble. At the agent's next step, the message is added to the conversation and the agent responds to it in the same run. Changed your mind? Undo on the bubble, or Escape in the composer, takes it back and returns the text and attachments to the composer. Queuing works in chat and while building workflows, apps, and skills.

### How it works

- **Held apart until it lands.** A queued message is stored separately, so nothing that reads the conversation (the model, summaries, titles, exports) sees it early. It joins the conversation exactly once.
- **One entry point.** Every way a run starts or restarts checks the queue, and mid-run the agent checks it at each step boundary.
- **Nothing stranded.** If a run fails or is cancelled, queued messages become ordinary history; if it pauses for your input, the queue waits for the resumed run.
- **Undo is unambiguous.** Either the model never saw the message, or it's already in the transcript.

## Getting Started checklist that ticks itself off as you go

> A Getting Started checklist in the sidebar walks new members through six first steps and marks each one done the moment you actually do it.

Aug 8, 2026. Topics: Specialists. https://www.generalinput.com/changelog/2026-08-08-getting-started-checklist

New members now get a Getting Started checklist in the dashboard sidebar. It walks through six first steps: connect an integration, chat with the agent, install [Token Tunnel](/token-tunnel), build a workflow, build an app, and build a skill. Each step opens a short explanation with a button that takes you straight to the right page.

### How it works

- **It notices what you did.** Steps complete themselves when you actually do them, like connecting your first account or publishing your first app, so there's nothing to tick by hand. You can still mark a step done or finish them all.
- **Progress never goes backward.** Once a step is complete it stays complete, even if you later delete what you built.
- **Live updates.** The checklist refreshes every minute and whenever you return to the tab, and disappears once every step is done.
- **Clean new workspaces.** New workspaces start empty instead of seeded with example workflows, apps, and skills, so the checklist guides you to build your own.

Prefer a guided tour? The [crash course](/blog/getting-started-crash-course) covers signing up, connecting your tools, and shipping a workflow and an app.

## Workspace deletion: permanently delete a workspace

> Owners can now delete a workspace from Settings. It goes dark immediately, and its subscription, data, files, and schedules are removed for good.

Aug 5, 2026. Topics: Collaboration, Security. https://www.generalinput.com/changelog/2026-08-05-workspace-deletion

Owners can now delete a workspace from Settings. Confirm by typing the workspace's name, and it becomes invisible and inert immediately: members lose access, and nothing in it runs again. Its data is then removed permanently, not just hidden.

### How it works

- **Owner only.** Deleting a workspace requires the Owner role.
- **Outside services first.** The workspace's Stripe subscription is cancelled immediately, its hosted databases are deleted, and its stored files are swept from storage.
- **One transaction for the data.** Every record the workspace owns, from workflows and runs to connections, chats, and memberships, is deleted in a single ordered transaction, so a failure can't leave half a workspace behind.
- **Schedules stop.** Scheduled and polling triggers are removed once the deletion commits.
- **Nothing forgotten.** A test reads the database schema and fails if a new kind of workspace data is ever added without being covered by deletion.
- **Your account stays.** Deleting a workspace doesn't delete your account or your other workspaces; for that, see [account deletion](/changelog/2026-09-25-account-deletion).

### Also shipped

- New accounts verify their email address before entering the product, and accepting an invitation has a clearer screen.

## AI usage analytics per member, with PDF and CSV reports

> A new Analytics page shows who in a workspace uses AI and for what: per-member builds, runs, tokens, and credits, exportable to PDF or CSV.

Jul 29, 2026. Topics: Collaboration. https://www.generalinput.com/changelog/2026-07-29-workspace-analytics-member-reports

The new Analytics page shows who in a workspace is using AI and for what. It replaces the separate executions, usage, and security audit pages with one view, and adds a Members section that ranks every active member by what they built and ran.

### How it works

- **One page, one toolbar.** Executions (success rates, runs by workflow), usage (spend over time with receipts), and security (audit logs) share one time window, from 24 hours to 90 days, and a member filter.
- **The member table.** One row per member: the code workflows, agent workflows, apps, and skills they own, plus executions, chat messages, building iterations, tokens, and credits spent in the window. Columns sort, and pending invites appear on the workspace view.
- **Reports.** Export the table as a branded PDF or CSV. Each member also has a profile PDF covering their totals, what they've built, and a token breakdown by prompt, completion, cache read, and cache write.
- **Access.** Everyone can see and download their own row; seeing anyone else requires the usage audit permission.

### Also shipped

- Resource pages open full screen, and list pages became document-style lists with thumbnails.
- Update an API key in place instead of deleting and re-adding it, so bound workflows keep working.
- Sharing an app or skill sends its own notification with a direct link.

## Claude Opus 5 replaces Opus 4.8, and Kimi K3 arrives

> Claude Opus 5 takes over from Opus 4.8 at the same price with saved selections upgraded automatically, and open-weight Kimi K3 is now available.

Jul 28, 2026. Topics: Models. https://www.generalinput.com/changelog/2026-07-28-claude-opus-5-and-kimi-k3

Two hosted models landed at the end of July. Compare them on the [models page](/models).

### Claude Opus 5

Opus 5 replaces Opus 4.8 in the hosted catalog at the same rates: $5 input, $25 output, $0.50 cache read, and $6.25 cache write per million tokens. Every stored reference to Opus 4.8, like a member's default model or a workflow's configured model, now resolves to Opus 5, so nothing needs reconfiguring.

- A 1,000,000-token context window.
- Reasoning effort from low to max, defaulting to medium.
- If Anthropic is overloaded, runs fall back to GPT-5.6 Sol, then Gemini 3.5 Flash.
- Opus 4.8 remains available through Token Tunnel for members whose Claude plan still serves it.

### Kimi K3

Kimi K3 is Moonshot's open-weight model, available for chat, building, workflow runs, and as a utility model.

- A 1,048,576-token context window.
- Reasoning effort from low to max, defaulting to high.
- Image input.

Both models bill on actual cache reads and writes, like the rest of the catalog. Read why we think [running open-source models yourself](/blog/chinese-open-source-models-safest-cheapest) is a safe, cheap option.

## Faster apps: warm servers, viewer identity, and deep links

> App actions run on a warm per-app server, handlers know who is using the app, and every page inside an app gets its own shareable URL.

Jul 20, 2026. Topics: Apps. https://www.generalinput.com/changelog/2026-07-20-apps-warm-servers-viewer-identity

July reworked how apps run and how people move through them. Actions respond faster because they hit a server that's already up, app code can behave differently for different members, and any page inside an app can be linked to directly. See how apps fit into [agents inside your apps](/blog/agents-inside-your-apps).

### How it works

- **Warm per-app servers.** Each app gets one warm sandbox server shared by everyone using it, instead of a fresh sandbox per action. It starts on the first action, stops after five minutes idle, picks up new versions in place, and is replaced on any failure.
- **Viewer identity.** Handlers still run with the app owner's connections, but every call now knows who is using the app, so agents can build rules like "only I can delete" or "reps see their own accounts." Checks are enforced in server code, never by hiding a button.
- **Browser bar and deep links.** Apps get back, forward, and home controls, and the current page is reflected in the dashboard URL, so a copied link opens on the same page with the same filters.
- **Stays signed in.** Long-open apps refresh their session in place, without reloading or losing state.
- **Connections first.** An app with unconnected required integrations shows a connect screen instead of loading into errors.

### Also shipped

- Handlers can stop long requests early when the person closes the page.

## Token Tunnel: use your Claude, ChatGPT, Gemini, or Grok plan

> Token Tunnel connects the AI subscriptions you already pay for, so chats and workflows run on them with no API keys and no per-token charges.

Jul 19, 2026. Topics: Models, Platform. https://www.generalinput.com/changelog/2026-07-19-token-tunnel

[Token Tunnel](/token-tunnel) is available to every workspace. Install General Input Desktop, sign in to the AI subscriptions you already have (Claude, ChatGPT, Gemini, or Grok), and those models appear in General Input as your own. Chats and agent workflows run on them without an API key, usage isn't billed per token, and your provider logins live only on your computer. Learn more about [running local and personal models](/blog/what-is-a-local-ai-model).

### How it works

- **A menu bar app.** One universal macOS build for Apple Silicon and Intel. Sign in to General Input with a device code, then to each provider with its own login. The app auto-connects and updates itself.
- **The tunnel.** The app keeps an outbound connection to our gateway. When a run uses one of your models, the request is relayed to your computer, sent to the provider on your subscription, and streamed back.
- **Model sync.** Any model in our catalog that your subscription serves appears automatically, including models we don't host, like Claude Fable 5.
- **Explicit offline handling.** If your computer is off, chat says so immediately and never silently switches to a paid model. Agent workflows choose a policy: skip the run after retrying for 15 minutes, or fall back to a hosted model you pick.
- **Clear errors.** Rate limits, expired logins, and provider outages are labeled as such, and each device serves 10 simultaneous requests by default.

## Chat streaming that survives sleep and dropped Wi-Fi

> Chats now reconnect cleanly after a laptop sleeps or the network drops, showing every message exactly once while your run keeps working.

Jul 18, 2026. Topics: Platform. https://www.generalinput.com/changelog/2026-07-18-chat-streaming-reconnects

Long agent runs used to look broken at exactly the wrong moments: a laptop waking from sleep, a train going through a tunnel, a flaky office network. The chat stream is rebuilt so reconnecting is clean. Your run keeps working on our servers the whole time, and the chat catches up exactly where it left off.

### How it works

- **Every event is numbered.** After a reconnect, the chat applies only newer events, each exactly once, so text never appears twice.
- **Fewer, larger updates.** Text is batched into about 25 updates per second instead of one per token, in strict order with tool and status updates.
- **Dead connections are caught fast.** The server checks in every 15 seconds, and 40 seconds of silence forces a reconnect even when the browser thinks the connection is fine. A network change or a tab waking up reconnects immediately.
- **An outage isn't a failure.** During a long drop, the chat keeps retrying and says the connection is out while your run continues.
- **Specific errors.** A run that ends on a provider problem now says why, such as rate limited or provider unavailable, with a next step.

### Also shipped

- One memory-hungry command no longer takes down an agent's whole sandbox; only that command is stopped, with a note to process the data in smaller pieces.

## Auto model routing: the right model tier for every task

> Auto sends each run to a Fast, Balanced, or Max model tier based on the work, falls back across providers, and is now the default.

Jul 17, 2026. Topics: Models, Agents. https://www.generalinput.com/changelog/2026-07-17-auto-model-router

Most requests don't need the most expensive model, and some need nothing less. Auto now makes that call per run. It sits at the top of the model picker with three tiers (Fast, Balanced, and Max), and new members start on Auto everywhere. Members who already chose a default keep it.

### How it works

- **Fixed surfaces route directly.** Building or editing a workflow, app, or skill always runs on Max; agent workflow executions default to Balanced.
- **Chat is classified.** Your workspace's utility model sorts each message into build, execute, or answer, mapped to Max, Balanced, and Fast. A question about your own data counts as execute.
- **Fails up, never stops.** If classification fails, the run goes to Max. Routing can never block a run.
- **Sticky while warm.** A conversation stays on its tier for five minutes so follow-ups keep hitting the same prompt cache, and the choice is stored on the run so resumes stay consistent.
- **Outage-tolerant.** Each tier has a fallback list spanning three providers.

The classifier scored 50 out of 50 across three runs on an eval built from the real (anonymized) distribution of chat openers.

### Also shipped

- Grok 4.5, and the GPT-5.6 family (Sol, Terra, Luna) with 1M-token context windows.

## 500+ integrations: Workday, NetSuite, Okta, AWS, and more

> The General Input integration catalog grew from 275 to more than 500 in July, adding enterprise ERP and HR, AWS, payments, commerce, and AI services.

Jul 17, 2026. Topics: Integrations. https://www.generalinput.com/changelog/2026-07-17-integration-catalog-passes-500

Our integration count went from 275+ at the start of July to 500+ on July 17. Each integration ships with operation-level API documentation agents search, a setup guide, a credential check on connect, and poll triggers wherever the service has a real new-items stream. Browse the full [integrations catalog](/apps).

### What was added

- **Enterprise systems:** [Workday](/apps/workday), [NetSuite](/apps/netsuite), Microsoft Dynamics 365, SAP SuccessFactors, Coupa, Odoo, Brex, Mercury, Canvas, and Clio.
- **Developer and cloud:** AWS (S3, SES, SQS, Lambda, CloudWatch, DynamoDB), Azure DevOps, CircleCI, Snyk, LaunchDarkly, [Okta](/apps/okta), Auth0, Heroku, Render, Neon, and Firebase.
- **Payments and commerce:** PayPal, Adyen, Braintree, Paddle, Chargebee, BigCommerce, eBay, and Shippo.
- **Data and AI:** Databricks, ClickHouse, Fivetran, dbt Cloud, Pinecone, Vapi, Replicate, and DeepL.

### How it works

- **Validated on connect.** Adding a credential runs a minimum-privilege check and records account context for agents; keys with restricted scopes still pass.
- **Per-tenant OAuth.** Workday, NetSuite, Dynamics 365, and others collect your tenant or region before sign-in, so calls reach the right instance.
- **Triggers start from now.** New poll triggers baseline when enabled, so turning one on never replays a backlog.
- **Guardrails.** User-supplied hosts must match the provider's domains, and keys are scrubbed from error logs.

## Export and import workflows, apps, and skills as .zip files

> Move any workflow, app, or skill between workspaces as a .zip, and upgrade template-installed workflows in place when the template improves.

Jul 15, 2026. Topics: Workflows, Developers. https://www.generalinput.com/changelog/2026-07-15-export-import-and-template-upgrades

You can now move a workflow, app, or skill between workspaces as a file. Export downloads the resource's live bundle as a .zip; import validates it, shows a preview, and creates the resource. Credentials never travel in the file, so an imported workflow arrives ready for you to connect your own accounts.

### How it works

- **Export.** Anyone with read access can export. For workflows, you choose which setting values ride along, so workspace-specific values can stay behind.
- **Import.** Upload a .zip of up to 50 MB from the Workflows, Apps, or Skills page. Unsafe archives are rejected, the bundle is validated against that resource's spec, and nothing is created until you confirm.
- **Safe arrival.** Imported workflows arrive disabled, so nothing fires webhooks or polls before you review it. Missing connections show as needing attention, and a failed import leaves nothing half-created.
- **Portable skills.** Skills use the standard Agent Skills folder layout, so they move between hosts.

### Template upgrades

Workflows installed from a template now show their source and an upgrade banner when the author publishes a newer version. Upgrading snapshots your current code, applies the new version, keeps your connections, settings, triggers, sharing, and run history, and lets you roll back.

### Also shipped

- Template authors choose which setting values ship as defaults.

## Agent runs resume after restarts without repeating actions

> Every agent tool call with side effects is journaled, so a run interrupted by a deploy resumes without sending that email or creating that record twice.

Jul 15, 2026. Topics: Agents, Platform. https://www.generalinput.com/changelog/2026-07-15-tool-call-journal

An agent run can take many minutes, and occasionally one of our servers restarts in the middle of it, for example during a deploy. Until July 15, the resumed run could repeat a step it had already taken. Now every tool call with side effects is recorded in a journal before it runs and again when it finishes, so a resumed run picks up exactly where it left off.

### How it works

- **Journal before and after.** A tool call that changes something, like sending an email or updating a CRM record, is written to the journal when it starts and when it completes.
- **Rebuilt, not repeated.** After a restart, the run rebuilds its unsaved step from the journal instead of executing those calls again.
- **Uncertain calls are verified.** A call that was in flight when the server stopped is marked as uncertain, and the agent is told to check whether it happened before trying again.
- **Reads simply re-run.** Read-only calls have no side effects, so they're safely repeated.

### Also shipped

- Long conversations with many images stay under the context limit: image reads are stored as pointers to the file instead of inline data, and counted at their real cost.

## Voice dictation in every prompt box, with smart cleanup

> Every prompt box has a mic. Speech streams to live transcription, then a cleanup pass removes filler and applies your spoken edits.

Jul 8, 2026. Topics: Specialists. https://www.generalinput.com/changelog/2026-07-08-voice-dictation

Describing a workflow out loud is faster than typing it, but raw transcripts are full of false starts. Every prompt box in the dashboard now has a mic button: words appear as you speak, and when you stop, a cleanup pass turns the ramble into the prompt you meant and puts it in the box. It never submits for you. Read [why talking to agents is faster than typing](/blog/voice-dictation-faster-than-typing-ai-agents).

### How it works

- **Streaming transcription.** Your browser streams audio directly to AssemblyAI with a short-lived token; audio never passes through our servers, and a live strip shows the partial transcript.
- **Cleanup that edits.** On stop, your workspace's utility model removes filler, keeps only the corrected version when you change your mind mid-sentence ("make it a Google Sheet, no wait, a Slack message"), and applies spoken instructions like "delete the part about revenue charts" to what's already in the box.
- **Never loses words.** If cleanup fails, the raw transcript is added instead.
- **Everywhere you type.** Chat, workflow, app, and skill building, onboarding, and the new-resource dialogs.
- **Six languages.** English, Spanish, German, French, Portuguese, and Italian, detected automatically.

Transcription costs about $0.19 per audio hour, prorated per second.

## Agent skills: reusable SKILL.md instructions for every agent

> Skills are portable SKILL.md bundles in the open Agent Skills format that any agent loads when a task matches. Build them in chat or import a .zip.

Jul 7, 2026. Topics: Agents, Developers. https://www.generalinput.com/changelog/2026-07-07-skills-workspace-resource

Workflows and apps do work; skills teach agents how to do it. A skill is a `SKILL.md` instruction bundle in the open Agent Skills format: your email conventions, a report layout, a triage procedure, plus any scripts and templates that go with it. Skills now sit beside workflows and apps with their own page, every agent in the workspace can load them, and because the format is portable, a skill written here works in other Agent Skills hosts and the reverse. See why we favor [small agents over mega-skills](/blog/small-agents-not-mega-skills).

### How it works

- **The bundle.** `SKILL.md` holds a name and description, with optional scripts, references, and asset folders for runnable code, long reference material, and templates.
- **Progressive disclosure.** Agents see only each skill's name and description until one matches the task; then the body loads and its files are placed in the sandbox. You can also @-mention a skill to use it directly.
- **Validated on publish.** Every link inside the bundle must resolve, and a failed publish changes nothing.
- **Lifecycle.** Describe a skill and an agent drafts it, or import a .zip. Every publish saves a version, skills can be switched on or off, and they share like workflows.

### Also shipped

- The `geni` CLI authors skills with the same commands as workflows and apps.

## Prompt-cache-aware pricing for every AI model

> Every model now carries cache-read and cache-write rates, so each call is priced on what the provider actually served, and balances update live.

Jul 1, 2026. Topics: Pricing, Models. https://www.generalinput.com/changelog/2026-07-01-cache-aware-model-pricing

Agent runs resend the same long prefix on every step: instructions, tool definitions, and the conversation so far. Most of it comes back from the provider's prompt cache at a fraction of the input price. Every model in the catalog now carries four rates (input, output, cache read, cache write), and each call is priced on what the provider actually served.

### How it works

- **Three input buckets.** Uncached tokens bill at the input rate, cache reads at the cache-read rate, and cache writes at the cache-write rate. On Claude Sonnet 5, for example, input is $3.00 per million tokens and a cache read is $0.30.
- **More cache hits.** Each conversation's requests carry a session-affinity key, so providers serving open-weight models route a conversation back to the replica holding its warm cache. For Anthropic models we mark the end of the history as a cache breakpoint, so earlier turns read from cache on every step.
- **Pruning only when needed.** Old tool results are trimmed only when a conversation nears its context limit, since pruning earlier would invalidate the cache.
- **Auditable.** Every usage record stores its cache-read and cache-write counts.

### Also shipped

- Credits deduct while a run is in progress, and open dashboards update the balance live.
- Workflows that keep failing because credits ran out now pause with a notice saying how to resume.

## Claude Sonnet 5 becomes the default model; Opus 4.8 arrives

> Managed Claude models now run on Anthropic's API, upgraded to Claude Sonnet 5 and Opus 4.8. MiniMax M3 and GLM 5.2 also joined in June.

Jun 30, 2026. Topics: Models. https://www.generalinput.com/changelog/2026-06-30-claude-sonnet-5-default

On June 30 we moved our managed Claude models to Anthropic's own API and upgraded them in the same step. Claude Sonnet 4.6 became Claude Sonnet 5, Claude Opus 4.6 became Claude Opus 4.8, and Haiku 4.5 stayed as it was. Sonnet 5 is now the default model for chat and for building workflows and apps, and the agents in our built-in templates use it too. See all models on the [models page](/models).

### How it works

- **Nothing to edit.** Old model IDs resolve to the new ones, so workflows, workspace defaults, member defaults, and conversation model pickers that named Sonnet 4.6 or Opus 4.6 now run on Sonnet 5 and Opus 4.8.
- **Native effort.** Effort settings map to Anthropic's native effort parameter.
- **Pricing.** Listed at $3 input and $15 output per million tokens for Sonnet 5, and $5 and $25 for Opus 4.8. Both accept images and files.

### Earlier in June

- **MiniMax M3** replaced MiniMax M2.7, bringing a 512K-token context window and vision. Saved selections moved over automatically.
- **GLM 5.2** joined the catalog for agent work, with a 1M-token context window.

## Agent Firewall: per-operation API permissions for AI agents

> Agent Firewall lets you block reads, writes, or individual API operations per connection or workspace-wide, enforced before requests leave the sandbox.

Jun 26, 2026. Topics: Security, Integrations. https://www.generalinput.com/changelog/2026-06-26-agent-firewall

OAuth scopes and API keys are coarse. Connecting Google Sheets grants edit and delete on every spreadsheet, and an agent holding that credential inherits all of it. [Agent Firewall](/agent-firewall) moves the unit of control down to the operation: on any connection you can block whole categories (every write, every read) or individual operations, and admins can set standing rules across the workspace. Agents keep the access their job needs and lose the actions you never want them to take. Read [why scopes are the wrong unit of control](/blog/oauth-scopes-wrong-unit-of-control-for-ai-agents).

### How it works

- **Built on our integration docs.** Every documented operation carries an HTTP method, path, and read or write category, and every integration lists its domains, so rules expand into precise request matchers.
- **Enforced in the sandbox.** Outbound traffic passes through a proxy that checks each request against the rules. A blocked call gets a clearly marked 403 telling the agent which operation was denied and to ask a workspace owner.
- **Layered rules.** Workspace rules combine with each connection's own rules, so a member can't loosen a block an admin set.
- **Everywhere agents run.** The same policy applies in chat, agent workflow runs, and `geni exec` on your machine.

Find it in Settings under Agent Firewall, on each connection's page, and in the Integrations Tools tab.

## Workspace notifications delivered as Slack DMs

> Admins connect Slack once, members are matched by email, and each notification type can go to email, a Slack DM, or both.

Jun 25, 2026. Topics: Collaboration, Integrations. https://www.generalinput.com/changelog/2026-06-25-slack-notifications

Notifications used to go out by email only. A workspace admin can now connect [Slack](/apps/slack), and each member chooses, per notification type, whether it arrives by email, as a Slack DM from the workspace's bot, or both. That covers auto-disabled workflows, failed triggers, low balance, balance refills, revoked credentials, and workflows, credentials, or databases shared with you.

### How it works

- **One-click setup.** Add to Slack runs our managed Slack OAuth, or an admin can pick an existing Slack connection. The token is stored encrypted on a dedicated notification connection, separate from anyone's personal credential.
- **Automatic matching.** Members are matched to Slack users by email, admins can correct any match, and resyncs never overwrite a manual match. Members can send themselves a test DM.
- **Permissioned.** Managing the Slack connection requires a new Manage notification channels permission, held by Admins and Owners.
- **Independent channels.** Delivery fans out per channel, so a Slack failure never blocks the email, and email and Slack render from the same content.
- **Graceful failure.** An invalid token disables the workspace connection with a reconnect path, an unreachable member disables only their link, and rate limits never disable anything.

## Atomic app builds on a dedicated esbuild service

> App builds now run as queued jobs on their own service. A failed build keeps the last good version live, with build status shown as it happens.

Jun 24, 2026. Topics: Apps, Platform. https://www.generalinput.com/changelog/2026-06-24-app-builds-dedicated-esbuild-builder

Apps used to build on our API servers. An agent edit could trigger duplicate builds, concurrent builds were silently dropped, publishing cleared the running app until the next good build, and a crashed build could leave an app stuck on "building." We rebuilt the pipeline in two steps.

### Queued, atomic builds (June 3)

- Builds are queue jobs, one active build per app. Triggers that arrive mid-build collapse into a single rerun with the latest files instead of being dropped.
- Build output is written to a fresh location and the app switches to it only when the build succeeds, so a failed build leaves the previous version serving.
- The app pane follows build status (queued, building, ready, error) and swaps in the new version as soon as it's ready. Failed builds keep the compiler output for you and the agent.

### A dedicated builder (June 24)

- Builds run on their own autoscaling service, so bursts never compete with API traffic. The builder holds no credentials or database access and moves files through short-lived signed links.
- esbuild replaced Vite for bundling, and type checking reuses a warm TypeScript program, so library types are parsed once rather than on every build.
- Icon imports are rewritten per icon, cutting the icon library from about 4,500 modules to a few dozen.

## Workflow file uploads and optional settings and connections

> Workflows accept uploaded files as input, settings with defaults can be left blank, and connections can be optional so one workflow fits many tool stacks.

Jun 22, 2026. Topics: Workflows. https://www.generalinput.com/changelog/2026-06-22-workflow-file-inputs-optional-settings

Over June we loosened what a workflow needs before it can run. It can take files as input, its settings can be optional, and so can its connections, so one workflow can serve people with different tool stacks and a missing nice-to-have no longer blocks a run.

### File inputs

- An input marked as a file renders as an upload field on the run form, and the file lands in the workflow's workspace for code or agent steps to read. You can restrict the accepted type, such as PDF only.
- Multi-file fields accept several uploads at once.
- When the building agent tests a file input, it stages a real sample file, so tests match what real uploads do.
- Each run records the input it received alongside the trigger that fired it.

### Optional settings and connections

- A setting with a default can be left blank, and the run uses the default.
- A connection can be marked optional: the workflow runs either way, skipping the dependent step when the account isn't connected. Optional connections are labeled in the workflow view and in templates.
- The building agent reserves optional connections for secondary paths, never for something the core flow depends on.

### Also shipped

- Workflows with several triggers can tell which one fired.

## Build workflows and apps from Claude Code with the geni CLI

> Coding agents like Claude Code can now create, validate, publish, and test General Input workflows and apps from local files with the geni CLI.

Jun 20, 2026. Topics: Developers. https://www.generalinput.com/changelog/2026-06-20-geni-cli-workflow-app-authoring

The `geni` CLI can now author code workflows, agent workflows, and apps end to end. Local files are the draft: your coding agent edits them with its own tools, `geni resource validate` checks them without saving, `geni resource publish` makes them live, and `geni workflow test` runs the published version in the cloud. It's the same build loop the in-product agent follows, backed by the same server-side checks. See the [developer page](/developers).

### How it works

- **Lifecycle commands.** `geni resource` creates, pulls, validates, configures, and publishes any resource; `geni workflow` tests runs and inspects executions; `geni app` checks builds, runs handlers, and reads errors.
- **One validation path.** The CLI runs the same spec and type checks as the dashboard, so the two can't drift.
- **Access-checked.** Every command that takes a resource ID is checked against your membership, exactly as in the dashboard.
- **Byte-exact files.** Images and document templates survive pull and publish unchanged.
- **Full run traces.** `geni workflow execution --download` writes the run, logs, input, and agent thread to disk, the same trace the cloud agent reads when it debugs.

Developer docs cover every command.

## One AI agent on every surface, with skills loaded on demand

> The separate chat, workflow, app, and database agents are now one agent that loads authoring skills when a task or page needs them.

Jun 19, 2026. Topics: Agents, Specialists. https://www.generalinput.com/changelog/2026-06-19-one-agent-progressive-skills

We ran four agents: one for chat, one that built workflows, one that built apps, and one for database questions. Each had its own prompt, tools, and run lifecycle, so a fix to one often missed the others. They're now a single agent, and what changes between surfaces is the subject it's pinned to (home, a workflow, or an app), which decides its instructions, preloaded skills, and tools.

### How it works

- **Skills on demand.** Every conversation starts with the same base tools. Authoring tools sit behind skills, loaded when needed or automatically when you open a workflow or app, and they persist for the conversation.
- **Shared tools.** Per-type tools merged into resource-wide ones that behave the same everywhere.
- **Test runs in chat.** Tests stream live inside the conversation as an expandable card.

### Quality from evals

- New code and app eval suites, built from the same prompts the New Workflow and New App dialogs send, drove a round of prompt and scaffold fixes.
- Code workflows are type-checked on the server against the real runtime library before they're saved.
- A run stops with a clear message when the same tool hits the same error five times in a row.

### Also shipped

- Web search falls back across three providers when one is rate-limited.
- Interactive runs are capped per member and queue visibly instead of competing for workers.

## Global search across workflows, apps, connections, and files

> Search everything in a workspace from one box: workflows, apps, connected accounts, databases, members, and context files, with fuzzy matching.

Jun 11, 2026. Topics: Platform. https://www.generalinput.com/changelog/2026-06-11-global-search

As workspaces filled up, finding something meant remembering which page it lived on. Global search, added June 11, puts one search box in the dashboard header that looks across the whole workspace at once.

### How it works

- **Everything in one place.** Results cover workflows and apps, connected accounts, databases, members, and context files, each marked with its own icon so you can tell them apart at a glance.
- **Forgiving matching.** Search matches names and descriptions with fuzzy, typo-tolerant matching, and boosts results that start with what you typed, so the most likely match rises to the top.
- **Connections by what they're for.** Connected accounts match on their title, description, notes, and service, so searching "warehouse" finds the database connection you annotated that way.
- **People too.** Members match by name or by email address.

Combined with [notes on connections](/changelog/2026-03-19-connect-postgres-mysql-sql-server), it's the fastest way to find the right account for a task, for you and for the agent.

## AI agent memory: a summary of your workspace and you

> A memory agent keeps a short summary of your company and of you that every agent run loads, and opens detailed files only when needed.

Jun 7, 2026. Topics: Agents, Specialists. https://www.generalinput.com/changelog/2026-06-07-workspace-and-personal-memory

We rebuilt workspace and personal context into a memory system. Each workspace and each member now has a distilled summary of at most 200 words covering identity and working style: who you are, how you write, and the standing instructions you've given. Every agent run loads that summary, so agents know the essentials on every run without reading your whole knowledge base each time.

### How it works

- **Summary plus files.** Facts, processes, and reference material stay in context files, indexed by title and description, and agents open them only when a task calls for it.
- **One memory agent.** It seeds a nearly empty knowledge base with public research about your company, fills gaps in a sparse one, and distills a large, messy one into a few focused topic files. When notes conflict, the most recent thing you said wins.
- **Trustworthy sources.** Web content is treated as data, never as instructions. Researched claims carry their source, and personal facts come only from you and your connected data.
- **Refreshes on its own.** Your edits mark the summary stale, and a background refresh runs once changes have been quiet for a few minutes. You can also refresh on demand or turn automatic refresh off.

### Also shipped

- A redesigned Context page with Workspace and Personal views, an autosaving editor, and live refresh status.

## Custom integrations: connect any API-key or public REST API

> When an app isn't in the catalog, an agent turns its API docs into a private integration that works in chat, workflows, and apps.

Jun 3, 2026. Topics: Integrations, Agents. https://www.generalinput.com/changelog/2026-06-03-custom-integrations

Until now, an API outside our catalog meant filing a request and waiting. You can now add it yourself: in Integrations, choose New, then Custom Integration, and describe the API or drop in its docs. An agent drafts a private integration for your workspace, and once published it works everywhere a built-in integration does. Agents call it in chat, and workflows and apps declare it as a connection.

### How it works

- **Same structure as ours.** A custom integration has a description, an authentication definition, common docs (base URL, auth header, pagination, rate limits, errors), a setup guide, and one documented operation per endpoint, so agents call it as reliably as a catalog integration.
- **Reads any format.** Drop in an OpenAPI or Swagger spec, a Postman collection, a PDF, or plain docs, or just give a name or link and the agent researches the public reference.
- **API keys or public APIs.** Define one or more key fields and mark which are secret; secret fields are encrypted, scrubbed from output, and injected only at run time.
- **Publish when complete.** Publishing requires authentication, docs, a setup guide, and at least one operation; the agent tells you what's missing.
- **Workspace-owned.** Members connect their own credentials by following its setup guide.

Services that only support OAuth can still be requested through Integration Request.

## Apps: build internal tools and dashboards by describing them

> Describe a dashboard, lookup, or one-click action and an agent builds a working React app on your connected data, opened right from your workspace.

Jun 2, 2026. Topics: Apps. https://www.generalinput.com/changelog/2026-06-02-apps-internal-tools

Workflows run in the background, but some work needs a screen. Apps, available to every workspace since June 2, are single-purpose internal tools an agent builds for you: a dashboard over your CRM, a quick lookup across two systems, a one-click action your team runs every day. Describe what you need, and the app builder writes it, tests it against your real accounts, and publishes it to your workspace.

### How it works

- **A real app.** Each app is a React interface rendered in a sandboxed frame, with server-side handlers that call your connected integrations using your stored credentials. Handlers run isolated in a sandbox and are metered by runtime.
- **A component library.** Apps start from a shared set of tables with sorting and filter chips, tabs, detail views, and settings screens, plus CSV and PDF export.
- **Built and checked by the agent.** The builder runs handlers against the live app, reads its render errors and handler logs, and confirms each build before handing it over. Handler results can be cached for 15 minutes to keep apps fast.
- **Not a workflow.** Apps have no triggers or schedules; they connect only the integrations they need.

Apps have grown a lot since, from [warm servers and per-viewer identity](/changelog/2026-07-20-apps-warm-servers-viewer-identity) to [agents inside your apps](/blog/agents-inside-your-apps).

## Hour-long workflow runs and automatic sandbox failover

> Every run can now last 60 minutes, deploys finish in-flight runs instead of cutting them off, and runs fail over between sandbox providers.

May 30, 2026. Topics: Platform, Agents. https://www.generalinput.com/changelog/2026-05-30-hour-long-runs-and-sandbox-failover

Long runs used to stop for reasons that had nothing to do with the work. Code workflows were capped at 5 minutes and chat and scheduled runs at 10, a deploy could stop a worker mid-run, and a sandbox provider having a bad hour meant failed runs. Over May we lined all of those up.

### How it works

- **One 60-minute limit.** Chat, scheduled runs, resumes, follow-ups, and code workflows share a single 60-minute timeout. A run that hits it is recorded as timed out, separately from a cancel, and the error states the limit.
- **Deploys drain instead of killing.** On shutdown, a worker stops taking new jobs and finishes the ones it has, for up to an hour, so a deploy no longer cuts off a long run or its final file save.
- **Autoscaling.** The worker pool scales with load, waiting before scaling up so brief spikes don't overreact and before scaling down so bursts can finish.
- **Two sandbox providers.** Sandboxes run on E2B or a second provider, built from one shared image so every run sees the same packages, fonts, and tools.
- **Failover.** If the primary provider errors or isn't ready within its deadline (10 seconds by default), the run moves to the next provider automatically.

## Per-model reasoning effort, GPT-5.5, and Gemini 3.5 Flash

> The model picker shows an estimated price and an effort control using each provider's native levels. GPT-5.5, Gemini 3.5 Flash, and Kimi K2.6 arrived.

May 28, 2026. Topics: Models. https://www.generalinput.com/changelog/2026-05-28-model-effort-and-new-models

Choosing a model is two decisions: which model, and how hard it should think. The model picker now shows both, along with what each option costs, and five new models arrived during May. Compare them on the [models page](/models).

### How it works

- **Estimated price.** Models are grouped into Basic, Capable, and Advanced tiers, each showing an estimated price in credits per 1,000 tokens, weighted 10 to 1 toward input because agent turns read far more than they write.
- **Native effort levels.** The effort picker lists only the levels the model's provider accepts (low to xhigh for GPT, low to max for Claude Sonnet and Opus, minimal to high for Gemini Flash) and passes the value straight through.
- **Saved defaults.** Your default model is saved with its effort, separately for chat and for building workflows.
- **Switch mid-conversation.** Conversations can move between providers, with tool-call history normalized so the next provider accepts it.

### New models

GPT-5.5, Gemini 3.5 Flash, Kimi K2.6, Qwen 3.6 Plus, and GLM 5.1. Most open-weight models moved to Fireworks AI, and saved selections moved with them, so no workflow had to be reconfigured.

## Self-serve plans: sign up and start building, no waitlist

> Anyone can now sign up and start free with 800 credits, or subscribe to a paid plan through Stripe for discounted monthly credits.

May 26, 2026. Topics: Pricing. https://www.generalinput.com/changelog/2026-05-26-self-serve-plans

Until now, a new workspace waited on a waitlist or a sales conversation before it could run anything. Sign-up is now self-serve: pick a plan during onboarding and start building. Everyone still on the waitlist was approved when self-serve went live. Current plans are on the [pricing page](/pricing).

### Plans at launch

- **Free:** 800 credits to start, pay-as-you-go top-ups, one member, no card required.
- **Individual and Team:** a monthly credit grant at a discount to pay-as-you-go, for solo builders and for teams that share workflows and credentials.
- **Enterprise:** custom pricing, unlimited members, and on-premise deployment.

### How it works

- **Credits live in grants.** Every credit comes from a subscription payment, a top-up, or a promotion. A plan's discount is applied once, when money comes in, so a credit is worth the same wherever it came from.
- **Spend order.** Usage draws from the grant that expires soonest, so monthly subscription credits are spent before purchased top-ups. Subscription credits don't roll over; top-ups never expire.
- **Seats.** Seat limits count pending invites as well as active members.
- **Stripe.** Checkout and subscription management run through Stripe.

## General Input is CASA Tier 2 verified

> General Input passed CASA Tier 2, the App Defense Alliance security assessment Google requires for restricted Gmail and Drive scopes.

May 24, 2026. Topics: Security, Platform. https://www.generalinput.com/changelog/2026-05-24-casa-verified

General Input is now CASA Tier 2 verified. CASA (Cloud Application Security Assessment) is the App Defense Alliance's review, and Google requires it before an app can use restricted scopes such as reading and modifying Gmail or full Google Drive access. To prepare, we ran the platform through the same dynamic and static scans the assessment uses and fixed what they found across the API, the dashboard, and our edge.

### What changed

- **Error responses.** Server errors return a generic message; details are logged, never echoed back.
- **Logs.** Tokens, cookies, and secrets are redacted before a log line leaves the process.
- **Caching.** Every API response is marked no-store, since responses are private to a session.
- **Rendered output.** HTML produced by agents renders in a sandboxed frame with no access to the dashboard.
- **Transport and headers.** TLS 1.2 or later, plus a Content Security Policy, HSTS with preload, clickjacking protection, a strict referrer policy, and a Permissions-Policy that restricts 21 browser features.
- **Dependencies.** Packages with published advisories are pinned to patched versions.

### Also shipped

- Password reset by email.

## Collaborative workflow editing with live presence

> Shared workflows gain an Editor role, live avatars for who's viewing, and version checks that stop one save from overwriting another.

May 21, 2026. Topics: Collaboration, Workflows. https://www.generalinput.com/changelog/2026-05-21-workflow-editor-role-and-presence

Two weeks after sharing launched, a workflow can be shared with Editor access. Editors can change instructions, triggers, credentials, settings, and agent configuration, and can ask the agent to make changes. Once more than one person can edit the same workflow, collisions become possible, so this release also makes concurrent editing safe.

### How it works

- **Version checks.** Every workflow carries a version number, and each change is sent with the version the browser last loaded. If someone else saved first, you see "This workflow was changed" with a reload option, and your unsaved edits stay on screen so you can copy them.
- **Live updates.** Each save is broadcast to everyone viewing the workflow, and open tabs refresh only when they're actually behind.
- **Presence.** The workflow page shows an avatar for each member who has it open.
- **One agent at a time.** When another member starts the agent, everyone viewing attaches to that run and watches it stream, instead of starting a second one.
- **Admin access.** Workspace admins now get Editor access to every workflow by default.

## Persistent agent workspaces that survive restarts

> Every conversation and workflow run now has a persistent work folder, so agents resume with their files instead of starting over.

May 19, 2026. Topics: Agents, Workflows. https://www.generalinput.com/changelog/2026-05-19-persistent-agent-workspaces

An agent's files used to last only as long as one sandbox. Close the conversation, or follow up on a finished run, and its scratch files, downloaded data, and half-written scripts were gone. Now every conversation and every execution has a persistent work folder, and agents run code the way an engineer does: with bash.

### How it works

- **Saved and restored.** The folder is saved to storage about once a minute after changes settle, and restored when the next turn or run starts, so a crash loses at most about a minute of work. Workspaces hold up to 1 GiB, and binary files like spreadsheets and PDFs round-trip byte for byte.
- **Follow-ups keep context.** A follow-up on a finished agent run, or a run resuming after a question, continues with the previous files.
- **Bash as the primitive.** Agent workflow scripts run directly in shell, Python, or JavaScript, receive credentials as environment variables, and call platform services over HTTP.
- **Faster first answers.** The sandbox boots in the background while the model starts responding; only the first tool call waits.

### Also shipped

- Uploaded files stay on disk with a short reference in the conversation, so a large CSV no longer overflows the model's context.
- ffmpeg, ImageMagick, and YouTube tools come preinstalled in the sandbox.

## Over 100 new integrations and 344 workflow triggers

> May added more than 100 integrations and grew the trigger library from about 60 triggers on 20 services to 344 on 52.

May 17, 2026. Topics: Integrations, Workflows. https://www.generalinput.com/changelog/2026-05-17-integrations-and-triggers-expansion

More than 100 services gained connection support in May, taking the catalog past 240 integrations: data tools ([Snowflake](/apps/snowflake), Segment, Mixpanel, Amplitude), work apps (Pipedrive, ClickUp, Zoom, Xero), web data (Firecrawl, Tavily, Bright Data), voice (ElevenLabs, Deepgram), enrichment, and media monitoring. Over the same month, the trigger library grew from about 60 triggers on 20 services to 344 on 52, so more workflows can start from the event itself instead of a schedule that checks for it. Browse them in the [integrations catalog](/apps).

### New trigger services

- [GitHub](/apps/github) (14 triggers), [HubSpot](/apps/hubspot), [Salesforce](/apps/salesforce), [Zendesk](/apps/zendesk), Freshdesk, Front, [Linear](/apps/linear), Sentry, PostHog, [Calendly](/apps/calendly), Outlook, OneDrive, SharePoint, monday.com, [QuickBooks](/apps/quickbooks), Todoist, and YouTube.
- Recruiting and HR (Greenhouse, Workable, BambooHR, Rippling) and meeting recorders (Fathom, Grain, tl;dv, Read AI).
- Custom cron expressions alongside the minute, hourly, daily, weekly, and monthly presets.

### How it works

- **Resume from a watermark.** Triggers built on change feeds save their position after each successful check and continue from it, so no event is skipped or repeated.
- **Introspection.** Every new integration reads back the account and resources it can reach, so agents build against what exists.
- **One connection layer.** Every connection now runs through our own OAuth and credential system.

## geni CLI: your connected apps for Claude Code and Codex

> Install the geni CLI and Claude Code, Codex, or Gemini CLI can call any service you've connected, with credentials injected and scrubbed from output.

May 11, 2026. Topics: Developers, Integrations. https://www.generalinput.com/changelog/2026-05-11-geni-cli

`geni` is a command-line tool that gives an AI coding agent on your machine access to the integrations you've connected in General Input. Ask Claude Code to post in a Slack channel or pull last week's Stripe charges, and it finds the right credential, reads the operation's docs, and makes the call, without ever seeing the token. Install it from npm as `@general-input/cli` and see the [developer page](/developers).

```sh
curl -fsSL https://generalinput.com/install.sh | sh
geni login
geni skills install
```

### How it works

- **Browser sign-in.** `geni login` runs a device-code flow: approve in the browser, pick a workspace, and the CLI saves a session token.
- **Discovery first.** Commands list your credentials and each operation's exact request shape and environment variable names, so the agent doesn't guess URLs.
- **Secrets injected, then scrubbed.** `geni exec` resolves each credential in the cloud, injects it as an environment variable for one local command, and redacts it from the output.
- **Every use is logged.** Each credential must be paired with a reason, which lands in your workspace's credential access log.
- **Skills for your agent.** `geni skills install` teaches Claude Code, Codex CLI, Gemini CLI, and VS Code Copilot Chat how to use it.

## Share workflows and credentials with view and run roles

> Share workflows and connected accounts with members or the whole workspace. Runners use your credentials without ever seeing the secret.

May 7, 2026. Topics: Collaboration, Workflows. https://www.generalinput.com/changelog/2026-05-07-share-workflows-and-credentials

Until now, a workflow and every credential behind it belonged to the one member who built it. You can now share both the way you share a document: pick members or give the whole workspace access, then choose what they can do. The person who connected [Salesforce](/apps/salesforce) can hand a workflow to the team, and the team runs it without their own admin login. Read the [announcement](/blog/share-workflows-and-credentials).

### How it works

- **Workflow roles.** Viewers can open a workflow and its full run history; Runners can also launch it. Editing and managing access stay with the owner.
- **Credential sharing.** A shared credential can be selected in the recipient's own workflows, but the key or token stays encrypted and is only injected into the sandbox at run time, so nobody it's shared with can read it.
- **Scoped to the workflow.** A runner doesn't need a separate credential share; the credentials a shared workflow uses resolve for that workflow's runs only.
- **Enforced on the server.** Every action that changes a workflow or its runs checks access on the server, not just in the interface.

### Also shipped

- Make a copy of any workflow you can read; credentials you don't own are removed from the copy.
- Email notifications when something is shared with you, and runs record who started them.

## Failing triggers now pause instead of disabling workflows

> Poll triggers now retry transient errors and judge failures by HTTP status. When one gives up, only that trigger pauses and the workflow stays on.

Apr 30, 2026. Topics: Workflows, Integrations, Platform. https://www.generalinput.com/changelog/2026-04-30-failing-triggers-pause-not-disable

Poll triggers check a service on a schedule and start a run for each new item. When polling broke, we used to disable the whole workflow after three consecutive failures, whatever the cause, so a provider outage could switch off an automation its other triggers were still feeding. As of April 30, a failing trigger pauses only itself.

### How it works

- **Retries in place.** Network errors and timeouts get up to three attempts within a check, and an authentication error retries with a freshly loaded credential in case the token rotated.
- **Judged by status code.** Lost access (401, 403) or a deleted resource (404, 410) pauses the trigger after one failed check. Server errors are tolerated for 25 consecutive checks, other client errors for 3. A rate limit never pauses a trigger.
- **Only the trigger pauses.** The workflow stays enabled, its other triggers keep firing, and you get a notification naming the trigger and the reason. Editing the workflow after fixing the cause turns it back on.
- **A shorter lookback.** Checks look back one hour instead of 24.

### New triggers

[Google Sheets](/apps/google-sheets) row updates, [Airtable](/apps/airtable) records, [Jira](/apps/jira) issues, [DocuSign](/apps/docusign) envelopes, Ashby candidates, Ramp transactions, [Asana](/apps/asana) tasks, and PandaDoc documents.

## Prompt library: ready-made starting points for workflows

> Browse starter prompts by use case and integration, in the product and on the web, and turn one into a code or agent workflow in a click.

Apr 30, 2026. Topics: Workflows. https://www.generalinput.com/changelog/2026-04-30-prompt-library

Knowing what to automate first is often the hardest part. The prompt library, launched April 30, collects ready-made starting points by use case and by integration. Pick one and the builder starts from that prompt, so the first draft of a workflow is a click away instead of a blank page. The same library is public at [generalinput.com/prompts](/prompts).

### How it works

- **Lighter than templates.** A prompt describes the job rather than shipping a finished workflow, so the builder adapts it to your own tools and data as it builds.
- **Your choice of workflow type.** Turn a prompt into a code workflow for fixed steps, or an agent workflow for work that needs judgment.
- **Browse by use case or app.** Filter by category, and every integration's page lists the prompts that use it.
- **Part of onboarding.** Since May, new workspaces finish onboarding with a suggested first prompt.

### Also shipped

- App prompts in August: starting points for internal tools and dashboards, not just workflows.

## Human-in-the-loop approvals for agent workflows

> Agent workflows can pause at moments you define, ask for approval or a missing detail, and resume where they left off once you answer.

Apr 28, 2026. Topics: Workflows, Agents. https://www.generalinput.com/changelog/2026-04-28-agent-workflows-ask-before-acting

Some steps shouldn't run unattended: sending a draft to a customer, choosing which leads to contact, filling in a detail only you know. Agent workflows can now stop and ask. The run parks with a Paused status, the question appears on your hub and on the execution's page, and once you answer, the agent picks up exactly where it stopped.

### How it works

- **Opt-in per workflow.** You write when to pause, for example "Pause to confirm the draft email before sending," and the agent only gets the pause tool when pausing is on.
- **One question per item.** Three posts needing approval means three questions you page through; the run resumes only when every open question has an answer.
- **No question without a decision.** If a run finds nothing to approve, it finishes without asking.
- **State survives the wait.** The agent's files are saved while paused, and waiting time doesn't count against the run's time limit.

### Where you answer

The hub replaced the home page on April 22, with a Running panel and a Waiting for you panel that collects every open question. Executions open inside the workflow page, with a link you can share.

### Also shipped

- Stop any active execution; stopped runs get their own Cancelled status.

## Onboarding interview that teaches agents your company

> New workspaces start with a short interview that writes shared and personal context, so every agent knows your company, your role, and your style.

Apr 25, 2026. Topics: Specialists. https://www.generalinput.com/changelog/2026-04-25-context-onboarding-interview

Agents now carry what they know about you from one conversation to the next. Context holds two sets of files: workspace context every member shares, and personal context only you can see. On April 25 we made filling it in the first thing a new workspace does.

### The setup interview

- **Workspace interview.** It asks what the workspace is for, looks up public information like your website, product, and brand so you don't retype it, and plays back what it found for you to correct. It writes a General profile and, when there's a visual identity, a Design file that agents use for PDFs, decks, and emails.
- **Personal interview.** After you connect your integrations, it reads a snapshot of each account (Slack channels, Linear teams, GitHub repos, Gmail labels), asks about your role and working style, and writes your profile.
- **Free during onboarding.** Later updates from the Context page bill like any other run.

### How agents use context

Every agent run gets an index of context files with a one-line description each. Agents always read the General profiles and open other files only when a task needs them. Agents write to context when you ask them to remember something, and only Admins and Owners can change workspace context.

## Usage in credits, plus an Audit section for spend and access

> Balances now show in credits at 4,000 for $25, and a new Audit section breaks down credential access, spend, and run outcomes.

Apr 23, 2026. Topics: Pricing, Security. https://www.generalinput.com/changelog/2026-04-23-credits-and-audit

Billing now shows credits instead of dollars. The rate is fixed at 160 credits per dollar, so $25 buys 4,000 credits, and refills come in packs of 1,000, 2,000, 4,000, and 10,000. Every execution and agent run shows its cost as a receipt. See current plans on the [pricing page](/pricing).

### The Audit section

Three views cover your own activity or, with permission, the whole workspace, over the last 1, 3, or 7 days:

- **Security:** every time a credential was used, the service it belongs to, what used it, and why.
- **Usage:** spend grouped by category, such as AI tokens and platform services, with receipts linking each charge to the run or chat that caused it.
- **Executions:** completed and failed runs per workflow, with a success rate.

Each workspace-wide view has its own permission, so you can grant spend visibility without granting security logs.

### Also shipped

- Background AI work, like titling chats and summarizing long conversations, appears as its own category so it's easy to tell apart from your agent runs.

## Agent skills for PDF, Word, Excel, and PowerPoint files

> Agents load skills on demand to produce finished PDFs, Word documents, Excel workbooks, slide decks, on-brand designs, and email that renders everywhere.

Apr 23, 2026. Topics: Agents. https://www.generalinput.com/changelog/2026-04-23-document-skills

Ask an agent for a deliverable and you used to get Markdown or a hand-built HTML file. Agents now have skills: packaged instructions plus the tools to produce a specific kind of output, shared across chat, the workflow builder, and agent workflow runs.

### The skills

- **PDF:** extract text and tables, merge, split, watermark, run OCR on scanned pages, and create new PDFs.
- **Word, Excel, PowerPoint:** create and read .docx, .xlsx (with formulas and styling), and .pptx files, and convert any of them to PDF.
- **Brand guidelines:** pull a company's palette, fonts, and logo from its website and apply them consistently.
- **Email design:** HTML email that holds up in Outlook, dark mode, and Gmail's 102 KB clipping limit.

### How it works

- **Loaded on demand.** Agents see a one-line description of each skill and load the full instructions only when a task needs them, which keeps prompts short and cacheable.
- **Ready to run.** The sandbox ships with the document toolchain (pypdf, python-docx, openpyxl, python-pptx, pandas, LibreOffice, Tesseract) and 48 fonts preinstalled, so the first PDF in a run doesn't wait on installs.
- **Inline previews.** Files and images an agent creates render right in the chat.

## One-click integrations with scopes you choose

> Microsoft 365, Google Workspace, HubSpot, Salesforce, and dozens more connect in one click, with read, read-and-write, or custom scopes you pick first.

Apr 14, 2026. Topics: Integrations, Security. https://www.generalinput.com/changelog/2026-04-14-one-click-oauth-and-scopes

Connecting tools was the slowest step before a first workflow could run. Dozens of providers now connect in one click: pick the service, approve the provider's own consent screen, and you're done, with no app to register and no token to paste. That covers the Microsoft suite (Outlook, [Teams](/apps/microsoft-teams), OneDrive, SharePoint, Excel), the Google suite ([Gmail](/apps/gmail), Drive, Calendar, [Sheets](/apps/google-sheets), Docs), [HubSpot](/apps/hubspot), [Salesforce](/apps/salesforce), [Airtable](/apps/airtable), Box, Dropbox, [GitHub](/apps/github), [Linear](/apps/linear), QuickBooks, Shopify, and Stripe. Read the [release post](/blog/one-click-integrations-release).

### How it works

- **Scopes you choose.** Before authorizing, pick Read, Read and Write, or Custom, with each scope described in plain language. You can edit a connection's scopes later.
- **Agents respect them.** Before calling an API, the agent checks the granted scopes and asks you to adjust the connection instead of making a call that fails.
- **Healthier connections.** Simultaneous token refreshes no longer break single-use refresh tokens, disconnecting one Google app keeps the others connected, and deleting a credential turns off the workflows that depend on it.

### Also shipped

- More than 20 new integrations, including [Jira](/apps/jira), [DocuSign](/apps/docusign), [Asana](/apps/asana), Ashby, Bullhorn, PandaDoc, GitLab, and ZoomInfo.

## Choose your workspace's AI models, or bring your own

> A Models settings page controls which AI models a workspace can use, and custom models can point at any OpenAI-compatible endpoint you host.

Apr 4, 2026. Topics: Models. https://www.generalinput.com/changelog/2026-04-04-workspace-models

Workspaces now decide which AI models their agents use. A new Models page in settings lists every managed model by provider and lets admins turn each one on or off. Teams that already run an approved model in their own cloud can add it as a custom model, which is the bring-your-own-model path for regulated or cost-sensitive teams. See the current lineup on the [models page](/models).

### How it works

- **Two roles.** Agent models appear in the model picker for chat, building, and workflow runs. One utility model handles background work like chat titles and summarizing long conversations, where a fast, cheap model is the right choice.
- **Custom models.** Any OpenAI-compatible API: a base URL, model name, context window, and capability flags. Keys are encrypted at rest.
- **Checked before anything runs.** Enabling an agent workflow confirms its model is turned on for the workspace.
- **New models.** OpenAI's GPT-5.4, mini, and nano joined Claude, Gemini, and MiniMax, and DeepSeek V4 Flash and Pro arrived on April 24 with 1M-token context windows.

### Also shipped

- Your default model is saved per member, so it follows you across browsers and devices.

## Agent workflows: AI that follows your written procedure

> A new agent workflow type hands each run to an AI agent that follows your written procedure and makes judgment calls fixed code can't.

Apr 2, 2026. Topics: Workflows, Agents. https://www.generalinput.com/changelog/2026-04-02-agent-workflows

Until April, every workflow was TypeScript that ran the same steps each time. That suits moving data between apps, and breaks down on work that needs judgment: deciding which stories in a feed matter, triaging a reply, drafting a response. Workflows now come in two types. Code workflows work as before. Agent workflows hand each run to an AI agent that follows a written procedure, and you can switch a workflow between the types.

### How it works

- **Three files.** The same manifest code workflows use (credentials, triggers, inputs), a plain-English runbook, and an agent configuration with the model, a time limit, and a reasoning effort.
- **Scripts as utilities.** The builder writes a small helper script for each external call, and the agent decides when to run them. If a script breaks mid-run, the agent can fix it and the fix is kept.
- **A living runbook.** After each test, the builder writes what worked (endpoints, response shapes, working code) back into the procedure, so later runs follow it instead of exploring again.
- **Run history as context.** Agents can pull a workflow's recent executions to debug failures against real runs.

### Also shipped

- An Activity calendar of past and upcoming scheduled runs, and per-type email alerts.

## Shopify, Cal.com, Granola, Gong, and Fireflies triggers

> Workflows can now start from Shopify orders, Cal.com bookings, Granola notes, Gong calls, Fireflies transcripts, and Zoho CRM records.

Mar 31, 2026. Topics: Workflows, Integrations. https://www.generalinput.com/changelog/2026-03-31-new-triggers-and-polling-controls

Six more services can now start a workflow on their own events, which closes loops like booking, to CRM, to meeting notes without anyone copying data by hand. A [Cal.com](/apps/cal-com) booking can create a lead in your CRM, and the [Granola](/apps/granola) note from that call can update the record afterward.

### New triggers

- **[Shopify](/apps/shopify):** new, paid, fulfilled, cancelled, and refunded orders; draft orders; new customers; new and updated products.
- **Cal.com:** new and cancelled bookings, filterable by event type.
- **Granola:** new meeting notes. **[Gong](/apps/gong):** new calls and users. **Fireflies:** new transcripts.
- **[Zoho CRM](/apps/zoho-crm):** new leads, contacts, companies, tasks, and users, plus updated leads and contacts.

### Sturdier polling

- Every trigger filter accepts multiple values, so one Gmail trigger can watch several labels.
- A Triggers tab shows each check's status and item counts, with a Sync Now button.
- Webhook triggers can authenticate with a secret URL alone, so tools that only accept a URL can start workflows.

## Multiple workspaces on one account, with readable URLs

> One login can now join and switch between several workspaces, each with its own workflows, connections, role, and default models.

Mar 29, 2026. Topics: Collaboration, Models. https://www.generalinput.com/changelog/2026-03-29-multiple-workspaces

Until now, each account belonged to exactly one workspace, so accepting a second invitation failed. As of March 29, one login can be a member of any number of workspaces. That matters most for consultants and agencies who build automations for several organizations, and for anyone who wants a test workspace next to their team's.

### How it works

- **Memberships.** Each membership links a person to a workspace with its own role and status. Workflows and connections belong to the membership, so what you build in one workspace never shows up in another.
- **Switching.** A workspace switcher sits in the sidebar, and the dashboard opens on the workspace you used most recently.
- **Readable URLs.** Dashboard links carry a workspace name you can edit instead of an internal ID.
- **Default models per workspace.** Each membership sets its own default model for chat and for building. The system default moved to Claude Sonnet 4.6.

### Also shipped

- Chats get automatic short titles, unread markers, and live run status.
- Consecutive tool calls in a chat collapse into expandable groups.

## One-click OAuth, plus Zoho CRM, Dropbox, Airtable, and more

> General Input can now supply the OAuth app so members connect in one click, starting with QuickBooks. Seven new integrations joined.

Mar 26, 2026. Topics: Integrations, Security. https://www.generalinput.com/changelog/2026-03-26-managed-oauth-and-new-integrations

At launch, every OAuth integration required a workspace admin to register an app with the provider and paste in its credentials. That's still right for teams that want tokens issued to an app they own, but it's a lot of setup for one connection. As of March 26, General Input can supply the OAuth app itself, so members connect in one click on the provider's own consent screen, starting with [QuickBooks](/apps/quickbooks).

### How it works

- **Three tiers.** Every OAuth connection uses, in order: the member's own registered app, the workspace's app, then a General Input managed app. An app you bring always wins over ours.
- **Encrypted.** Managed client secrets are stored encrypted, like every other credential.
- **Setup guides as PDFs.** Every bring-your-own setup page can be downloaded as a branded PDF for whoever administers that system.

### New integrations

[Zoho CRM](/apps/zoho-crm), [Dropbox](/apps/dropbox), [Box](/apps/box), [Airtable](/apps/airtable), [Calendly](/apps/calendly), [Cal.com](/apps/cal-com), and QuickBooks, each reading your account's structure (folders, bases, event types) as soon as you connect. [Shopify](/apps/shopify) moved from an API key to OAuth.

## Built-in workspace databases for workflows and AI agents

> Every workspace can create hosted SQLite databases that workflows, agents, and members share, with a table browser and CSV export.

Mar 26, 2026. Topics: Workflows, Agents, Platform. https://www.generalinput.com/changelog/2026-03-26-workspace-databases

Workflows often need to remember things: which leads were already processed, when the last run happened, a running list someone wants to query later. Keeping that state used to mean wiring up a spreadsheet or an outside database. Every workspace can now create its own databases, and the Databases page is in the sidebar for all members.

### How it works

- **Hosted SQLite.** Each database belongs to the workspace rather than one workflow, so one workflow can write rows another reads.
- **Agent tools.** Agents can list, create, inspect, and query databases. They reuse an existing database before creating a new one, check the schema before querying, and add a unique ID column when a workflow must never process the same item twice.
- **When agents use it.** Ask an agent to "track," "keep a list of," or "remember" something, and it reaches for a database and links you to the table it wrote.
- **Browse and export.** View tables in a data grid and export any table to CSV.
- **Isolated by workspace.** Every query is checked against the run's workspace.
- **Metered.** Queries from workflow runs cost $0.000013 each.

## Integration API docs split per endpoint for sharper agents

> Agents now search integration docs one operation at a time and load only the endpoints a task needs, instead of a service's entire API reference.

Mar 25, 2026. Topics: Agents, Integrations. https://www.generalinput.com/changelog/2026-03-25-api-docs-per-endpoint

Until March 25, when the workflow builder or the chat agent needed a service, it loaded that service's complete API reference into its context, however few endpoints the task used. A large reference crowded out the conversation and made mistakes more likely. We split every integration's documentation into individual operations, one per endpoint, plus one shared section per service covering authentication, pagination, and error handling.

### How it works

- **Search, then fetch.** Agents search across all operations with hybrid retrieval (vector embeddings plus full-text) and get the top 10 matches grouped by service, then fetch only the operations they need.
- **Everything needed to call it.** Each fetched operation arrives with its service's shared section and the exact credential fields its code should read.
- **No more whole documents.** The path that loaded an entire reference was removed, so context holds only the operations an agent looked up.
- **Shorter prompts.** Moving reference material behind search tools also shortened the agents' standing instructions, which leaves more room for your conversation and your data.

Browse every documented integration in the [integrations catalog](/apps).

## Agents render PDF reports and slide decks in a real browser

> Files the chat agent creates are now built as HTML and exported through headless Chrome as polished PDFs and images, guided by reference designs.

Mar 24, 2026. Topics: Agents. https://www.generalinput.com/changelog/2026-03-24-browser-rendered-documents

Ask the chat agent for a report, a slide deck, or a one-page graphic, and it now designs the file the way a web designer would: as HTML and CSS, exported through headless Chrome inside its sandbox. That gives every file a real layout engine, with grids, web fonts, proper text wrapping, and inline SVG charts, instead of hand-placed coordinates.

### How it works

- **Formats.** Reports export as A4 PDFs, slide decks as 16:9 landscape PDF pages, and infographics or flyers as full-page PNGs. Raw data still comes back as CSV.
- **Clean page breaks.** Agents are instructed to keep tables, headings, and charts from splitting across pages.
- **A library of reference designs.** Agents search a library of example PDF reports, slide decks, graphics, CSVs, and HTML emails by description, read the closest match, and borrow its spacing, typography, and structure rather than copying it.
- **One rendering path.** This replaced the coordinate-based PDF library and the separate PowerPoint, Word, and Excel generators. Native Office files came back in April with [document skills](/changelog/2026-04-23-document-skills).

## Chat with AI agents in Microsoft Teams and Slack channels

> The General Input agent now answers Microsoft Teams direct messages and Slack channel @mentions, with files in both directions.

Mar 23, 2026. Topics: Specialists, Integrations. https://www.generalinput.com/changelog/2026-03-23-microsoft-teams-and-slack-channels

You can now work with the agent where your team already talks. It answers direct messages in [Microsoft Teams](/apps/microsoft-teams), can be @mentioned in [Slack](/apps/slack) channels to start a thread, and sends and receives files in Slack, Teams, and [Telegram](/apps/telegram). From any of them it can search, run, and build workflows.

### How it works

- **Teams in your own tenant.** An admin creates an Azure bot and Teams app in their own Microsoft tenant by following a step-by-step guide, so the bot stays under your organization's control.
- **Members matched by email.** Teams and Slack users are matched to workspace members automatically, and one admin setup covers the whole workspace.
- **Files and formatting.** Attachments are stored with the conversation so the agent can read them, generated files come back as attachments, and replies are converted to each app's formatting.
- **Slack threads.** Replies in a thread continue the same conversation.

### Also shipped

- Agent runs moved to dedicated worker servers, separate from the dashboard's servers.
- Stop now halts a run in progress, and failed runs show a Retry button.

## Connect Postgres, MySQL, and SQL Server to AI agents

> Connect your own Postgres, MySQL, or SQL Server database, and AI agents query it in chat or in scheduled workflows through a logged proxy.

Mar 19, 2026. Topics: Integrations, Agents. https://www.generalinput.com/changelog/2026-03-19-connect-postgres-mysql-sql-server

Your own databases are now connections like any other integration. Connect [PostgreSQL](/apps/postgresql), [MySQL](/apps/mysql), or SQL Server, and agents can answer questions from your data in chat or use it inside scheduled workflows. When you have more than one, type @ and the connection's name to point the agent at exactly the right one.

### How it works

- **Schema introspection.** On connect, we read the database structure (tables, views, column types, primary and foreign keys), so agents query tables and joins that actually exist instead of guessing.
- **A logged proxy.** Queries go through a General Input endpoint that opens the connection, enforces a 30-second statement timeout, and caps results at 10,000 rows. Every query is recorded in Access logs against the credential and the run that made it.
- **Notes on connections.** Any connection can carry notes, like "read-only replica; orders live in public.orders," which agents read when choosing a connection.
- **Standard settings.** Host, port, database, user, password, an optional Postgres schema, and SSL. SQL Server connections encrypt by default.

## General Input launches: AI-written workflow automation

> General Input is live in public beta. Describe an automation in plain English and an AI agent plans, builds, tests, and runs it.

Mar 17, 2026. Topics: Workflows, Agents, Integrations. https://www.generalinput.com/changelog/2026-03-17-general-input-launch

General Input is live in public beta. You describe a job in plain English, and an AI agent turns it into a workflow: a real program that runs on a schedule or in response to events, presented as a document you can read and edit rather than a flowchart of nodes. Read the [launch announcement](/blog/introducing-general-input).

### What you could do on day one

- **Plan first, then build.** The builder agent writes a narrative plan with chips for each connected account and setting, waits for your approval, then writes TypeScript and test-runs it in an isolated sandbox.
- **No fake data.** The builder may not mock responses or hardcode anything user-specific; recipients and search terms become configurable inputs.
- **Triggers.** Run from the dashboard or by HTTP, on cron schedules, or from Gmail, Google Calendar, Google Forms, Google Sheets, Reddit, RSS, and Stripe.
- **A chat agent** (then called Geni, today the Chief of Staff) in the dashboard, Slack, and Telegram that runs workflows and does one-off work with your connected accounts.
- **Built-in services and models.** Web search, scraping, AI, and image generation with no extra keys, and a choice of Claude, Gemini, and MiniMax models.
- **Templates.** Dozens of ready-made workflows for sales, operations, and customer success.

## A credential access log for every connected account

> General Input logs each use of a connected account: which credential, what used it, and a plain-English reason, all visible in Access logs.

Feb 26, 2026. Topics: Security, Integrations. https://www.generalinput.com/changelog/2026-02-26-credential-access-log

You should be able to answer "what touched my Gmail account, and why?" without reading code. Since February 26, every time the platform decrypts one of your credentials it writes a record, and the Integrations page has an Access logs tab that lists them all.

### How it works

- **A reason on every credential.** Each account a workflow uses is declared with a plain-English access reason the agent writes, for example "Fetch recorded sales call transcripts from Gong."
- **A record on every access.** An entry is written when a workflow run uses a credential, when a trigger checks a connected account for new items, and when we register a webhook with a provider on your behalf.
- **Encrypted at rest.** Credentials are encrypted with AES-256-GCM and decrypted only for the run that needs them, after checking they belong to the person running it.
- **Refresh tokens stay with us.** For OAuth accounts the server refreshes tokens itself and passes only a short-lived access token into the sandbox.

### Also shipped

- Publishing a workflow as a template packages only its code. Variable values and connected accounts stay in your workspace.

## Workflow triggers: webhooks, schedules, and app events

> Workflows start from a webhook, a cron schedule, or new items in Gmail, Google Sheets, Calendar, Stripe, Reddit, or RSS, and each item fires only once.

Feb 26, 2026. Topics: Workflows, Integrations. https://www.generalinput.com/changelog/2026-02-26-webhook-schedule-and-poll-triggers

A workflow is only useful if it runs at the right moment. By February 26 there were three ways to start one, and they are still the three trigger types today: a webhook, a schedule, or a poll that watches one of your apps for new items. The first polling providers covered new emails in [Gmail](/apps/gmail), new rows in [Google Sheets](/apps/google-sheets), Google Calendar events, [Stripe](/apps/stripe) charges and subscriptions, new subreddit posts, and RSS feeds.

### How it works

- **Webhooks.** Any workflow can be started by an authenticated HTTP request, and the dashboard's run form is generated from the workflow's input schema.
- **Schedules.** Cron expressions with a per-workflow time zone.
- **Shared poll sources.** Each source, such as an inbox or a spreadsheet, is checked once a minute no matter how many workflows watch it, and every item is recorded so it never fires twice.
- **Broken workflows stop themselves.** If a workflow's last three runs fail, it is turned off automatically and you are told why.

### Also shipped

- A Data captured tab shows exactly what each trigger received.
- A workflow can have several triggers, each enabled on its own.

## Built-in AI, web search, and scraping on one prepaid balance

> Workflows can call an AI model, web and image search, and a scraping proxy with no extra accounts, all paid from one prepaid workspace balance.

Feb 23, 2026. Topics: Pricing, Integrations, Platform. https://www.generalinput.com/changelog/2026-02-23-platform-services-and-prepaid-credits

Most automations need an AI model, a search engine, or a way to read web pages, and none of that should require signing up with another vendor first. Since February, workflows can use built-in platform services the moment they declare them, and all usage is paid from one prepaid credit balance you top up by card.

### How it works

- **The services.** An LLM with low, medium, and high intelligence levels, internet search, image search, web scraping that returns clean text or HTML (with JavaScript rendering for sites that block plain requests), and image generation.
- **Metered precisely.** Model tokens, sandbox time, and every platform call are recorded to the millionth of a dollar, and every run shows exactly what it cost.
- **Automatic top-up.** Set a threshold and an amount, and your saved card is charged when the balance drops below it. You get a notification each time it refills.
- **Stops before it starts.** With an empty balance, new runs, retries, and agent messages are refused up front rather than failing partway through.

### Also shipped

- Workspace members: invite people by email as an Owner, Admin, or Member.

## Integrations as curated API docs, not prebuilt connectors

> General Input integrations pair a secure connection with a curated API reference the agent codes against. Over 90 services were documented by February.

Feb 19, 2026. Topics: Integrations, Agents. https://www.generalinput.com/changelog/2026-02-19-integrations-documented-for-the-agent

Most automation tools can only do what their prebuilt connectors expose. In General Input, an integration is two things: a way to connect your account (OAuth or an API key) and a curated API reference the agent reads before writing code against that service. That means the agent can use almost anything the service's API supports. By February 19, more than 90 services were documented and close to 60 could be connected, including Google Workspace, Microsoft 365, [Slack](/apps/slack), [GitHub](/apps/github), [Notion](/apps/notion), [Stripe](/apps/stripe), and [Zendesk](/apps/zendesk).

### How it works

- **One record per service.** Each catalog entry holds the connection settings, a key setup guide, and the API reference, so the connection screens and the agent's docs never disagree.
- **Hybrid search.** The agent finds the right docs by meaning and by keyword, blending embedding similarity with full-text search.
- **No guessing.** The agent must read a service's docs before calling it, and if a service isn't documented it says so and suggests a documented alternative instead of inventing endpoints.
- **Docs that keep up.** Documentation agents research new services and audit existing docs against the live API.

## An AI agent builds, tests, and repairs your workflows

> Describe a workflow and an AI agent asks questions, writes the code, tests it against your real accounts, and repairs failed runs from their logs.

Feb 10, 2026. Topics: Agents, Workflows. https://www.generalinput.com/changelog/2026-02-10-agent-builds-tests-and-fixes-workflows

In General Input you don't write workflows; an AI agent does. By February 10 the agent could ask you structured questions mid-build, write the workflow, test it in the same sandbox production uses, and repair a failed run starting from its actual error.

### How it works

- **Questions as forms.** Instead of guessing, the agent asks clarifying questions, confirmations, and connection requests as widgets in chat, then resumes exactly where it stopped once you answer.
- **Tested against real services.** Test runs use your connected accounts, and the agent must read the output before it reports back. Its instructions forbid mock data and placeholder fallbacks that make a run look successful without doing the job.
- **Fix with AI.** Any failed execution has a Fix with AI action that opens a new conversation seeded with that run's state and logs.
- **Long conversations keep going.** When a conversation nears the model's context limit, it is summarized into the request, current state, pending work, and key decisions, and the agent continues from there.

### Also shipped

- Every agent edit saves a version you can restore.
- A model picker in chat, and a running total of what building a workflow has cost.

## Workflows run as real code in isolated cloud sandboxes

> From week one, General Input workflows were TypeScript programs written by AI, each run in a fresh, isolated cloud sandbox.

Jan 29, 2026. Topics: Workflows, Platform. https://www.generalinput.com/changelog/2026-01-29-workflows-run-as-code-in-sandboxes

We started General Input on January 24 with one thesis: instead of hand-maintaining hundreds of connectors that fall behind API changes, ship identity, triggers, and execution, and let an AI agent write the integration code each workflow needs. By January 29, every workflow was a real program running in its own fresh, isolated cloud sandbox.

### How it works

- **A contract plus code.** Each workflow pairs a short configuration the platform can read (steps, inputs, and the routes between them) with TypeScript the agent writes. The dashboard draws the workflow from the configuration without reading any code.
- **A fresh sandbox per run.** Every execution gets a new E2B cloud sandbox: the code is uploaded, dependencies install, and the run streams its progress live to the dashboard.
- **Files between steps.** Steps pass data as typed files, and the final files are the run's output, so results are easy to inspect and download.
- **Secrets only at run time.** A workflow records which connected account each step needs, never the secret. Credentials are decrypted for that one execution and passed into the sandbox.

The file layout has changed since, but the split between a plan the platform can read and code the agent writes has held from the first week.