Release notes

Forge changelog

Stable v6.79.5 is the recommended download. Beta v6.79.5 is opt-in and gets new features first. Download Forge.

  1. v6.79.5

    Stable

    When you open an older day, job, thread or project on a new computer, its agent history now comes from your account on its own, and the Agent Stream says "Bringing this day's agent history from your account…" while it does. This replaces the "Load it" link. Settings → Work data sync → Load older agent history still brings everything at once.

    A new computer now brings the last 30 days of agent history as intended, and the Catching up bar moves with your days and jobs too.

    Setting up a new computer no longer uploads all your files again straight afterwards, so your other computers no longer download them a second time.

  2. v6.79.4

    You can add a job on a personal account. Forge no longer asks for a company when your sign-in does not have one. The job stays yours, and it still backs up to your account. Jobs inside a company are unchanged: you see your own, and an admin can still see the company's backed-up jobs.

    If you are a Super Admin, My Issues has This tenancy, next to Assigned to me and Submitted by me. It lists the open issues for the company you are signed into, and you can assign an owner from there. Every issue card shows Owner: and the name. On a long issue, Resolve stays on screen while the write-up scrolls.

    A delegated day task keeps Cancel while the agent is still working. Discarding every saved key asks inside Forge, and a SuperGrok sign-in that needs you to connect again says so. Signing in with SuperGrok keeps your Google key, and it does not use a pasted xAI key at the same time. Turning SuperGrok off brings that pasted key back.

    A job shortlist leaves out ads that are already closed. A day that fails to load shows the reason, instead of a blank error.

  3. v6.79.3

    Setting up Forge on a new computer is quicker. If your account is on the newer sync, the new computer catches up in one pass instead of also running the older "Restoring work data" restore, and the Catching up window shows how far it has got.

    A new computer now brings the last 30 days of agent history instead of all of it. To bring the rest, use Settings → Work data sync → Load older agent history, or "Load it" in the Agent Stream, then reopen the conversation.

    Projects that have not changed are no longer sent to your account again, and tasks belonging to a job that was deleted before this computer saw it no longer show up as failures.

  4. v6.79.2

    Forge talks to your account less often. Saving or opening something no longer sends records your account already has, starting Forge no longer repeats its sign-in work every time it syncs, and your computer no longer downloads changes it made itself.

    Settings no longer shows agent activity as changes waiting to sync, or a partial backup, after it has already been saved to your account.

    The sync summary in the log now says how many records a catch-up brought in.

    Meetings no longer keeps trying to update a calendar invite you deleted in Google Calendar, and only updates an invite when something about it changed.

  5. v6.79.1

    Files no longer collide when Forge uploads the same file from two places at once, and a busy upload is tried again after a short pause instead of failing.

    Starting Forge no longer briefly switches off one of your AI provider keys while it reads your saved keys, so work that starts straight away is not interrupted.

  6. v6.79.0

    Faster start-up and safer file sync

    Forge now starts up with less waiting. It no longer re-checks your whole history for deleted items each day, it loads your project list more efficiently, and it leaves agent history until you open a day or the Agent Stream. The "Catching up" window only appears if catching up takes more than a few seconds.

    Files you change are now stored as separate versions in your account, so your other computers always get exactly the version that was recorded, even when two computers save the same file around the same time. This switches on automatically once your account supports it.

    Work that was on this computer but missing from your account now uploads straight away, instead of waiting for you to press Sync now.

    Settings → Work data sync is simpler. It shows one status, such as "Backed up to your account" or "Changes waiting to upload". Backup and restore happen on their own, so the old Add a New Device and Restore from account buttons now sit under a collapsed Recovery tools section for the rare times support asks you to use them.

    Log files are now named by your local date, so today's log is easy to find.

  7. v6.78.1

    Files now sync reliably between your computers. A file you edit uploads again, a file added as a thread reference reaches your other computer, and a file that cannot be downloaded is set aside instead of stopping the rest of your catch-up. Settings shows how many were set aside. Once, after your first full catch-up, Forge uploads your files again so every copy in the cloud matches.

    If you use Forge in more than one company on the same computer, each company's files now stay with that company and no longer hold up the other's catch-up.

    Starting Forge is steadier. If your computer is slow to unlock your saved keys, Forge waits and carries on by itself instead of losing access to them until you restart, and syncing starts either way.

    A task you complete on one computer shows as completed on the other, even if the other opened today's daily flow first. A project deleted on one computer disappears from the other, and deleting a project no longer shows an error when it worked.

    Forge now keeps a log file you can open from Settings, and a Detailed logs switch for when support asks for more. It turns itself off after a day. On Windows, Open logs folder now opens the right folder.

  8. v6.78.0

    Forge now catches up when you start it, sign in or switch accounts, and otherwise only when your other computer has changed something. Switching back to the Forge window no longer starts a catch-up, and the catch-up window only appears at start-up or sign-in. Everything after that happens in the background, with a short message when something arrives from your other computer.

    When something changes on your other computer, Forge brings over just that kind of work, such as a task, a job or a thread, usually within a few seconds. Your own changes are no longer downloaded back to the computer that made them, and saving a change sends only what changed. This makes syncing faster and lighter, especially while an agent is working through a day.

    A new computer now offers to restore your work even if Forge has already created today's day. Edits made after a task was dropped bring it back, deletions stay deleted, and a change made while another computer was offline still arrives once it uploads.

    A job's files always stay in that job's own folder on every computer, so output written on one computer shows up on the other.

    New projects and their steps now reach your other computers.

  9. v6.77.1

    Unexpected failures are filed on the Service Desk. An ordinary refusal is not sent on as a crash.

    Work you do on one computer now reaches the other. Projects, steps, jobs, days, and threads stay together, and a step waits until its project is on this computer.

    Forge tells you when a catch-up cannot start yet, for example when you need to sign in, you are offline, or an update is required. News that arrives while the window is in the background waits until you come back.

    Deleting a job, a day, or a thread on one computer is not brought back by the other. If your sign-in is no longer valid, Forge treats that as a sign-in problem. A job folder opens on the first try.

    A Gmail action that gets stuck fails instead of freezing the morning briefing. The Gmail connection stays with the person who granted it.

    When a project sync or a sign-in download fails, Forge records it so it can be looked at.

  10. v6.77.0

    • Meeting captions stay with the person who was speaking. A guest can open the room from the link in the email. Long recordings are saved in pieces so a long meeting does not fail to save. On a Mac, the meeting window can go fullscreen when the system window has no fullscreen control of its own.
    • Forge now keeps an organisation report library. Pulse, sealed days, and the sample week are included. Missed mornings are caught up, and a day that has not been signed is not emailed. When a board sitting opens, the sealed quarter and year are attached to the board pack.
    • You can ask Marcus, and two other seats you choose, from inside Forge. Every director is on the same voice roster as the daily cast. Forge asks before a persona is archived. Voice and slider settings you set for the Business cast stay in place, including when they are updated from the portal.
    • If the morning briefing already ran in the portal, Forge will not start a second one for that day.
    • A new job records who created it. My jobs shows that person's jobs. An admin can open a company job to look at it, without that job becoming theirs.
    • A project is seen by its creator, the people assigned to it, and an admin of its company. Signing in downloads that company's projects. Archiving or restoring a project on this computer is not replaced by an older copy from the cloud.

  11. v6.76.2

    The API key security update now says plainly what is happening. Forge is moving your saved API keys into your computer's secure storage, and they stay on this computer. If your computer asks for permission, choose Always Allow so it does not ask again. If you choose Not now, Forge asks again the next time you sign in.

    On a Mac, allowing Forge to use a saved key lasts across later Forge updates, until you remove that permission in Keychain Access.

    A provider you have switched off is not loaded when you sign in. Forge does not call it, and does not tell you it is out of credits.

  12. v6.76.1

    Forge checks each provider key with its provider before the key syncs between your computers. A key the provider rejects is not sent, and a rejected key from another computer does not replace a working one here. Forge tells you when either happens.

    Settings shows whether each provider key is ready, rejected by the provider, or saved but not yet checked.

    A key no longer disappears from this computer because it is missing from your account's copy. When you remove a provider, its key is also removed from your other synced computers.

    Signing in no longer shows "Daily Flow: Not authenticated".

  13. v6.76.0

    Provider keys on this computer can move into the system credential store. Forge asks before an existing vault moves. A new account uses the system store directly.

    Signing out clears those keys from the running app. You can remove this account’s keys from the computer. Uninstall can leave them in the system store.

    If an older Forge no longer has this computer’s vault file, it does not see those keys. Keys that were synced come back from your account. Keys that were never synced do not. A reinstall that loses Forge’s saved record on this computer can fill the keys from your account again.

    While Forge is open, each saved key asks the system once. Choose Always Allow and the next open does not ask for that key again.

    The crash-report question waits until you are signed in. It names the error name, the function names, and the app version. It does not include the raw error text, the business name, the email, or files.

    If a newer version is ready, you can install it from the sign-in screen.

  14. v6.75.0

    This release is for operators who run meetings, hunt, and browse in the same sitting. Invites mean a send. Career keeps the hunt pack. Browser pages stay as tabs. Clara works the page she already has. Live Voice closes when you walk away, and greets the day you can see.

    Meetings

    Send invites is the only action that emails a guest and places the sitting in their diary. Adding someone to People lists them as Not sent. Copying the guest link is a backup, not a send. Invited means the invite left Forge.

    Guests can Accept in Forge or from the calendar email. Accept records Yes for the host and writes the sitting to the guest’s connected calendar. The host People list then shows Confirmed.

    An Accept invite bar can appear at the top of Forge as soon as you have an unanswered invite. When the sitting is close, that bar becomes Join now.

    Join asks for the microphone and the camera separately. Declining the camera no longer ends the room. You can still join on audio.

    Career and Daily Flow

    Hunt work lives on the Career thread until you Approve & send. Cover letters and shortlist files no longer wander onto a Daily Flow folder when the day rolls, and they are no longer attached as empty PDFs.

    A shortlist review can move into Career and back to the day without losing that pack. Monday’s hunt is not held back by older unsent applications.

    Ask Clara to open a named file, and the editor opens it. Asking her only to move to Daily Flow, Career, or another view changes the screen and leaves the editor alone.

    Ask her to make a PDF from a file you already have, and she exports that file — the same idea as Export PDF in the editor.

    Overnight, unfinished work still carries forward. It no longer appears twice.

    The activity row names who is working.

    Operator Browser

    Each page is its own tab. Click a tab to return to that page. A link that opens a new window becomes another tab; it does not replace the page you were on.

    Clara can attach a file from the workspace to a Browse or upload control on the page. Typing Backspace in the browser address bar or a page field no longer deletes a file that happens to be selected in Explorer.

    Clara is paced so she searches and changes view a limited number of times per turn, then reads the page she already has. Work on the live page is not capped.

    Voice

    Voice On hangs up after three minutes of silence, or if Forge cannot see you for a minute. Meetings are exempt, so Clara can sit quietly through the agenda. On a local rebuild, Voice On hangs up so a leftover session does not keep billing. A hangup you asked for does not show “Voice connection lost.”

    Turn Voice On on Daily Flow and Clara greets for the day in front of you, including after a rebuild.

    Follow Up on a task returns to that card and that conversation. Voice On resumes it. Following up a different person, or using a stream tag, still starts their own conversation.

    Observatory

    Live Daily Flow tasks stay on the Observatory. Follow Up does not create a second row for the same task.

    What to do

    1. Update Forge.
    2. Add a guest to a meeting. Confirm Not sent, then Send invites, then Invited.
    3. Join a room, decline the camera once, and confirm you remain in the sitting on audio.
    4. If you are the guest, Accept invite and confirm the sitting appears on your calendar and as Confirmed for the host.
    5. On Career, write or review a shortlist letter, roll or change day, and confirm the letter is still on Career until Approve & send.
    6. Ask Clara to move to Daily Flow without opening a file; then ask her to open a named file and to export that file as a PDF.
    7. In Operator Browser, open two pages, click the tabs, type Backspace in the address bar, and attach a file on a page that asks for one.
    8. Turn Voice On on today’s Daily Flow. Confirm the greeting. Follow Up a task, then Voice On again — same conversation. Leave Voice On idle past three minutes and confirm it hangs up. In a meeting, confirm quiet agenda time does not hang up.

  15. v6.74.0

    The person you are talking to is the same person if you type or speak. Follow Up goes back into the work you already started. The day title reads the way dates read where you are.

    The same person, typed or spoken

    Clara, Patrick, Aurora, Atlas, Quill, Lens, and the rest of the cast each keep one conversation. A line you type is part of the same memory as a line you say, and the other way around.

    Voice On uses whoever is already on the face. If you are with Patrick, you hear Patrick. Back to Clara returns you to Clara.

    Type @patrick (or any name) and finish the sentence before you send. The stream stays where it is until you send. Then that person takes the thread.

    Follow Up on someone’s existing work reopens that thread. It does not start a second copy of the same briefing or inbox chat. A new row appears only when the work itself is new.

    Dates and draft cards

    The Daily Flow day title follows your computer’s region. In Australia that is 6 Oct 2026. The record underneath stays the same calendar day, so overnight tasks still roll forward correctly.

    On Drafts awaiting approval, the attachment links sit on the same line as Discard. The card is shorter. Open, Attach, and Approve & send are unchanged. Approve & send is still the only send.

    What to do

    1. Update Forge.
    2. Open today’s Daily Flow and check the day title reads naturally.
    3. Follow Up on an existing task, talk or type, then Follow Up again. It should be the same thread.
    4. Turn Voice On with that person on the face. Ask them something you just typed.
    5. On a queued letter, confirm the attachment sits with Discard, then Approve & send only when you mean to send it.

Showing the latest 15 of 141 releases. Full release notes on GitHub.