Evergreen
Sign up

What's new

What each release of Evergreen adds, where to find it, and how it works.

Evergreen 0.9.0

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.

Evergreen 0.8.0

Keep your sessions open beside any page

A sessions panel now opens next to the rail. You can see your sessions and jump between them without leaving the page you're on. It stays open or closed as you left it, on every device.

Click Panel on the rail's Sessions row.

  • Grouped like the board. Groups are Pinned, Waiting for you, Needs review, Running, Merged and Recent. Empty groups are left out. You can also group by project. Each group shows ten rows, and Show more loads the rest.
  • Same filters as Sessions. The funnel opens the Sessions page's filters, with Show first: Yours, Shared with you or Both. Chosen filters appear as small chips under the header.
  • Marks with details. Hover the marks at a row's bottom right to see a card. It shows the project and automation as links, the repos, the owner when it isn't you, and the session's family as a tree.
  • Drag it wider. Drag the panel's right edge to widen it, up to 650px or 35% of the window. Double-click the edge to reset it to 280px. Each browser keeps its own width.
  • Wider screens only. The panel appears on tablet and desktop widths. It isn't shown on a phone.

Pick model and effort inside the box

On desktop, the model, effort and per-phase models used to be separate controls under More. They are now one dropdown in the New session box's footer, and its label says which models will actually run.

New › the model name at the bottom of the box.

  • Says what runs. Before, a dot with a count hinted that some phases used other models. Now the label spells it out, for example "Claude Opus 5.5 High · Planning on Sonnet 5.5", "2 phases differ" or "3 models".
  • Per phase in one line. Set planning, executing and review apart from the menu's Per phase row. If you change only a phase's effort, that phase keeps its model.

Sort the Sessions page and keep your view

The View menu has a new Sort by section, and the board can draw one swim lane per project, owner or repository. The page now opens on the last view you set, in any browser, with your filter chips.

Sessions › View

  • Sort by. Attention, the default, puts what waits on you first, then Needs review. Chronological sorts by last update. Group by gains None, so the old flat list is None plus Chronological.
  • Swim lanes on the board. On the board, grouping by Project, Owner or Repository draws one row per group, split into the status columns. Lane headers fold and stay pinned at the left as you scroll.
  • Saved for you. Your scope, filter chips, grouping and display are saved for you in each workspace. Opening someone's link with its own filters never overwrites your saved view.
  • Families have names. A Family pill now names the family, such as "Flaky sweep · 3", rather than "Family · 3". Opening any Family pill shows the family as a tree, with a This one chip on the current session.
  • In the terminal. Use evergreen ls --sort or -g none. On the terminal's home screen, ctrl+r switches between the two sorts.

Tell Evergreen how to name your sessions

Evergreen names every session you don't name yourself. You can now say how you like those names written, for example starting with the Jira key or using noun phrases. Evergreen follows your words when it names a session at the start, after the first summary, and when the agent renames it.

Settings › Defaults › Sessions › Session names

  • A short note. Write up to 500 characters in plain words. Your guidance takes priority over Evergreen's own naming defaults.
  • In the terminal. Use evergreen session-names set to set it, show to read it and clear to remove it.

Mark up a page from a floating toolbar

Feedback on a published page used to open as a column beside the page, squeezing it narrower than its real layout. Feedback now floats as a toolbar over the page, so the page keeps its full width, and the comment box opens right next to what you marked.

Open a published page and use the Feedback toolbar at its foot.

  • Comment on the whole page. A new Comment tool sits beside Highlight and Circle. Use it for feedback such as "too dense" that isn't about one spot, without marking anything on the page.
  • Move it anywhere. Drag the toolbar by its grip anywhere over the page. It holds a comments button with the open count and Send all.
  • Reopen a mark. Click a mark's badge to open its comment beside it, with Resolve, Send and Delete.
  • Fix with Evergreen too. The Fix with Evergreen widget on other sites now uses the same toolbar instead of a 380px sidebar, so you can mark the whole page. It also follows your light or dark setting.

Evergreen 0.6.0

The agent talks plainly to non-engineers

Choose how the agent talks to you. With Plain language, it leads with the outcome in your terms, leaves out code and file paths, and makes technical choices itself instead of asking you. Technical keeps the agent's usual detail.

Settings › Defaults › Interface › How the agent talks to you

  • Follows whose turn it is. In a shared session the agent answers each person in their own style, so a paralegal and an engineer each get wording that fits them.
  • Clearer permission cards. A permission card reads 'The agent wants to: …' and 'Nothing happens unless you allow it.' The raw command sits behind Show the exact request.
  • Calmer plans and transcript. The transcript starts condensed, and a plan's files, checks and pull requests fold behind one line. Pick Detailed once and it stays that way.
  • In the terminal. Sessions started from the CLI get the agent's plain replies, but the terminal keeps its technical labels. Change the setting on the web.

Unsent replies wait for you

