What shipped

When inviting another company, choosing a share preset used to collapse the picker into a badge, and changing your mind meant finding a “Change” button first. The picker now stays on screen so you can switch presets freely.

Reviewing which projects someone can reach, and cutting them from specific ones, now lives under Settings → Members alongside the rest of your organization's people, instead of a separate Permissions page.

A shareable invite link now shows when it expires — “Expires in 13 days”, “Expires tomorrow” — so you can tell at a glance whether a link you sent is still a way into your project.

A preset that granted more than can be shared across organizations was quietly left out of the list when you connected with another company, with nothing to say why. Those presets now appear greyed out and name the areas holding them back, so you can go and narrow them.

Naming a preset the same as an existing one said only that the name was in use. It now tells you whether the preset already using that name is an internal or an external one, so you know where to look.

Marking a preset for sharing with other organizations while it still grants something that cannot cross that boundary is now caught as you save it, naming what to remove, instead of only surfacing later when you tried to use it.

A preset you share with another organization can now let them respond on submittals and RFIs, not just read them — they can answer the records they are actually a party to, on the project you shared. Raising new submittals or RFIs, and seeing who else is on the project, stay with your own team.

A project's Team panel had two separate buttons for putting someone on the job — one for your own colleagues, another for outside companies — so you had to decide which kind of person you were inviting before you could start. They are now a single “Invite to collaborate” button, with a Your company / Another company switch inside. Same two ways to invite, no longer a fork in the road before you begin.

On a project's Team panel, your own people are listed together under your organization at the top, with outside companies below. Anyone from your company who also had a contact card was being filed among the outside companies instead, sorted in alphabetically as though they were a counterparty.

The public About page now introduces the three co-founders by name, role and photograph, each with a link to their LinkedIn and a direct email address. The page used to describe the team without ever showing it.

The public site now follows your device's light or dark setting, and a control in the footer lets you pick a look yourself — the same Day, Cloudy, Night and Rainy themes the app carries — so you can see what you will get before you sign in. Your choice is remembered on that device.

When you invite a company by email, what they can see now follows the role you give them: invite a general contractor or a sub to work on construction and they land on the construction phases, while an architect also keeps the design phases they author. Invite links do not carry this yet. You can set what any company sees at any time from their panel on the Team tab.

The panel for a connected company now matches the one for a person on your team: removing their access sits at the bottom, under everything it affects, instead of beside the company name. If removing a company fails, the confirmation now stays open and tells you why, instead of closing as though it worked.

Open a submittal or an RFI and the page now leads with where the record is — a lifecycle strip from Drafted to Closed, with a rejection shown as the stop it is — and, when the next move is yours, a highlighted action block for your review, approval or response, with what that action commits you to spelled out beside the buttons. The review chain or response thread takes the wide column, the details sit alongside, and closing or recalling a record moves to the top corner where it no longer leads the page. Reviewers and authors get initials and a stacked name-over-company cell, and a step still waiting reads as amber Awaiting instead of gray Pending.

The free-text Cost Code box is gone from the RFI form. Assign a trade by choosing its Rhett code — search by trade name or paste an industry code — so two RFIs on the same trade can never spell it differently. Older RFIs that carried a typed cost code still show it.

The Spec reference field on the ASI form now searches your project manual, so you can pick the governing section instead of typing its number. When the reference resolves to a section in the current spec book, the ASI page links straight to it in Specifications.

The design team can now issue formal supplemental instructions to the field — the outbound mirror of RFIs. Create a draft, name recipients, attach project files and drawing sheets, then issue to allocate a number and publish selected revisions. Served parties acknowledge on their own row and can file or update an impact claim while the instruction stays open. Track every ASI and ESI in a project register with distribution and acknowledgment status. The assistant can draft and queue changes with your approval.

Construction projects get a daily log: one entry per day covering manpower, weather, visitors, delays, deliveries and notes, plus photos. Fill it in over the course of the day and complete it when the day is done — a completed day is a claims record, so it locks and cannot be reopened.

Site conditions now lead with the current temperature, a matching icon and today's high and low, and add an hour-by-hour temperature curve with the chance of rain — so you can see how the rest of the shift looks at a glance. A new Week view shows the next seven days. Active weather warnings now sit at the top of the card, where they cannot be scrolled past. As before, this is a live National Weather Service feed and is never part of the logged record.

A thumbs-up on an answer now turns green and a thumbs-down turns red, instead of both going the same grey. The highlight that used to linger after you cleared a rating is gone.

The button that jumps to a change you approved is no longer a filled green chip competing with the answer beside it — just a link in the app's green.

“Hello, [name]” at the top of a new chat was rendering in a serif that appeared nowhere else, which read as a font failing to load. It now uses the same typeface as everything around it.

Both windows opened with a strip of blank space above their content — worst on the shorter one. Content now starts at the top.

Clicking New chat cleared the notification count from the browser tab — both the number in the tab's name and the dot on its icon — even when the notifications were still unread. Both now survive moving around the app.

Creating a project from the Projects panel left it missing from the sidebar until you reloaded the page. It now appears immediately, from either place you can create one.

On the Team roster, a company row's access chip describes what a connected organization has been granted — so your own organization's row, which is never "connected" to itself, wrongly showed "No access" on a project it owns. Company rows without a connection no longer show an access chip at all.

Archiving a project makes its access management read-only, as it should: the Team panel no longer offers Add members, Connect organization, or access editing on an archived project, and a notice at the top of the roster says why. Restoring the project brings everything back.

The Team panel's Add members dialog now shows your whole organization as a checkbox list — type to narrow it, tick everyone who belongs on the project, pick one access level, and add them all together. No more searching people out one at a time.

