🎛️ Switch the agent's permission mode from the composer
Previously the mode was a line of text under the composer that you clicked to step through, and new sessions began in Plan. Now a chip beside the model picker opens a menu that describes all five modes, and new sessions start in Auto unless you pick your own default.
👉 Click the mode chip left of the model picker in a session's composer, or press Shift+Tab.
- 🧭 Five modes, described. Manual, Accept edits, Plan, Auto, and Bypass. Each menu line says in one sentence what the mode lets the agent do without asking.
- ✅ Open prompts close themselves. Switch from Manual to Auto while a permission card is open, and the card closes if the new mode already allows that call.
- 📝 Plan, then carry on. Approving a plan names the mode the work continues in, such as Approve and continue in Auto.
- ⚙️ Your own default. Settings › Defaults sets your starting mode and whether sessions wait for your answers. New session shows both as chips, Waits for you or Carries on without you.
- 💻 In the terminal. The terminal client names the mode in words, from 'manual mode on' to 'bypass permissions on'.
➕ The composer is one box with a + menu
Previously the session composer stacked a row of icons, a row of chips, and a two-line hint. Now it is one box with a single row under it: +, mode, model, microphone, and Send or Stop. On a phone, Home is that same box, so a session starts there.
👉 Click + in any session's composer.
- 📎 The + menu. Holds Attach files, Draw a diagram, and your integrations with their count. It opens as a popover on a wide screen and as a sheet on a phone.
- 🔘 One action button. Send shows an arrow and Stop a filled square. A finished session shows a worded button instead, such as Resume or Start follow-on.
- 📏 The row never wraps. On a narrow screen it drops the effort first, then the mode's name, then shortens the model's name.
- 📱 Phone Home starts sessions. The box sits above the tab bar and rides up with the keyboard. + holds every other setting, and the green Start session button sends it.
- 🧹 No now-running bar. The phone's bar above the tab bar, with the running session and its Stop button, is gone. The Sessions list and the session page cover it.
🔒 See who can read a private session
Private and public sessions used to look alike once you opened them. Now a private session's composer says who will read what you type, its browser tab leads with a lock, and team or private projects wear a locked folder wherever they appear.
👉 Open a private session and click the access chip in its composer.
- 👥 Who can read. The chip reads Only you, You and Carlton, or You and 2 others. Its menu lists people by role, and Manage access opens Share.
- 🆕 Before you start. Starting a session in a team or private project shows the same chip, naming who will be able to read it.
- 🗂️ A locked tab. The tab reads '🔒 Q4 org planning · Evergreen'. The terminal client's tab title leads with its own lock and says the state and privacy in words.
- 📁 Locked project folders. Shown on session rows, group headers, search, and the projects list. Slack's project line and the terminal say team or private beside the lock.
- 🤝 Collaborator, not Editor. Share's role picker now reads Owner, Collaborator, and Viewer, matching the Collaborators list. What each role can do is unchanged.
🚨 Evergreen says what it is doing about red CI
Previously a failing check showed only Checks failing, while Evergreen re-ran tests or merged the base branch in the background. Now each of those decisions writes a plain sentence in the session, and when the red isn't your pull request's fault you get a card offering a separate fix session.
👉 When the card appears in a session, click Start a fix session.
- 🔁 Re-runs explained. A re-run names the failing test files and says why they look flaky, for example that the same test failed on other pull requests lately.
- 🧯 A fix on offer. Fix this outside the pull request says what is red, where, and why. It appears for a red base branch, flaky tests, or CI failing after a merge.
- 🔗 Find the fix. Start a fix session opens the new session, and the transcript row links to whichever session is fixing that red.
- 🧮 One card per red. You get one card per session and failure, and only while the failure is still there.
🚚 See your merged PRs still on their way
Standup now lists your merged pull requests that haven't reached production yet, in a new On the way section beside Now. Pick a group instead of You to see the same for your team, whatever window you're reading.
👉 Standup › On the way, or evergreen standup.
- 🙋 Needs a person. The heading counts the changes and how many need a person. Each stuck, failed, or held row says which, in the warning color.
- 🧾 Each row. The title links to its session and repo#number links to the pull request, followed by its status and environment rail.
- ✂️ Kept short. On a busy read it keeps every row that needs a person and fills up to five.
- 📋 Copy and terminal. Copy for standup includes the section, and
evergreen standup prints it in the terminal. - 🕐 Exact deploy times. Hover an environment on a pull request's deploy rail to see when it deployed, in local time and UTC. The transcript no longer prints a line per environment.