Previously, a reply you typed in a session was lost if you opened another page, reloaded or closed the tab. Now each session keeps its own unsent draft in the reply box until you send it.

  • One draft per session. Each session keeps its own draft, and it never appears in another session or for someone else signed in on the same browser.
  • Cleared on send. Sending the message clears the saved draft, so the box is empty next time.
  • This browser only. Drafts stay in the browser you typed them in and don't follow you to another device. The terminal client doesn't keep them yet.

Your filters stay set between visits

Previously, Home, a project's Sessions tab and the Projects list opened on default filters every time. Now each one reopens on the filter chips you last chose in this browser.

Set a filter on Home, Projects or a project's Sessions tab, then come back later.

  • Per project. A project's Sessions tab remembers its filter chips for that project, since repos and owners differ. Everyone or Yours is shared across all projects.
  • Links open as shared. A link that already carries filters opens exactly as linked. Clear is remembered too, so a cleared view stays cleared.
  • What starts fresh. Search text and the archive toggle reset each visit. The memory is per browser and survives signing out and back in.

Retry a failed run with one click

Previously, after a run failed, Resume stayed disabled until you typed something, so people typed 'continue'. Now the button works with an empty reply box and sends the continue message for you.

On a failed session, click Retry in the reply box.

  • Retry or Resume. The button reads Retry when the failure is temporary, such as a model error, rate limit or lost runner, and Resume otherwise. Type a message and it sends yours.
  • Cause in the title. The card's title names what went wrong in plain words, in place of the small gray note under it.
  • Enter stays safe. Pressing Enter in an empty box still sends nothing, so a stray key never starts a run.
  • On a phone. The arrow on the reply pill reads Retry and works with nothing typed.
  • In the terminal. evergreen send with no text resumes a failed or parked session.

See every session related to this one

Follow-ups and continued sessions were already linked, but only by a small chip and two rows in Details. Now the app bar shows the session this one came from, and a Family pill lists every related session with its status and pull request.

Open a session › Family pill next to the title

  • Parent in the app bar. The app bar reads Home › the session this came from › this session, so you can jump back up in one click.
  • The whole family. The popover lists who started this session, follow-ups started alongside it, the ones it started and the ones that continue it.
  • Merged vs completed. Each row shows its pull request number colored by state, so a merged session reads differently from a completed one.
  • Private stays private. Related sessions you couldn't find in a list don't appear in the family.
  • Phone and terminal. On a phone, ⋯ › Family opens the same list. In the terminal, evergreen status prints the Family rows with status and PR.

Evergreen 0.5.0

Find files and projects from ⌘K

Previously ⌘K searched only sessions and pull requests, and a file's text was searchable only from a box in the session sidebar. Now one palette searches sessions, the files attached to them and projects. It puts a Top result first and previews the row you highlight.

Press ⌘K (Ctrl+K), or tap Search on a phone.

  • Files open at the passage. Search for a line in a PDF, sheet or deck you attached, and the hit opens the file in Evergreen at that page with the matched words marked. Searching "Acme deck" also finds the session the file was attached to.
  • A preview beside the list. A file previews as itself. A project shows its people, live sessions and recently merged PRs. Press O to open, C to copy the link, or 1–3 to jump to a match. The Preview toggle hides the pane.
  • Top result and filters. A project or session title you type in full, or what you opened before for the same words, goes to the top. Click a filter to narrow the results instead of typing one.
  • Ways out of no results. When nothing matches, search offers to look across everyone's sessions or drop one word, and shows how many results each choice finds.
  • In the terminal. evergreen search lists matching projects alongside sessions.

Evergreen feels like a phone app

Previously a phone got the desktop layout squeezed onto a small screen. Now phones get a bottom tab bar (Home, Search, New, Inbox), a one-line composer, menus that slide up from the bottom, and an Inbox where you can answer what's waiting without opening the session.

Open Evergreen on your phone, or add it to your Home Screen.

  • Triage from the Inbox. Tap a waiting row to Allow or Deny a command, answer a question or approve a plan in place. Swipe an update left to mark it read. A push notification opens the exact ask.
  • Home leads with Needs you. Home opens on what needs you. Lane tabs stay pinned at the top as you scroll. A card above the tab bar shows your running session, with Stop or Answer.
  • Long press for more. Hold a session row for Copy link, Share and the PR. Hold a message for Copy message or Quote in reply.
  • Undo on one-tap actions. Archive, Mark completed, Pin and Read show a bar at the bottom with Undo for a few seconds.
  • Native on Android. Android gets Material bars and a floating New session button. Back closes the top sheet first. Long press selects several rows to act on at once. You can share a screenshot from any app into a new session.

Discuss is open to everyone, in the sidebar

Discuss is a session's comment thread for people only; the agent never reads it. Previously it needed a beta grant and opened as a modal that covered the transcript. Now anyone who can open a session can read and comment, and the thread sits in the sidebar's Discuss tab beside the transcript.

On a session, click Discuss in the dock or the Discuss tab in the sidebar.

  • Files on comments. Attach files to a comment to share them with reviewers. The agent can't reach them.
  • Emoji reactions. React to a comment with any emoji. Each reaction shows as a chip with a count, and hovering it shows who reacted.
  • Mentions bring people in. @-naming someone in a comment adds them to the session and notifies them in Needs you and by Slack DM.
  • On a phone. Discuss opens the Details sheet at full height on the Discuss tab, with the comment box on screen.