On a person's card, the linked-account row now shows just the badge. The Message and View messages buttons were duplicates of the messaging pane sitting right beside the card, and the unlink control was one mis-click away from disconnecting the account — unlinking now lives in the contact's edit view, where deliberate changes belong.

The Specification field on the RFI and submittal forms now searches your project manual, so you can pick the governing section instead of typing its number from memory. The RFI opens straight to that section, and you can still type anything you like — the field never stops you.

Open any section in Specifications and it now lists the RFIs and submittals that cite it, each one a click away. If you don't have access to RFIs or submittals on the project, that list says so rather than pretending there are none.

Settings → General now has a Code system preference, so the spec book opens in Rhett codes or industry codes the way you actually work. Switching it here or in a spec panel changes it everywhere, on this device.

Project access is now managed in one place: the Team panel. The separate Settings → Access section is gone — see who has access in the roster's access column, adjust a person's level from their card, and manage a connected organization from its company row. Incoming connection invites appear at the top of the Team panel too.

After you approved a change Rhett proposed to a specification section, the Specifications panel kept showing the old text until you reloaded the page — so an edit that had actually been saved looked like it had been lost. The section and the spec book now update as soon as the change is approved.

If someone approved a change to a specification section while you had that same section open in the editor, saving your edit used to silently overwrite the approved text. RhettWorks now stops the save and tells you the section changed, so you can copy your work, then close the block to load the updated text before deciding what to do.

When Rhett drafts or revises a specification section it now follows the standard outline — PART, article, paragraph, subparagraph — instead of running the requirements together as plain paragraphs. Sections it writes are now collapsible and can be edited block by block, the same as an imported spec book.

A request that pulled in too much at once — a long conversation, a large attachment, or a whole spec book — used to fail with only "Something went wrong". It now says the request was too large and lists what actually helps: a shorter message, removing a big attachment, or asking for a narrower slice. There's a New chat button right on the message if the conversation has simply grown too long.

If an approval landed while the Overview panel was still opening, sections could sit on "Loading…" forever with no way back except reloading the page. They now show a clear error with a Retry button. Opening a project that has since been deleted shows only the "no longer exists" message, instead of leaving the old team and task lists on screen underneath it.

Deleting a phase that still had tasks used to fail, telling you to move or delete every task first. Deleting a phase now works: any tasks inside it move to the end of that stage, where you can re-file them wherever they belong.

When Rhett notices it is not helping — you have corrected the same thing twice, it contradicted itself, or something it needed simply failed — it now offers a report already written up for you. Nothing is sent until you read it and press send, and you can change every word first. Previously the reports we most wanted to see were the ones you had to remember to file yourself.

The project's Team panel now carries every way to bring someone in: add a colleague from your organization, connect a partner organization, or add one of your contacts. Adding several colleagues at once gives them all the same access level, and everyone you add appears on the roster right away.

People are listed under the company they work for rather than under an industry heading, so the roster answers who is on this project the way you would actually ask it. Colleagues in your own organization stay pinned at the top.

Taking a contact off a project moved from a small icon on the roster row to their person card, beside the access it affects, and now asks you to confirm first. The contact record is kept and can be added again, but their role, notes, and primary-contact flag on that project are not restored by re-adding them.

Contact rows sat slightly out of line with the colleagues beside them, and a contact linked to a platform account was filed under Other contacts instead of your own organization. Both are fixed.

For a construction company, a schedule is a work breakdown: its sections are tasks, and a top-level task with work under it becomes a section. The empty schedule now says exactly that, and no longer offers an Add phase button — phases are a property-development idea, and the button did nothing on a construction schedule. The New task form's Section box is also honest now: it was marked required but never was, and left your very first task with nothing to choose. It now offers “Top level — becomes a new section”, which is what actually happened all along.

A new project now begins with nothing on its schedule, the way it was meant to — you add the first task or milestone and pick the stage it belongs to. Construction companies were the exception: every new project arrived pre-filled with a starter work breakdown of sitework, structure, envelope, MEP and finishes, whether or not that matched the job. Existing projects are untouched, and nothing you have already scheduled has changed.

An empty schedule now offers an Add phase button, so you can lay out the structure of the job before there is a single task on it. Previously phases could only be added from a stage heading, and an empty project has no headings to add one from — so the only way in was to create a task first. Construction companies are asked only for the phase name, since every phase of theirs sits under Construction.

The public site's front page no longer shows the aerial backdrop on a phone. A wide aerial shot cropped into a tall screen left a narrow, hard-to-read sliver behind the headline, so small screens now get the headline on a clean background instead. This replaces the single still described in the 2.56.0 note below.

Scrolling near the top of the public site's front page could snap you back up as soon as you lifted your finger, which felt like scrolling had stopped working. It now scrolls freely.

Read a project's spec book right alongside everything else — browse the outline, jump to a section, and see its coverage. Import a spec book PDF and review the parse before it's added, or author and edit sections by hand. Every section keeps its own revision history, so you can see what changed and when.

The cost-code chart you classify work against is now called Rhett codes — you may have seen it as YES codes before. You'll see the new name on the submittals and RFI registers, the spec and drawing panels, the bidding budget, the code pickers, and Settings → Help → Reference. Nothing about the codes themselves changed — the same numbers, the same industry cross-references, the same chart. Only the name is different, so anything you've already classified stays exactly as it was.

The cost-code chart, the code pickers, the submittals register, and the spec-book import now talk about your codes and Rhett codes — the cross-reference column is simply “Industry code”. Nothing about the codes or the mapping changed: paste a recognised industry code and it still resolves to its Rhett equivalent, and a spec section number stays free-form, so you can number a book your own way.

