目錄
This article reflects information available as of August 2026. Notion’s website copy and product features may change at any time.
In early August 2026, a post on r/Notion pointed out that Notion had changed the messaging on its homepage. A few months earlier, the most prominent headline was still “Meet the night shift,” emphasizing that Notion Agents could keep working around the clock. Now, the first line on the homepage reads “Where teams and agents Think together,” placing human teams and AI agents in the same frame. The change is real, but interpreting it as Notion abandoning the idea of “AI taking over work” and fully returning to a human-first message would go too far. Scroll further down the current homepage and it still says that Custom Agents can keep work moving 24/7, while messaging such as “You assign the tasks. Notion Agent does the work” remains intact. What has changed is the emphasis at the very top of the homepage: AI is still there, but it is no longer standing alone at center stage.
At the same time, WIRED published “Why Normal People Aren’t Using AI Agents” on August 7, examining why AI agents, despite being discussed in Silicon Valley for more than a year, still have not entered everyday life the way conversational tools such as ChatGPT have. Looking at these two developments together, the more reasonable interpretation is not that “AI agents have failed,” but that product companies are starting to confront the same problem: what models are technically capable of doing and what ordinary users are actually willing to delegate are two different things. For teams planning a Notion workspace or evaluating Custom Agents and other AI agents, this gap is more useful to study than whichever slogan happens to appear on the homepage.
Did Notion Really Change Its Message? The Homepage Headline Did Shift from “Night Shift AI” to Teams and Agents
The Old Homepage Led with “Meet the night shift,” While the New One Says “Where teams and agents Think together”
The Reddit post summarized Notion’s old and new messaging as “AI employees take over everything” versus “empowering humans.” That phrasing is clearly sarcastic and is not a verbatim quotation from Notion’s website. However, the shift in homepage positioning can be confirmed from publicly available pages. The previous version led with “Meet the night shift,” followed by copy explaining that Notion agents could keep work moving 24/7, handling knowledge, answering questions, and advancing projects while users slept. The current homepage instead leads with “Where teams and agents Think together,” and the subheading has also shifted toward organizing context, finding answers, and automating work through “AI built for your team.”
This is a noticeable change in marketing emphasis, but it is not enough to say that Notion has abandoned its positioning around autonomous agents. The current homepage still includes “Keep work moving 24/7.” Custom Agents are still described as tools that can automatically handle repetitive work, and the Notion Agent section explicitly says, “You assign the tasks. Notion Agent does the work.” Notion’s July 1 product update also continued to promote External Agents that can automate entire workflows end to end. A more accurate description is that Notion has changed the first impression on its homepage from “AI works while you sleep” to “people and agents collaborate in the same workspace,” while the product strategy itself remains heavily invested in agents.
Why Does WIRED Say Ordinary People Still Aren’t Using AI Agents?
The Problem May Not Be Model Capability, but the Lack of Agent Products Enough People Want to Use Every Day
WIRED’s August 7 report interviewed Josh Miller, CEO of The Browser Company, whose observation was straightforward: AI agents have been discussed in technology circles for a long time, but most ordinary users have never meaningfully used one. Coding agents from companies such as OpenAI and Anthropic already have large user bases, but they still operate on an entirely different scale from conversational products such as ChatGPT and Gemini, which are approaching audiences measured in the hundreds of millions or more.
Miller argues that the problem is not necessarily that models are not smart enough. Instead, the technology industry is too quick to begin with the question of “what can the model do now?” and then design a product around that capability, expecting ordinary users to catch up. He sees an agent as a technical architecture rather than a product consumers inherently want to buy. People do not use a tool simply because it happens to be powered by an agent. What makes a product stick is whether a specific feature removes a real inconvenience without requiring users to learn a new discipline of “how to manage an AI agent.”
That is also what makes Notion’s homepage change interesting. There is no evidence that Notion changed its copy because of this WIRED article or because of a particular usage metric, so the two should not be connected as cause and effect. But they happen to converge on the same product question. The earlier phase of agent marketing heavily emphasized ideas such as “working 24 hours a day,” “autonomously completing tasks,” and “automating entire workflows.” Now, language such as “team,” “together,” and “where your team works” is becoming more prominent. The product capabilities have not disappeared, but the marketing has started putting people back into the picture.
Why Is This Timing Particularly Interesting? The Notion Community Is Actually Discussing Several Different Problems
A Technical Consultant’s Criticism Is Not “Notion Is Bad,” but “Do Not Use It as the Backend for Everything”
During the same week, an r/Notion user describing themselves as a tech stack consultant shared observations from their work. Their view of Notion was actually fairly positive: centralized documentation, SOPs, knowledge bases, and small-team collaboration remain areas where Notion performs well. Notion AI also has practical value for organizing meeting notes, revising drafts, and searching internal information. Their reservations emerge around complex automation and data-intensive processes. Based on their experience, once Notion is used for multi-layer conditional triggers, complicated CRM systems, or backend operational workflows, limitations in databases and automation begin to become more obvious. As a result, they prefer to keep Notion in the knowledge and collaboration layer rather than turning it into the company’s core operational engine. This is the practical view of one consultant and cannot represent all Notion users, but it draws a useful distinction between “the tool can do this” and “the tool is suitable as the core system for this.”
The same distinction applies to AI agents. Custom Agents may be capable of performing multi-step work across pages, databases, and external tools, but that does not mean every workflow should be rebuilt around an agent. Once a previously simple requirement needs a large amount of prompting, permissions, trigger conditions, and exception handling, what increases may not be efficiency, but another system that someone has to maintain.
“How Humans and Agents Work Together” Is Becoming a New Product Question, but One Post Should Not Be Treated as Industry Consensus
Another long post on r/Notion was titled “As Planning Shifts From Human-to-Human to Human-to-Agent, How Do We Keep the Human at the Center?” It discussed what happens when work becomes distributed across coding agents, research agents, planning agents, and review agents. The author argued that people may actually lose visibility into what is happening across a project. Different tasks are scattered across terminals, chat windows, and individual agents. One agent may know something another does not. Work is technically progressing, but the human operator’s understanding of the overall project may decline.
One additional piece of context is necessary here: the second half of the post promotes Orbit, a product the author is developing. It therefore should not be treated as independent user research or as a consensus within the Notion community. The underlying problem it raises, however, is still practical. As the number of agents increases, a workspace needs to handle more than simply “which tasks can be automated.” It also needs to show what an agent did, which decisions require human confirmation, and who is ultimately accountable. If those things are not reflected directly in the structure of the workspace, users can easily end up seeing a stream of completion notifications without understanding what happened in between.
Notion Is Talking About AI Agents While Its Community Is Still Asking for Small Basic Features
Sub-Items Can Be Displayed in Different Ways, but There Is No Documented Setting to “Always Expand Everything by Default”
On August 6, another user asked why it is still not possible to have all Sub-items remain expanded by default when opening a database. This is not a new request. Users have been asking similar questions for years. Notion currently supports display options such as Nested in toggle and Flattened list, and filters can be configured to show Parents, Sub-items, or both. However, Notion’s official documentation does not currently provide a persistent setting that automatically expands every Sub-item whenever a database is opened. As a result, the community continues to rely on filters, templates, and alternative view configurations to work around the limitation.
Putting a request like this next to “AI agents working automatically 24 hours a day” creates a striking contrast, but it is also a normal part of software products. The friction users actually encounter every day is often not whether a model can execute ten steps autonomously, but why the same toggle has to be opened again every time.
Notion Has People Profiles, but No Documented Personal “Out of Office” Status
Another user raised an even more everyday issue. Because they communicate with some clients entirely through Notion, they realized while preparing for a vacation that Notion does not offer a personal status similar to Slack or Teams, where a profile picture can display something like “away until X” or “slower replies this week.” Notion already has People profiles that show a member’s collaborators, Teamspaces, and recent activity, but its current documentation does not list personal availability, out-of-office, or custom status fields. One workaround suggested in the discussion is to place a permanent availability section on every client homepage or project template.
This is a small feature request, but it is useful for thinking about what “teamwork” actually requires. People and agents may be able to process data together, generate reports, and update tasks, but sometimes collaboration simply requires letting another person know, “I’m away for the next two days.” AI is not necessarily the missing piece.
When Planning a Notion Workspace, Separate Automation, AI, and Human Judgment
If a Database, Formula, or Automation Can Solve the Problem, It Does Not Need to Become an Agent First
Notion Custom Agents are well suited to situations that require reading context, interpreting unstructured text, deciding what to do next, or coordinating work across tools. If the requirement is simply “update the date when the status changes to Done,” “place certain items into a specific View,” or “categorize records based on a field,” a regular database configuration, Formula, Button, or Automation is usually easier to predict and maintain.
A simple question can help when planning a workspace: does this process actually require AI judgment? If the answer is only a fixed condition leading to a fixed result, adding an agent simply introduces extra prompts, Credits, model choices, and error handling.
For Workflows Involving Agents, Build Human Review Directly into the Data Structure
Processes that genuinely need AI judgment do not need to be fully autonomous. For customer replies, important data changes, payment information, or formal external documents, the database can include a Status such as AI Draft → Human Review → Approved, along with fields such as Reviewed by and Approved at. This is more reliable than simply reminding the team to “remember to check the agent’s output,” because the human review step has become part of the workflow itself.
Notion’s current homepage places “teams and agents” together, and this is a useful way to interpret that message in practice. Which parts belong to the agent and where humans take over do not need to remain a branding slogan. They can be built directly into the database and permission structure.
External Collaboration Still Needs Clear Human Availability
If clients, suppliers, or other external collaborators work directly through Notion, a shared homepage can include a permanent Availability section showing current status, expected response times, and an alternate contact person. This does not require waiting for Notion to add a native feature, and it is more reliable than expecting the other person to infer availability from slower comment replies.
The same principle can be applied to agents. Alongside human status, each important agent can display Active / Paused / Needs Review / Error, making the current operating state of the system visible inside the workspace rather than known only to administrators.
Notion’s homepage redesign does reveal a shift worth observing: “Meet the night shift” has become “Where teams and agents Think together.” However, the current product pages still heavily promote 24/7 Custom Agents, automated task execution, and end-to-end workflows. This is not evidence that Notion is retreating from its AI Agent strategy. It looks more like a recalibration of how agents should be introduced to ordinary teams.
The question WIRED raised during the same week offers another useful angle. Ordinary people will not change the way they work simply because “Agent” is a technical term. What matters is whether a specific feature removes a specific inconvenience. Workspace design works the same way. Identify the things that are genuinely frustrating in daily work first, then decide whether the right solution is a database, Automation, Agent, or human process. That is much more practical than deciding that “the company needs to become agentic” and then looking for work to feed into agents.
FAQ
The main confirmed change is that the homepage headline shifted from “Meet the night shift” to “Where teams and agents Think together.” The older version placed 24/7 Agents at the front of the message, while the newer version first emphasizes teams and Agents working together. However, the lower sections of the current homepage still include “Keep work moving 24/7” and messaging around Custom Agents automatically handling work. This is therefore a change in marketing emphasis, not the removal of Notion’s Agent positioning.
There is currently no evidence of that. Notion continued introducing and promoting features related to External Agents, Workers, and Custom Agents in July, including explicit messaging around end-to-end workflow automation. What has changed so far is the homepage narrative, not the underlying product direction.
One of the main explanations raised in WIRED’s report is that the industry still lacks enough agent products that are genuinely compelling to ordinary users. An agent is closer to a technical architecture than a consumer-facing value proposition. Users care whether a product directly solves a concrete problem, not whether the technology underneath it happens to qualify as an agent.
Notion currently offers Sub-items display modes such as Nested in toggle and Flattened list, but its current official documentation does not list a setting that permanently expands every Sub-item by default. Community members still rely on filters, templates, or View adjustments to achieve similar results.
Notion already has People profiles, but its current official feature documentation does not list fields for Out of office, vacation periods, or custom availability status. If vacation information needs to be visible to clients or teammates, a permanent Availability section can be added to a shared homepage or project template.