Save the people you work with as a group

Previously you added the same people to every project one at a time, and a saved people filter on Team was yours alone. Now a saved set of people is a Group. Keep it to yourself or open it to everyone in your organization, then add all its members to a project or session in one pick.

In any people picker, tick two or more people and click Save these N as a group.

  • Pick a group anywhere. People pickers list groups alongside people and teams, so one Add brings in everyone. Save as group on a project's collaborators card, or Start from a team, copies people you already have.
  • Catch up in one click. Adding a group copies its members at that moment. When the group changes later, the project card shows who joined or left, and Catch up applies the change.
  • `@mention` a whole group. Typing @finance in a message or comment reaches every member of the open Finance group, each person once.
  • Group pages. Each open group has a page listing its members and the projects it's on. Reach it from ⌘K, from the "via" chip on a collaborator, or from a person's profile.
  • In the terminal. evergreen groups create, add, remove and share manage groups. evergreen share --group adds one to a session.

Evergreen 0.4.0

See which sessions are waiting on you

Previously, when the agent answered without opening a pull request, the session read Completed even though the agent was still listening. Now it stays live with an amber Waiting for you badge while the agent stands by for 30 minutes, then settles to Completed.

  • One Running lane. The Waiting for a human lane is gone. Running lists the sessions waiting on you first, each saying what it needs: Approve the plan, Answer a question or Reply to continue.
  • A countdown in the composer. The message box reads “The agent waits 20 more min for your reply.” A reply sent in that window reaches the agent within seconds.
  • Told when it answers. The bell says Answered — reply to continue as soon as the turn ends, and Slack posts “💬 The agent answered.” instead of waiting for the window to close.
  • In the terminal. evergreen ls and evergreen status show Waiting for you with an idle m:ss countdown, and evergreen wait returns as soon as the agent is waiting on you.

Search finds your sessions by meaning

Search now ranks your own sessions first and groups results under Yours, Shared with you, Your team and Everyone in your organization. It matches by meaning as well as words, so “the flaky Playwright test” finds a session titled “e2e spec is unstable in CI”.

Press ⌘K (Ctrl+K), or open the Search page. In a terminal: evergreen search .

  • Ask in plain words. Type “my failed web app runs last week” and search turns it into filters, shows Understood as, and offers Search the words as typed to take it back.
  • Why each result is there. Each row shows the line that matched, captioned Task, Summary, Said, Pull request or File. A passage found by meaning is captioned Related.
  • Look-alikes fold together. Sessions with near-identical titles collapse under one row that reads “3 more with this title”.
  • In the terminal. evergreen search reads a plain sentence the same way and says Understood as. Add --literal to search your exact words.

Evergreen runs as an app on your phone

Add Evergreen to your phone's Home Screen and it opens as an app, starting on a launch screen with its icon instead of a blank page. Session pages now fit a phone held upright or turned sideways.

Open Evergreen on your phone and add it to your Home Screen.

  • Swipe a session row. Swipe right to Mark completed or Pin, swipe left to Archive or Restore. A long swipe runs the action at once, and each one is a tap to undo.
  • Pull to refresh. Pull down from the top of a list or transcript to refresh it. Long lists load their next page as you scroll toward the end.
  • Gestures that get around. Swipe to leave a session, drag the Details sheet open and closed, and tap the top bar to scroll back up.

The terminal client is open to everyone

Previously the terminal client needed a Terminal grant from an admin. Now anyone signed in to Evergreen can install it and open any session they can see, with the live transcript and cards answered from the keyboard.

On a session, click Handoff › Open in terminal, copy the install line, then run evergreen login.

  • Home in a terminal. evergreen ls lists your sessions on this checkout's repo in Home's lanes, Pinned first. Add -s shared, -s all or -s everyone to widen it.
  • Manage sessions from the shell. evergreen pin, archive, rename, share and fork do what the web's buttons do. Archive asks first; add --yes in scripts.
  • Keys like Claude Code. ← on an empty box goes back to the session list. Ctrl+C clears your draft and a second press exits. Esc interrupts the agent only on a second press.
  • Dictate on a Mac. Run /voice once, then hold Space to talk into the box. The Mac's own recognizer does the work, so no audio reaches Evergreen.

Connect Kubernetes without asking for access

Previously the Kubernetes integration was a beta that needed an admin's grant. Now anyone can connect it, and kubectl in your sessions runs with your own cluster permissions, writes included, wherever your team's access reaches.

Integrations › Kubernetes › Connect

  • Asks before changing anything. The agent prefers reads and names the cluster and namespace before any apply, delete, scale, exec or Secret read, unless your approved plan names that exact change.
  • Kept off production. The agent is told never to write to a production cluster and never to copy Secrets or customer data into commits, pull requests or messages.
  • What is not checked. Evergreen does not inspect kubectl commands. After a plan is approved, or in an unattended session, they go straight to the cluster.