Where an owner has not signed in yet, the team can send their setup link again without removing and re-adding them. Repeat sends are spaced out so an invitee's inbox does not get a burst.

A typo in a new organization's owner address used to be permanent — the invite went nowhere and the correct address could not be used. It can now be corrected while the invite is still unclaimed, which sends a fresh setup email to the right person.

Creating an organization now says what actually happened with the owner's invite: sent, not needed because they already have an account, or failed to send. It previously reported the second of those as a problem when nothing was wrong.

Our Privacy Notice and Terms of Use now spell out how subscriptions are billed and cancelled, that support staff can access records to operate the platform, that project cover images are viewable without a sign-in, and which payment and search providers we rely on.

Aerial footage of real development projects now fills the sign-in page, shuffled so you land on a different one each visit. It replaces the still photos that used to cycle there.

The front page of the public site now runs that aerial footage behind the headline. On a phone, or if you have asked your system to reduce motion, it settles on a single still instead.

Signing in on a phone used to mean a form on a plain panel — the imagery was desktop-only. Now a project photo sits behind it there too, kept light enough to stay out of the way of the fields.

The + beside the message box opens your files directly. It used to open a short menu first, where three of the four choices were not available yet. What you attach now sits on the same row as the +, so the box no longer grows taller with every file; past the first one they gather behind a count you can open.

Almost every dialog was opening with the close button focused, so the first thing you typed went nowhere and the first Enter closed the window. They now open on their own first field. The close button also stays inside the dialog and stays put as you scroll, and the buttons along the bottom no longer have content showing through them.

The chat limit counted everyone on one office network as a single person, so a few colleagues working at once could lock each other out. It now counts per person.

A project with bids out but none returned said no bids matched your filter, when no filter was set. Invitations you are still waiting on now count as activity. Elsewhere, a workspace with no projects yet says so plainly, and tells you when it is still loading or could not load rather than looking empty.

As the panel narrows, the toolbar drops one label at a time instead of all of them at once, and wraps rather than sliding controls out of reach sideways. Trash keeps its label longest, because it is the one that tells you whether you are in it.

The legal pages now carry the RhettWorks name and mark, matching the rest of the app.

Workflows has been removed from the sidebar and the search menu. It was a placeholder that never did anything, and it sat beside features that do.

The public site has been rebuilt from scratch — what the platform does, who it is for, and how to get in touch, with a page for each kind of team who uses it.

Tell us who you are and what you are working on, and it reaches us. Until now the form showed a phone number and an email address instead, because there was nowhere for it to go.

The browser-tab icon is now the Rhett mark, replacing the old green letter. It adapts to your browser theme — deeper sage on a light tab bar, lighter sage on a dark one — so it stays legible either way. The unread-notification dot still rides on top of it.

Open a spreadsheet with conditional formatting and you'll now see it: highlighted cells in their original colours, colour scales, data bars, and icon sets like traffic lights. Row banding shows up too. Rules that compare a cell against another cell — an actual against its budget, for example — aren't shown yet; the note above the sheet tells you how many were left out. Editing the rules themselves isn't supported yet either. Your formatting is kept in the file as long as you only change cell values, so it's still there when you open the workbook in Excel.

Owners and admins can now change someone's role from the members list — promote a member to admin, or hand over ownership — instead of removing and re-inviting them. You can also pick a role when sending an invite. Owners manage everyone; admins can add other admins but not owners. An organization can never be left without an owner, and every change is recorded.

The app you're using is now called RhettWorks, and the assistant you chat with is Rhett. The company behind it is still YIMBY Enterprise Systems. Nothing about how the product works has changed — your projects, files, conversations and settings are all exactly where you left them. You will see the new name in the sidebar, on the sign-in screen, and in email we send on your behalf.

In messaging, the assistant now answers to @Rhett. The previous @Reeve and @YIMBY mentions no longer reach it — send one and the message posts normally but nothing answers, so swap it before sending. Older messages still show the name they were written with, greyed out to mark it as retired.

Open a spreadsheet with named ranges and they're all there: in the name box, in the name manager, and in your formulas. Add, rename, or delete one and it saves back into your original file with everything else left alone: charts, images, dropdowns and comments all survive. Print areas and hidden names stay in the file too, even though the editor doesn't show them.

A new project no longer arrives with 21 numbered folders already in it. Most of them went unused, and two had been replaced by real features: photos by the photo library, notes by project notes. Create the folders you actually want, or have an admin set a folder template for the whole organization. Existing projects keep every folder they already have.

The Team panel now shows every teammate in your organization and every connected company on the project — not just the contacts you added. Open a teammate's card to see who they are and message them. Managing access stays with owners and admins.

Private albums can now be shared with specific people on the project. Open an album's Share control to pick teammates — they can view the album and its photos while everything else private stays hidden, and you can revoke access at any time. Sharing never adds edit rights, and photos marked private individually stay visible to managers only.

In a project's tool list, Drawings and RFIs have moved out of Project Management and into Construction, alongside Submittals and Bidding. Nothing about them has changed — they are just grouped with the other records that run during construction, so Project Management is left holding the planning tools.

Open a person's card and you now see every way you already reach them — your direct message and the groups you share — plus how to start a new one. Messaging someone for the first time opens the composer with them already filled in, instead of an empty To: field.

A contact who has a platform account now shows a Messaging tab beside their Comms timeline and change History, so you can talk to them without leaving the Team panel.

An unnamed group now reads by its members — “Marco, Gail +2 others” — instead of a bare “Group,” so you can tell your conversations apart at a glance.

Removing the link between a contact and their platform account used to happen on a single click. It now confirms first, so a stray click can't undo the link.

If a company with the same name was created moments before you approved a "Create company" card — for example by a related contact card you approved first — approving used to fail and throw away the details you had just approved. It now adds those details to the existing company instead, filling in whatever it was missing and leaving anything it already had alone, and tells you in chat that it did so.

(Superseded — see v2.51.0.) On this date the product and the assistant were renamed Reeve. Nothing about how the app worked changed, and the company behind it remained YIMBY Enterprise Systems. The name appeared in the sidebar, on the sign-in screen, in email we sent on your behalf, and everywhere the assistant introduced itself.

(Superseded — see v2.51.0.) At the time, the assistant answered to @Reeve, and @YIMBY kept working alongside it. Older messages still showed the mention the way they were written.

When YIMBY looks something up on the web, the answer now carries its sources inline — a small chip sitting in the sentence it backs, rather than only a list at the end. Each one opens the page it came from in a new tab, so you can check a number against its source without hunting for which link went with which claim. Answers that needed no lookup say so instead.

When you approve a connector action, the assistant reports what came back — the price, the figure, the market stats — instead of only confirming that the tool ran. If the call fails, it explains why in plain language rather than showing raw output.

A connector call could come back rejected even though your API key was fine, because the assistant was guessing what the tool's settings were called. It now reads them from the connector itself, so it asks for the right thing the first time. Reconnect a connector once (Settings → Connectors → Test connection) to pick this up.

Reopening a chat where you had approved a connector call showed a block of raw data underneath the reply that was not there the first time. The conversation now reads the same whether you are watching it live or returning to it later.

Approving a connector call and then switching chats — or starting a new one — could send the answer to whatever you moved to, or open a new chat containing a message you never typed. The answer now stays with the conversation it belongs to.

A result too large to show in full was quietly cut off. It now tells you how much you are seeing, so a partial answer is never presented as the whole picture.

After you approved a connector action, the follow-up reply could second-guess itself and withdraw earlier figures as possibly made up — even when every one of those calls had really run and returned. It now reports the approved result without re-litigating what it already told you.

An answer containing a long unbroken string — a full web address, an identifier, a block of data — pushed the message wider than the column and cut the text off at the edge. Long strings now wrap onto the next line. Code blocks are unchanged: they still scroll on their own so code stays intact.

Excel cell notes now appear in the editor, and you can edit them, add new ones, or delete them. Your changes save into the original workbook in place, with charts, dropdowns, and images intact, and a note you add carries your name as its author when the file is opened in Excel. Threaded comment conversations are kept safe in the file but aren't shown in the editor yet.

Approving a card used to pull you straight into whatever it created, interrupting what you were in the middle of. It now stays put and leaves a View button on the reply, so you go there when you actually want to.

Asking to save a file from an email into My Files, Org Files, or a project could get you a reply saying it wasn't possible. It always was — the assistant just didn't know the way there. Ask again and it will save the attachment where you asked, under its real filename.

Opening a task for editing in the schedule's Gantt view drew the grid's row and column lines straight through the form, which made it look like rows were overlapping it. The edit panel is now solid.

Excel dropdown lists now appear in the editor and you can pick from them, instead of only being preserved invisibly in the file. Editing a dropdown's options saves in place too, with charts and images intact. Rules that point at a range of cells or a named range are still kept in the file rather than shown.

Settings → Connectors is a directory for hosted tools like Financial Modeling Prep, RentCast, FRED, BLS, Census, and HUD. Admins pick who may connect. Each person uses their own API key by default; an admin can switch a connector to one shared org key, or allow both — where your own key is used automatically if you've added one, otherwise the org's shared key.

Each connector tool can be Always allow, Needs approval, or Blocked. Needs approval shows the same chat card as other assistant actions, then runs the tool if you approve.

Built-in market quotes and rental comps now come from the FMP and RentCast connectors you attach in Settings. Connect a key there before asking the assistant for that data.

Opening an Excel file in the editor and saving it used to quietly strip its dropdown lists, charts, images, comments and named ranges. Editing cell values now updates your original workbook in place, so all of that survives the round trip and is still there when you open the file in Excel. They are kept in the file rather than shown in the editor, which does not display them yet. Some changes, like reformatting cells or adding and removing sheets, still need a full rebuild, and the app now tells you what that costs instead of dropping it silently.

Ask YIMBY to write something up and it now asks which folder it should go in before creating anything, instead of picking for you. The approval card names the destination too, so you can see where a document will land before you approve it.

A document created without a folder was saved but never appeared anywhere in Files — the only place documents live — so there was no way to open it again. Every document now has a home from the moment it's created.

If a document's file was deleted while you had it open, the editor kept trying to save and quietly failing on every keystroke. It now tells you the document is gone. Restoring the file from Trash brings the document back with it.

Delete permanently and Empty Trash used to remove only the file — a document you'd created from it stayed behind. Now deleting a file for good also permanently deletes any document built on it. There's no way to bring it back, so check before you empty Trash.

When a request was assigned to, or received from, someone at another company working on the job, the card couldn't name them — even though the request itself was perfectly valid. Those people are now named, but only to teammates who can open that job. Anyone genuinely outside the job still isn't named, so the card is never a way to look up a stranger.

Approve is switched off for permanent deletions when the card can't say what it would delete. It was switching off too eagerly — a card that named the record perfectly well on one line could still be blocked by a different line, leaving Reject as the only way out. It now only steps in when the card identifies the record by nothing at all.

Approving a schedule change that moved a phase underneath a different one showed only the phase's current details — nothing said a move was happening. The move is now spelled out, along with changes that clear a field rather than set it.

Changing a checklist item's reviewers listed only the first one. All of them are now shown. Phase names on approval cards also match what they're called everywhere else in the app instead of an abbreviated version.

A few approvals asked you to sign off on work you couldn't see. A schedule import showed one line of boilerplate and none of the tasks, dates or durations it was about to write. A generated document showed its file name but none of its terms. Batch edits showed new dates without saying which tasks were moving. All of them now show the full contents before you decide.

If a card proposes permanently deleting something and can't work out which record it is — because it's already gone, or you don't have access to it — Approve is now disabled and the card says why. Previously you could approve it anyway.

A conversation with a lot of pending approvals only ever showed the first 50, and the counter read as though that were all of them — the rest were still waiting but unreachable. The full queue now shows.

Several cards repeated the same text twice under two headings, printed internal codes where a plain label belongs, showed settings that only mean something to the system, or left a bid amount unformatted next to a properly formatted one. All cleaned up.

Approval cards used to show raw internal reference codes — and a few showed nothing identifying at all, so you had to approve a change without seeing what it applied to. Every card now names the record: the RFI and its subject, the submittal, the company or contact, the budget line, the file, the checklist item. Long values get a Show more link instead of being cut off.

Approving a new RFI or submittal showed only a handful of its details — the cost and schedule impact, the spec reference, the drawing number, the cost codes and the people it was being assigned to were all left off. Both cards now show every field the request sets, and name the people instead of listing reference codes. When someone can't be named — because they work at another company on the job — the card says so plainly instead of suggesting they don't exist.

Approving a file upload showed an internal reference code beside the file name. The card now shows just the file name and the folder it's going to.

On the projects map, the tool menu no longer runs off the bottom of the screen — every option stays visible and reachable no matter where on the map you open it.

When you select a task in My Tasks, the header tidies its controls out of the way instead of letting them spill off the edge, so the filter, column, and approval buttons stay reachable.

Settings could show your Microsoft account as "Not connected" — with a Connect button — while the connection was working perfectly. The same mistake could make a new project skip creating its SharePoint folders, or ask you to reconnect before setting them up. YIMBY now checks the connection itself rather than a shortcut that goes stale, and it tells the difference between a genuinely disconnected account and Microsoft simply being unreachable for a moment.

The duplicate Projects header is gone. The Projects row now does it all: click the name to open your portfolio, use the arrow beside it to tuck the project list away, and the folder button to start a new project. A line under the row marks where the scrolling list begins.

The sidebar's chat list orders by when you last used a conversation, not when you created it — so a long-running chat you message every day stays near the top instead of sinking under newer ones.

Chat pinning has been removed. Every conversation now lives in one place — under its project, or in the Chats list — and previously pinned chats have rejoined those lists. Use search (⌘K) to jump between your recent conversations instantly.

After connecting your Microsoft account, the page could show “The Microsoft window closed before the connection finished” even though the account had connected successfully — the panel below the message showed it as Connected at the same time. The message now waits for the real result instead of assuming the worst when the Microsoft window closes.

YIMBY could only read your inbox, so a question about mail you sent — "who did I send this to", "have I emailed them" — was answered from the wrong mailbox or not at all. It now reads your sent mail too and tells you who you wrote to, including anyone you BCC'd. Over a long stretch it works back from the most recent mail and tells you how far back it got.

YIMBY sometimes told you to reconnect your Microsoft account and refused to read your mail, calendar, or files — even though the connection was working fine. It was checking a shortcut that goes stale on its own, rather than the connection itself. It now checks properly before saying anything is disconnected.

Marking a notification as read in the Inbox left the unread number beside Inbox in the sidebar — and the count on the browser tab — showing the old total for up to a minute. Every place that shows the count now updates together, instantly.

Password fields on the sign-in and set-password screens now have an eye button to reveal what you typed, so a typo doesn't mean guessing.

Drawing search covered every project you can reach with no way to narrow it, so a request for one project's sheets could come back carrying an unrelated project's. YIMBY now keeps the search on the project you asked about.

When YIMBY drafted a forward without having the original message open, the draft could be sent carrying only your cover note — the original, its attachments and the earlier replies were all silently missing from what the recipient got. Sending is now blocked in that case, and the draft points you at the message to forward from instead.

Resizing the window or dragging the reading pane's divider left the bottom of a message clipped, with no scrollbar to reach it. The pane now re-measures every message as it resizes. Forwarded chains are the tallest thing the pane shows, so this was worst right where it mattered most.

Certain messages could freeze the mail view for several seconds while it scanned their content. The scan is now effectively instant regardless of what an email contains.

If loading a conversation failed, it quietly showed the preview text as though that were the whole message. It now says so and offers a Retry.

The “Images blocked” bar could stay up on a message that had no images left to load, and clicking it did nothing. It now appears only when there are images to show.

Opening a forward could show only the sender's short note above it, with the forwarded email itself missing entirely. When Mail detects that a forwarded or quoted chain was left out of a message, it now offers a button that reveals the original in place — labelled “Show forwarded message” on a forward.

Checkboxes across the app — task lists, filters, settings — now use one shared control, so they match in colour, size and keyboard focus instead of drifting apart screen by screen.

Confirmation dialogs used to surface the raw technical error when something failed. They now explain what happened in plain language, so a dropped connection reads as a dropped connection.

A name with a bracketed tag in it — the shape Microsoft-connected accounts often have — produced a garbled two-letter avatar. Initials now come from the person's actual first and last name.

A right-click menu opened near the bottom or edge of the window could run past it, leaving the last options cut off and unreachable. Menus now always fit on screen, and a menu with more options than will fit scrolls inside itself.

Calendar mail — invitations, cancellations, and accept/decline replies — often arrives with no written message at all, so it showed as "No message body." These now show the meeting itself: what kind of notice it is, when the meeting is, and where. YIMBY reads the same detail, so asking about a cancelled meeting gets a real answer instead of an empty message.

In the composer's To, Cc and Bcc fields, typing a complete address and pressing Enter could send to whoever happened to be at the top of the suggestion list instead. Your typed address now wins; suggestions are used when you pick one with the arrow keys, or when what you typed is a name rather than an address. Hovering the list with your mouse no longer changes what Enter picks.

Moving between messages with the arrow keys left a blue outline around the message that had just opened, in Safari only.

Meeting-invite replies — the automatic "Accepted"/"Declined" notes Outlook sends — carry no message body at all, so they showed up as an empty message that looked like a loading failure. They now say so plainly, and messages that used to come up blank for other reasons show their full text.

A forward saved to your Drafts folder kept the recipients on screen but not in the saved draft, so reopening it later showed an empty To field. Everyone you addressed — To, Cc and Bcc — is now saved the moment the draft is created.

The composer now shows the original message under a forward or a reopened draft. In the normal case the full original was already being sent — it just wasn't shown, which made forwards look like they'd been cut off.

Asking YIMBY to forward one email and then another no longer reuses the first forward's draft — the second forward now carries its own subject, quoted message, and attachments instead of the first one's.

Asking YIMBY to revise a staged email no longer spawns a duplicate draft threaded onto the first one — the revision now updates the draft already in your composer, and attachments land with it.

If an open draft was deleted elsewhere (for example while tidying the Drafts folder), the composer now recreates it on the next save instead of failing repeatedly with an error.

An email drafted from the main chat is now saved for you — open Mail, hit Compose, and the draft is there, even if you drafted it on another device or reloaded in between. Previously it could quietly disappear if the Mail panel wasn't open at the moment it was drafted.

Asking YIMBY to forward a specific email while you're reading a different thread now forwards the email you named — with its attachments — instead of the thread you happened to have open. The composer also no longer shows another thread's quoted history under a forward that doesn't belong to it.

In rare cases a follow-up request could make YIMBY treat its own unsent draft as an email to reply to, producing a stray "Re:" draft with no recipients. Unsent drafts no longer show up in the assistant's inbox or thread listings, so it can't treat one as a message to reply to — and a revision can no longer blank out the recipients already on your draft.

When YIMBY drafts a forward, the composer now asks you to confirm the recipients before it goes out — unless everyone you're forwarding to was already on that exact message. Forwarding carries the original's body and attachments, so this is the moment to catch a wrong address.

Chat now speaks the same asset classes as the rest of the app — all eight, from Multifamily to Specialty — and can drill into specific building types (say, a data center under Industrial). Ask YIMBY to create a project as any class, or update an existing project's types, and the change flows through the usual approval card.

The report-a-problem form now submits with Cmd+Return (Ctrl+Return on Windows), just like composing an email.

Close your browser, come back, and your workspace comes back with it: the tabs you had open along the side, the document you were reading, the folder you were browsing in Files, the drawing sheet you were on, the mail folder and conversation you were in, and the chat you were last talking in. Anything you no longer have access to is quietly left out rather than shown as a dead tab. Reopening a chat or a mail conversation is limited to the last hour — after that you land on a fresh one, so on a shared or unattended machine yesterday's messages are never sitting on screen for whoever sits down next. Everything is cleared when you sign out or switch accounts.

When your Microsoft connection expires, reconnecting used to navigate the whole app away and bring you back to an empty workspace, losing your place and any unsent message. It now happens in a small separate window: your work stays exactly where it was, and whatever failed picks up again on its own. If your browser blocks pop-up windows it falls back to the old full-page approach, and returns you to the same conversation.

If YIMBY can't reach your email or calendar mid-answer, the reply now carries a Reconnect button instead of just reporting that something went wrong — and it tells you whether the connection expired or is missing a permission. Every reconnect button in the app now says plainly when an attempt fails, rather than appearing to do nothing.

Reloading the page could silently clear the tabs you had open along the side — you would usually notice only on the next reload. This was reported and is now fixed, which is also what makes reopening your workspace reliable.

Reopening a very long conversation now loads the most recent stretch first, with earlier messages available above, instead of fetching the entire history before anything appears.

YIMBY can now pull live financial-market data into a conversation: stock quotes, company financials and earnings-call transcripts, macro indicators like rates and CPI, commodity prices such as lumber and steel, market movers, upcoming earnings and economic calendars, and finance news. Ask about a REIT's latest earnings, where the 10-year sits, or what lumber has done this quarter, and the answer comes from live data rather than the model's memory. Everything is read-only, and the team's Operations workspace shows a running count of these external data calls.

Some work that spends on AI — reading scanned PDFs, describing images — was not always being recorded against the right organization, or in a couple of cases was not being recorded at all. Those gaps are closed, so cost figures now reflect the full picture regardless of which AI provider handled the work.

When you edit a task on the schedule, Status is now a colour-coded dropdown sitting next to Owner and Priority — pick any status, including moving a task back a step, rather than only cycling it forward. Marking a task done still asks for the usual note and review, and reopening a completed task asks you to confirm first so nothing gets un-completed by accident. The status pill on the row still works as the quick one-click shortcut. This applies when editing from both the project schedule's list view and your cross-project My Tasks page.

The old full-page project Conversations tab has been retired — a project's chats are already listed under that project in the sidebar, and opening one takes you to the main chat view. Old links and bookmarks still work; they now take you straight to the chat or the project overview. One thing is temporarily missing: searching, sorting and exporting a project's chat history, which only existed on that old page. Searching your recent chats with ⌘K still works, and we're bringing the rest back on the project sidebar.

The small pop-up messages that confirm an action or report a problem have moved from the top of the screen to the bottom-right, so they no longer cover the toolbar or whatever you were just reading. They also pick up the softer rounded card and clearer heading used elsewhere in the app, and file uploads now report progress in the same place. Success and failure are still told apart by the colour of their icon.

If a passkey is ever added to your account, you'll now get a notification and an email straight away — with the passkey's name and when it was added. If it was you, there's nothing to do. If it wasn't, the alert links you to Settings → Security so you can remove it and change your password. Because a passkey isn't removed by changing your password, being told promptly is what lets you act.

You can now sign in with your device's fingerprint, face, or screen lock instead of typing a password. Add a passkey from Settings → Security, or when you first set up your account, and use it from the sign-in page — either by choosing “Sign in with a passkey” or by picking it straight from the email box. Your password keeps working, so you can always get back in. Because a passkey is separate from your password, changing your password does not remove it; remove any you don't recognise in Settings → Security.

The communications rail on a project's Team view is less cluttered: one clear Comms/History switch, a compact filter for scoping to this project or all communications, and tidier entries that drop the repeated project label and put the date and time on a single line. The panel also fills the full height of the column now.

The Library now shows your file sources — My Files, Org Files, OneDrive, and Projects — as tabs across the top instead of a tucked-away dropdown, so it's always clear which store you're browsing and where a file actually lives. Hover a tab for its full name.

The Library's view switcher (grid, list, columns, and gallery) now shows a label when you hover it, and the toolbar buttons pop their tooltips right away instead of after a pause.

A project's status is now an ordered "Pipeline Status" — Prospect, Under Contract, Active, On Hold, Inactive, Complete, Cancelled, Archived — so you can see where a deal sits at a glance, separate from its Stage. Group, filter, and sort the portfolio board by that pipeline order, and the Settings dropdown now matches the rest of the app.

Turn your Outlook automatic replies on or off — with a separate message for colleagues and external senders, and an optional date range — from Mail's ••• menu, or just ask YIMBY in chat. Mail shows a reminder while it's on so you don't forget, and it's the same auto-reply Outlook uses, so it stays in sync everywhere.

When you ask YIMBY about an email whose contacts are tied to one of your projects, it now offers to file the thread under that project — so the conversation shows up where the work lives.

The Mail item in the sidebar now shows a dot and a count when you have unread email, so you can tell there's something new without opening the panel.

When you ask YIMBY to reply to everyone, it now gathers every participant across the whole conversation — not just the people on the latest message — so someone who wrote earlier in the thread no longer gets left off.

Submittals and packages now carry a YES cost code — search the chart or paste a CSI code and it maps to the YES equivalent for you. The register groups and filters by YES code, and importing a spec book auto-classifies every item. This replaces the old free-text spec-section field; an imported code that doesn't map yet still shows its raw CSI so you can reclassify it.

Settings → Reference now shows the full YIMBY cost-code chart as a browsable, searchable accordion — division down to subsection — with each code's equivalent CSI MasterFormat code shown alongside for easy mapping. This replaces the standalone CSI Codes reference.

The account menu now groups your signed-in accounts under their organization, so accounts across different orgs are quick to tell apart — hover "Switch accounts" to see them and switch, or add another. Your current account is checkmarked in its own group.

When a new version of YIMBY is ready, the account menu now shows an "Update now" item — press it to reload straight into the latest build, without opening Settings first.

The assistant now grounds its answers in whatever you have open — the current project, panel, or a specific record like a task, drawing, submittal, RFI, or spreadsheet selection — so you can ask "what am I looking at?" or "summarize this" without restating what's on your screen. A breadcrumb above the message box shows exactly what context is in play.

With a Mail thread open, the assistant reads that conversation for the current question and shows it in the same breadcrumb, then stops using it the moment you switch away from Mail.

A project's Type field now picks one or more asset classes — Multifamily, Office, Industrial, and the rest — and lets you drill into specific building types within each. Pick more than one class for a mixed-use project.

Organization records in CRM now carry the same asset-class picker, so you can flag which classes a firm is qualified to work on. Chips next to the Type pill show the classes at a glance, and hovering reveals the specific building types.

A new Settings → Help → Reference page lists every building type alongside its asset class and checklist template, so it's easy to look up where a building type falls.

Signed in with more than one account — say, one per organization? Add them all from the account menu and hop between them in two clicks, no password re-entry. Signing out of one account rolls you to the next; "Log out of all accounts" fully signs out everywhere.

Ask the assistant to add reviewers to a task — including more than one, with a sign-off rule (everyone must approve, or any one of them) — and it queues the assignment for your approval. Reviewer sign-off gates a task's status changes.

Owner and reviewer menus now show each teammate's email beneath their name, so people with the same name are easy to tell apart — and you can search the menu by email.

A reviewer set across several tasks at once is now correctly required to sign off on those tasks' status changes, matching a reviewer assigned to a single task.

A full Request-for-Information workflow: create RFIs against project documents or sheets, route questions to the responsible party, respond with highlighted references, and track every RFI in a sortable, filterable register with saved views and CSV export. The assistant can draft and manage RFIs with your approval.

Settings → Help now includes a searchable CSI MasterFormat reference — divisions, headings, and sections — so you can look up the right cost code without leaving YIMBY. The assistant can answer CSI questions too.

A guide to everything YIMBY can do, filtered to what your role and permissions actually let you use — so the list you read is the list you have.

YIMBY now tells you when a new version is ready instead of reloading out from under you. A small dot appears on your profile when an update is live; update from Settings → Version whenever it suits your workflow.

This timeline: every notable YIMBY release, newest first, with what was added, improved, or fixed — so you always know what changed and when.

Publishing a new version could previously reset open tabs without warning, interrupting work in progress. Updates are now applied on your terms, and the rare automatic recovery reload happens at most once — never in a loop.

Ask YIMBY to change cells in an existing workbook and it edits the file directly — no more regenerated copies. Every edit goes through the approval gate, and the assistant can read raw source cells to ground its changes.

Approval cards gained a View button that opens the approved change where it lives — the schedule item, contact, or file — so you can verify what happened in one click.

Roles and company types now support per-org sub-types (generalizing subcontractor trades), so your directory can mirror how your organization actually categorizes people and firms.

The projects portfolio moved into the side-panel workspace with a per-project tool menu, so you can hop between projects and their tools without leaving your chat.

Tasks, checklists, and files could show out-of-date content after a session refresh. Sign-in renewal was unified so panels reliably show current data.

A cleaner card layout with inline editing of proposed values and a "Chat about this" action that pulls the pending change into the conversation for discussion before you decide.

Files open in a right-side preview tab — including PDFs — so you can read a document and keep chatting at the same time.

Uploads accept every file type, run in parallel, and report progress on a single card. Nested-folder uploads no longer error.

A tighter single-row header, organization-level schedule templates you can manage in Settings, and nested project phases for real work-breakdown structure.

Markups carry forward when a new revision of a sheet arrives, an activity feed tracks who changed what, and simultaneous edits merge safely instead of overwriting each other.

Six long-standing annoyances fixed in one pass: header crush on narrow windows, sticky save buttons, project-rename propagation, member search, text sizing, and the mobile panel layout.

A native home for project documents: create and edit docs in the app, view spreadsheets and decks, and work on a document together with the assistant.

A Settings matrix that controls which tools and agents the AI may use on your behalf — block a capability once and every future conversation respects it.

A dedicated security pass over file storage and account-connection flows ahead of onboarding client data.

YIMBY now calls most tools directly instead of routing every request through a specialist agent, and caches its instructions between turns — noticeably faster replies on everyday asks.

A full visual reskin: warmer palette, a unified side panel for project tools, and pinning and archiving for conversations.

The theme picker grew from two to four: Cloudy, Rainy, Day, and Night — plus follow-your-OS System mode.

Draw polygon regions, drop text instantly, and see grouped markup counts with fill controls on drawing sheets.

Dictate to the chat composer with in-browser transcription — audio is processed locally and never leaves your machine.

Every conversation now has its own address, so you can bookmark a thread or share its link with a teammate.

A collapsible rollup of org and project permissions, so an admin can audit who can do what at a glance.

Per-person permission templates with an org-wide default, per-employee overrides, and cross-organization project sharing via template slices.

Choose Fast, Standard, or Expert per conversation, with a context-usage border that shows how full the thread is getting.

Approvals and dialogs answer to the keyboard (Enter to confirm, Escape to dismiss), and the product completed its rebrand to YIMBY.

The assistant can find drawing sheets and present them as cards in the conversation — open one straight into the viewer.

Ask the assistant for a document and get a real Word file or PDF delivered to your files, ready to send.

Companies got their own detail pages with types, child records, and history — no longer just a name on a contact.

Edit sheet titles and disciplines, and control visibility by review status so unreviewed sheets stay out of the way.

A notification bell with a panel, per-tab badges, and automatic resolution when the thing you were notified about gets handled.

YIMBY remembers durable facts and preferences across conversations, and you can review and edit everything it knows in Settings → Memory.

The assistant reads your calendar, finds free times across participants, and — with your approval — creates and updates events.

Project and CRM changes proposed in chat all flow through approval cards designed for each action type, with full payload detail and reasoning.

Deleting a file moves it to a Deleted folder with a trash view — recoverable, instead of gone.

A cross-project view of everything assigned to you, with priorities, review states, grouping — and a personal to-do list alongside your project work.

Light, Dark, and System theme options with a dedicated light palette.

Files attached in chat now persist in cloud storage — an app restart can no longer lose an upload mid-conversation.

A guided profile flow on first sign-in, so new teammates land with their name and workspace set up.

A split pane in the main chat previews files natively while you keep the conversation going.

Create, edit, and delete contacts directly in the app, scoped to your organization, with vCard export.

A security pass tightened organization boundaries across workflows, approvals, and admin surfaces so each org's data stays strictly its own.

A feedback page that captures rich debug context automatically, so a report is enough for the team to reproduce the problem.

Connect and disconnect your Microsoft account from Settings → Integrations, powering email, calendar, and OneDrive features.

A split-screen login with a project hero, plus a dedicated page for reporting sign-in trouble.

YIMBY became a true multi-tenant product: closed-system sign-in, organization member management for admins, and controlled sharing of projects across organizations.

The project home arrived: a portfolio list of every project and a per-project workspace with schedule, people, files, and chat in one place.

A two-axis participants view maps who said what, grounded in transcript evidence, with chat-assisted resolution for uncertain speakers.

Meetings now produce a summary grounded in project context and proposed action items you can accept, edit, or reject.

Upload a meeting recording and get a transcript with durable artifacts — the foundation of the meetings program.

New Agenda and Lookahead views alongside List and Gantt, with owner and reviewer columns, drag-to-reschedule in edit mode, and construction-style filters.

The global People page arrived: a full roster with detail views and interaction timelines, linked to each project's team tab.