[태그:] Workflow Automation

  • Build a One-Person AI Secretary with Claude Cowork: Automated Gmail, Notion, and KakaoTalk Briefings

    Build a One-Person AI Secretary with Claude Cowork: Automated Gmail, Notion, and KakaoTalk Briefings

    If you use Claude only as a “chatbot that answers questions,” you will hit its limits quickly. The story changes when you build a structure that reads your email, organizes your tasks, checks your schedule and the weather, and reports to you every morning. Based on the flow of the Soso AI Beginner Notes video, this article explains how to connect Claude Cowork with Gmail, Notion, and PlayMCP to create a one-person AI secretary workflow.

    Example of a Claude AI daily briefing delivered through KakaoTalk
    Example of an AI daily briefing delivered through KakaoTalk · Screenshot from the original video

    The key is not the prompt, but the flow of recurring work

    The most important part of the video is not “one great prompt.” It is the full workflow: reading email in Gmail, drafting replies, organizing tasks in Notion, then connecting weather and KakaoTalk briefings through PlayMCP.

    That difference matters. With one-off questions, a human has to explain the situation again every time. A work flow, on the other hand, can run at the same time each day, by the same standards, in the same output format once it has been designed. This is where the difference appears between people who use AI for work and people who build work systems with AI.

    Step 1: Connect Gmail in the Claude desktop app

    First, open the custom menu in the Claude desktop app and choose Connectors. In the video, after connecting the Gmail connector, the user asks Claude Cowork in collaboration mode: “Tell me about the four most recent emails.”

    Claude Gmail connector setup screen
    Claude Gmail connector setup screen · Screenshot from the original video

    Two useful capabilities become obvious right away.

    • It can summarize recent emails so you can quickly understand what needs attention today.
    • For messages that need replies, it can create draft responses so the user only has to review and send them.

    However, email contains a lot of sensitive information. At first, try connecting test emails or low-importance messages. It is also safer to create a separate work folder that Claude can access and keep important documents out of that folder.

    Step 2: Automatically organize tasks in Notion

    Checking email alone does not make an assistant. The assistant has to pull the work hidden inside those emails and move it into an actual task list. In the video, after connecting the Notion connector, the user asks: “Create this week’s work schedule as a to-do list page in my Notion.”

    Building a Notion work flow in the Claude collaboration screen
    Building a work flow in the Claude collaboration screen · Screenshot from the original video

    The advantage of this step is that the inbox and the task list stay connected. Usually, things get missed when we read email, make a separate note, and then move it again into Notion or a to-do app. If Claude reads and structures the email content, the human only has to decide priority and whether to act.

    You do not need to build a complicated dashboard from the beginning. Simple fields like the ones below are enough.

    • Task name
    • Related email or requester
    • Deadline
    • Priority
    • Status
    • Next action

    Step 3: Add KakaoTalk, weather, and map information with PlayMCP

    If Gmail and Notion organize work information, PlayMCP expands the connection to external tools. In the video, the user adds KakaoTalk’s chat with myself, KakaoMap, and weather tools to the PlayMCP toolbox, then connects them with Claude.

    Selecting weather and KakaoMap tools in PlayMCP
    Selecting weather and KakaoMap tools in PlayMCP · Screenshot from the original video

    With this connection, the briefing becomes much more practical for daily life. For example, you can ask: “Check today’s weather forecast, find five good restaurants near the off-site work location mentioned in Gmail, and send them to me on KakaoTalk.” It becomes not just a work summary, but actual decision-making material for starting the day.

    There is also something to be careful about here. Map, weather, and messenger tools are connected to permissions for external services. You must check which account is logged in, which permissions are granted to each tool, and where any automatic messages will be sent.

    Step 4: Run it every morning with a skill and a scheduled task

    The final exercise in the video is to create a daily briefing skill inside Claude and set it to run every day as a scheduled task. Once created, the skill remembers an order such as “check email → draft replies → update Notion → check weather and off-site information → report through KakaoTalk.”

    Daily briefing result automatically sent through KakaoTalk
    Daily briefing result automatically sent through KakaoTalk · Screenshot from the original video

    When a scheduled task is added, the user no longer has to type the prompt every time. While you are getting ready for work in the morning, AI can prepare the day’s materials first.

    At this point, skipping approval or enabling automatic execution is convenient, but it also increases risk. Start by testing with manual runs, check that no wrong emails are sent and no sensitive information is exposed, and only then raise the level of automation.

    Checklist before you follow along

    Before applying this workflow directly, organize the following four points first.

    1. Decide which work repeats every day. High-frequency tasks such as checking email, organizing schedules, drafting reports, and responding to customers are good candidates.
    2. Separate the accounts and data ranges that AI may access. Instead of opening your entire personal mailbox immediately, define a test scope first.
    3. Choose one channel where you will receive the output. Decide whether you will check it in KakaoTalk, Notion, or email so the flow stays simple.
    4. Run at least three manual tests before enabling automatic execution. Check summary quality, omissions, permissions, and message recipients.

    Who this method fits, and who should wait

    This method works well for people who have a lot of recurring work and move between several tools. If you check email every day, have meetings or off-site work, and already use a task management tool such as Notion, you can see the benefits quickly.

    On the other hand, if concepts such as Claude desktop, Notion, and MCP still feel unfamiliar, it is better not to connect everything at once. Start by connecting only Claude and Gmail and testing email summaries and reply drafts. Then add Notion, and finally add PlayMCP and scheduled tasks. That is the safer order.

    Recommended reading

    Frequently asked questions

    How is Claude Cowork different from regular chat?

    Regular chat is conversation-centered. Cowork, or collaboration mode, is closer to building a workflow that uses specific folders, files, connectors, and tools together. In the video as well, the user designates a work folder through the collaboration button in a new chat, then continues with email and file work.

    Is it safe to connect Gmail and Notion?

    The scope of permissions and your usage habits matter more than the tool itself. Do not automate every email and document from the beginning. Start with a test folder and low-risk work. For automatic sending features in particular, it is safer to keep a manual review step.

    Is PlayMCP required?

    To connect tools outside Claude’s basic connectors, such as KakaoTalk, KakaoMap, and weather, you may need an external tool-connection layer like PlayMCP. If you only want email summaries and Notion organization, you can start without PlayMCP.

    Can I turn on automatic execution every morning right away?

    It is not recommended. First, check the results with manual execution and confirm that sensitive information is not exposed and messages are not sent to the wrong chat room. After that, it is safer to add a scheduled task and automate it.

    Is this article a direct transcript of the original video?

    No. It is based on the practice flow of the original video, but it reduces the promotional latter section and reorganizes the setup order and cautions from the perspective of practical work automation.

    References

    Original Korean article: Claude Cowork one-person AI secretary workflow

    Image source: Captured images used in this article are stills from the original YouTube video. They are used for review, commentary, and educational explanation, and copyright remains with the original rights holders and the channel.

  • AI Agent Automation: What Matters More Than the One-Click Illusion

    AI Agent Automation: What Matters More Than the One-Click Illusion

    AI automation stories are getting inflated far too easily these days. Lines like “run a company with 50 AI agents,” “work only one hour a day,” and “leave a comment and I’ll send you the automation recipe. Makes money” keep appearing in our feeds.

    EO Korea’s interview with Gumloop founder Max Brodeur-Urbas puts a firm brake on that trend. The person in the video is the founder of an AI automation platform company that has raised major funding. Yet the point he repeats is surprisingly sober. AI is not a shortcut that lets you skip understanding. It is a tool that helps you execute faster on work you already understand.

    Gumloop founder Max Brodeur-Urbas criticizing exaggerated claims about AI automation in an interview
    Screenshot from EO Korea. Rather than simply summarizing the video, this article analyzes the real conditions for AI agent automation by reading the Gumloop case alongside external sources.

    The Problem With AI Agent Automation Is Not the “Number of Agents”

    Early in the video, Max treats claims such as “AI agents run the whole company” almost as marketing. The target of his criticism is not AI itself. The problem is the way automation is sold as if it can eliminate the need for understanding and trial and error.

    Gumloop’s official website aligns with this view. It puts forward the message that understanding the work should be the only prerequisite for automation. In other words, the point is to make automation possible for people who are not developers. But that person still needs to understand, at least at a basic level, the work they are trying to automate.

    This distinction matters. AI agent automation is not exactly a “do-anything assistant” that takes over whatever you want. It is closer to execution infrastructure that connects multiple tools, data sources, approval steps, and repetitive tasks into one flow.

    The New Automation Market Revealed by the Gumloop Case

    Y Combinator’s company page describes Gumloop as a platform. Uses AI to automate repetitive, complex workflows end to end. Users create automations by connecting modules through drag and drop. The goal is to let teams test and operate workflows faster than they could by writing code.

    Reports from EO, TechCrunch, and BetaKit point in a similar direction. In March 2026, Gumloop raised a $50 million Series B led by Benchmark. Its total funding was described as roughly $70 million. More important than the number itself is the market direction investors are seeing. A market where employees inside companies build AI agents themselves and package repetitive work into an operational form.

    Max Brodeur-Urbas explaining Gumloop's founding background and product direction in an interview

    What makes Gumloop interesting is that it does not only talk about competition over model performance. Its official site highlights concrete work agents such as data analysis, support ticket classification, CRM management, meeting preparation, and call analysis. Instead of abstract AGI, the repetitive work of actual departments comes first.

    Four Reasons One-Click Automation Fails

    AI agent automation usually does not fail for one simple reason such as insufficient technology. When we combine the video with external materials, four conditions become visible.

    1. If You Do Not Understand the Work, You Have No Standard for Automation

    Even if AI produces an output, someone still needs to judge whether that output is correct. Sales lead classification, customer inquiry triage, report writing. Meeting preparation all have different standards from one organization to another. Without business context, automation becomes fast error, not fast execution.

    2. Without Data Connections, Agents Are Empty-Handed

    Enterprise automation does not end with a single chatbot. CRM systems, documents, email, databases, ticket systems, and calendars need to be connected. This is why platforms like Gumloop emphasize connections and execution flows more than the model alone.

    3. Repeated Execution Requires Control and Observability

    A prompt that succeeds once is different from a work automation that runs every day. Repetitive work requires failure alerts, approval steps, logs, and permission management. As the number of AI agents grows, organizations need to be able to see who did what.

    4. Automation Does Not Replace Learning

    Max distinguishes between using AI as a learning tool and using it to skip understanding. AI can explain and assist. But if the user has no idea why a result came out the way it did, automation becomes an expansion of dependency, not an expansion of capability.

    What Non-Developer Automation Really Means

    The non-developer automation Gumloop talks about does not mean “anyone can build anything in any way.” More precisely, it means the person responsible for the work does not need to translate every requirement and hand it off to an engineer.

    Marketers understand campaign lead flows. Salespeople know the annoying parts of CRM updates. HR teams know the recurring candidate communications. Operations teams know where exception handling breaks down. If these people can become the designers of automation, the speed of AI adoption inside a company can clearly increase.

    But there are conditions here as well. The organization needs to decide how much automation authority it will grant. It must define which data can be accessed. Actions require approval before execution, and who is responsible when something fails. Adopting AI agents is not simply buying a tool. It is a redesign of the operating model.

    A Checklist Before Starting AI Workflow Automation

    If you or your organization want to adopt AI agent automation, it is better to start by asking these questions:

    1. Does the repetitive work actually exist?
    2. Can the person responsible explain the success criteria for that work in words?
    3. Can the required data and tools be connected?
    4. Is there a mechanism to stop or review the process when it fails?
    5. Is there a feedback loop for improving automation results?

    Without these five conditions, increasing the number of agents does not mean much. If those conditions are present, however, even one small automation can change how an organization works.

    Max Brodeur-Urbas explaining the importance of execution and people near the end of the interview

    Further Reading From Thinknote on AI Agents

    This perspective also connects with Thinknote’s existing articles on AI agents.

    Conclusion: AI Agents Are More About Operations Than Replacement

    The message from the Gumloop founder interview is simple. The promise that AI will take care of everything for us is attractive, but dangerous. Real value appears when we use AI to execute work we already understand more quickly and reliably.

    That is why the key question for AI agent automation is not “How many agents are you using?” A better question is this:

    Do I understand the work I want to automate well enough? And does that automation have enough verification, permission, and feedback structure to run safely every day?

    When you can answer those questions, AI agents stop being a buzzword and become infrastructure for a new way of working.

    FAQ

    What is AI agent automation?

    AI agent automation is a way of using AI models to connect repetitive work, data processing, cross-tool tasks, notifications, reporting, classification. Similar activities into one execution flow. Compared with a simple chatbot, what matters is its ability to connect with work systems and actually execute tasks.

    What kind of company is Gumloop?

    Gumloop is a platform that lets non-developers create AI-based work automations by connecting modules. Its Y Combinator company page and official site describe the company as focused on using AI to automate repetitive, complex workflows.

    If we have AI agents, do we no longer need to understand the work?

    No. As Max Brodeur-Urbas emphasizes in the video, AI is closer to a tool. Helps people execute work they already understand faster, rather than a replacement for understanding. Humans still need the standards for evaluating and improving the result.

    What should companies look at first when adopting AI automation?

    They should first look at whether repetitive work exists, whether success criteria are clear, whether the data can be connected, whether permissions can be managed. Whether there is a review structure for failures. Tool selection comes after that.

    What is the difference between an AI automation platform and a regular chatbot?

    A regular chatbot focuses on conversation and answers. An AI automation platform focuses on operating workflows. Include data sources, work tools, repeated execution, approval steps, and result records.

    References

    Image source: Captured images used in this article are stills from the original YouTube video. They are used for review, commentary, and educational explanation, and copyright remains with the original rights holders and the channel.

  • Agentic Engineering: What Comes After Vibe Coding?

    Agentic Engineering: What Comes After Vibe Coding?

    This is a fuller English adaptation of the Korean article on agentic engineering after vibe coding. The source uses Andrej Karpathy’s discussion as a starting point, but its main focus is practical: when anyone can generate code with AI, real engineering shifts toward specification, verification, environment design, and responsibility.

    agentic engineering after vibe coding
    Agentic engineering moves developers from typing code to directing and verifying AI agents.

    Original Korean article: 에이전틱 엔지니어링: 안드레이 카파시가 말한 바이브 코딩 이후의 개발 방식

    Why Agentic Engineering Has Become Important

    A turning point after late 2025

    The article argues that AI coding entered a new phase as models became capable of longer, tool-using work. Vibe coding showed that natural language can produce working prototypes. But when prototypes move into production, teams need more than vibes. They need a way to assign tasks to agents, constrain them, test outputs, and recover from mistakes.

    Agentic engineering names this emerging discipline. It is not just writing prompts. It is designing the full loop in which an AI agent receives a goal, uses tools, modifies artifacts, checks results, and reports its reasoning for human review.

    What Software 3.0 Means

    Code is not only in files

    Software 1.0 was explicit code written by humans. Software 2.0 often referred to learned weights and data-driven behavior. Software 3.0, as discussed in the source, includes prompts, tool interfaces, workflows, evaluations, context, and agents as part of the software system. The product is no longer only a repository of files.

    This changes what engineers must version, review, and test. A prompt template, an evaluation dataset, an agent routine, or an MCP tool schema can be as important as a function in a codebase. If these pieces are invisible, the system cannot be operated reliably.

    Vibe Coding Lets Anyone Build, but Real Work Is Different

    What the MenuGen example shows

    The Korean article mentions the kind of example where a non-specialist can create an app or interface quickly with AI. This is the promise of vibe coding: describe the feeling, iterate visually, and get a working result. It expands who can make software.

    However, production work still involves edge cases, data integrity, security, accessibility, performance, maintenance, and user support. Vibe coding is excellent for exploration, but the moment a product affects customers or business operations, engineering discipline returns.

    What humans still must own

    Humans remain responsible for goals, ethics, tradeoffs, and accountability. An agent can implement a feature, but it does not own the consequences of a privacy breach, a bad medical recommendation, or a financial error. The source article emphasizes that the human role rises toward judgment rather than disappearing.

    Agentic Engineering Is the Skill of Specification and Verification

    Software 3.0 and AI coding tools
    Software 3.0 uses prompts, context, and LLMs as a new programming layer.

    The core practice is writing specifications that agents can execute and humans can verify. A good specification includes context, expected behavior, constraints, examples, non-goals, test commands, and acceptance criteria. It should also define what the agent must not change.

    Verification is equally important. Teams need unit tests, integration tests, golden examples, simulations, benchmark tasks, human review gates, and rollback plans. The question is not whether the AI produced something impressive. The question is whether the team can prove the result is correct enough for the intended use.

    Verifiable Environments Are the Core Product Opportunity

    What founders should watch

    The article identifies a business opportunity: environments where AI agents can safely perform work and be evaluated. In coding, this may mean sandboxes with tests. In design, it may mean versioned assets and approval flows. In enterprise operations, it may mean permissioned data connectors and audit logs.

    Founders should look for workflows where the output can be checked. If a task has clear evaluation signals, agents can improve quickly. If the task is vague, subjective, or legally sensitive, human review must remain central.

    Where AI-Native Developer Differences Come From

    vibe coding and production software gap
    Vibe coding makes creation easier, but production work still needs structure.

    Productivity is not typing speed

    The difference between developers will not be who types fastest. It will be who decomposes problems better, gives agents the right tools, reads output critically, and builds reusable workflows. A strong AI-native developer can run several streams of work while maintaining quality gates.

    Agent-First Infrastructure Is Needed

    Human UI and agent interfaces are different

    Many current tools are designed for human clicks. Agents need structured APIs, logs, machine-readable state, reversible actions, and narrow permissions. Agent-first infrastructure does not mean removing humans; it means making work legible to both humans and machines.

    Conclusion: Developers Do Not Disappear; Their Role Moves Up

    AI agent verification workflow for developers
    Agentic engineering depends on specifications, tests, and verification.

    The source article’s conclusion is optimistic but disciplined. AI expands who can create software, but reliable software still requires engineering. Agentic engineering is the next layer: designing environments where AI agents can work productively while humans retain responsibility for direction and verification.

    Related Reading

    Continue with these related Thinknote English articles in the Digital Transformation cluster.

    FAQ

    What is this article about?

    This article explains a digital transformation, platform, market-structure, or technology-adoption topic with Korea-specific context and global implications.

    How should I use this guide?

    Use it to understand market signals and strategic patterns. Combine it with current market data before making business or investment decisions.

    Where can I read the original Korean article?

    The original Korean article is available here: Agentic Engineering: What Comes After Vibe Coding?.

  • AI-Native Workflows: How to Rebuild Work Around a Digital Brain and AI Agents

    AI-Native Workflows: How to Rebuild Work Around a Digital Brain and AI Agents

    This fuller English adaptation follows the Korean source on becoming AI-native. The main argument is that AI-native work is not about collecting many AI tools. It is a change in the working environment: building a digital brain, connecting agent workflows, and redesigning repeated tasks so that AI can help execute them.

    AI-native workflows with a digital brain and AI agents
    AI-native workflows start by connecting knowledge, context, and AI agents.

    Original Korean article: AI 네이티브 전환법: 디지털 두뇌와 AI 에이전트로 일하는 방식 바꾸기

    AI-Native Work Is an Environment Shift, Not Tool Usage

    Many people think they are AI-native because they use a chatbot, an image generator, or a meeting summary tool. The source article argues that this is only tool usage. AI-native work begins when information, decisions, templates, and routines are organized so AI can continuously support real work.

    In other words, the focus moves from “Which app should I try?” to “How should my work be structured so that AI can understand it, act on it, and improve it?”

    Why Make the Transition Now?

    The reason is speed. Work increasingly rewards people who can collect information, make decisions, produce drafts, and revise quickly. AI can accelerate all of these, but only when the user has prepared context. Without context, AI gives generic answers. With a well-built work system, AI becomes a collaborator that knows the user’s materials and standards.

    A Digital Brain Is the Starting Point

    1. Gather work materials in one place

    The digital brain is a structured collection of notes, documents, examples, decisions, references, checklists, and project memory. It may live in Obsidian, Notion, Google Drive, a local folder, or another system. The tool matters less than the habit of keeping reusable knowledge accessible.

    2. Document repeated work

    Repeated tasks should be written down: how reports are made, how emails are answered, how meetings are prepared, how research is checked, and how approvals happen. Documentation turns invisible experience into AI-usable context.

    Agent Workflows Matter More Than Chatbots

    digital brain for AI-native knowledge work
    A digital brain gives AI agents reusable context instead of isolated prompts.

    A chatbot answers once. An agent workflow can take a goal, read context, create an output, ask for review, revise, and store the result. The Korean source emphasizes that the workflow is the unit of transformation. A company does not become AI-native because employees ask random questions. It becomes AI-native when repeated work is redesigned around AI-supported loops.

    3. Give AI both roles and standards

    Good AI work requires more than a task request. The user should provide a role, audience, source materials, constraints, tone, examples, and quality criteria. This reduces generic output and makes review easier.

    Look at Automatable Work Structure Before Code

    Non-developers often assume automation requires programming first. The source article says the first step is identifying structure. Which tasks repeat? Which inputs are used? What decisions are made? What outputs are expected? Once the structure is clear, automation may be possible through no-code tools, agent workflows, scripts, or integrations.

    4. Store and reuse outputs

    AI output should not disappear after one chat. Useful prompts, drafts, summaries, decisions, and templates should be saved back into the digital brain. This creates a compounding effect: every completed task improves the next task.

    5. Connect small automations first

    Start with small, low-risk automations such as meeting summaries, research briefs, email drafts, blog outlines, file naming, or checklist generation. After these become reliable, connect more tools. The safest transition is incremental.

    A Practical Sequence to Start Tomorrow

    AI agent workflow automation for knowledge workers
    AI agent workflows turn repeated knowledge work into structured automation.
    • Choose one repeated weekly task.
    • Collect the documents and examples needed to perform it.
    • Write the current process as a checklist.
    • Ask AI to produce a draft using that checklist.
    • Review the result and save the improved prompt, output, and corrections.
    • Repeat until the workflow becomes stable, then consider automation.

    The First Benefit: Faster Execution and Clearer Judgment

    The Korean source concludes that AI-native work is not only about speed. It also clarifies judgment. When materials are organized and workflows are explicit, people can see what matters, what should be delegated, and what must remain human. AI becomes useful because the human work system becomes clearer.

    Related Reading

    Continue with these related Thinknote English articles in the Digital Transformation cluster.

    FAQ

    What is this article about?

    This article explains a digital transformation, platform, market-structure, or technology-adoption topic with Korea-specific context and global implications.

    How should I use this guide?

    Use it to understand market signals and strategic patterns. Combine it with current market data before making business or investment decisions.

    Where can I read the original Korean article?

    The original Korean article is available here: AI-Native Workflows: How to Rebuild Work Around a Digital Brain and AI Agents.

  • Knowledge Workers in the AI Agent Era: From Content Producers to Judgment Designers

    Knowledge Workers in the AI Agent Era: From Content Producers to Judgment Designers

    This English version is a fuller translation and adaptation of the original Korean article, “AI Agent 시대, 지식근로자는 어떻게 달라져야 할까,” for global readers. The article explores the changing role of knowledge workers in the AI agent era and how education should adapt to these changes. As AI becomes an integral part of our daily work, the question is no longer about how to use AI, but about how to connect AI to the work context and create valuable results.

    knowledge workers in the AI agent era
    Knowledge workers need new skills when AI agents become part of everyday work.

    Original Korean article: AI Agent 시대, 지식근로자는 어떻게 달라져야 할까

    The Competition Between AI Users and Non-Users is Already Over

    When generative AI first emerged, there was a significant difference between those who used AI and those who did not. However, the situation has changed. AI utilization has become a natural choice in many tasks, such as search, summarization, translation, report drafting, meeting minutes, and image generation. Therefore, the criteria for competition have also changed. It is no longer about whether one uses AI or not, but about how well one uses AI, what tools one uses, how well one formulates questions, how accurately one provides work context, how well one reviews and judges results, and how well one connects with the organization’s work style.

    Context is More Important than Prompts

    When discussing AI utilization, prompts often come to mind first. A good question is indeed crucial, and the more clearly one defines the desired output, role, format, and conditions, the better the result will be. However, prompts alone are not enough. For AI to produce a good answer, it needs to know the purpose of the task, the current situation of the organization, the reference materials, the applicable standards, the intended user of the output, the constraints to be considered, and the final form of the output. The same question can have different answers depending on the context. In tasks where context is crucial, such as curriculum design, policy document review, report writing, and performance management, this is especially true. Prompt engineering is the art of crafting good questions, while context engineering is the process of constructing the necessary context and materials for AI to work. In the AI agent era, an additional step is required: designing the work flow itself so that AI can understand the goal, perform the necessary procedures, and produce the output.

    AI education for knowledge workers
    AI education should connect tools with real work context and judgment.

    The Role of Knowledge Workers Shifts from Content Producers to Judgment Designers

    Knowledge workers are responsible for creating documents, finding and analyzing data, reporting, and supporting decision-making. AI can quickly process a significant part of this work. It can draft reports, summarize long documents, compare data, summarize meeting minutes, and structure ideas. However, this does not mean that the value of knowledge workers disappears. Instead, their role changes. The more important roles that knowledge workers will play in the future include defining problems, providing context, reviewing results, making judgments and choices, and improving work flows. As AI takes over routine tasks, humans must focus on higher-level problem-solving and deeper understanding.

    From Knowledge-Consuming to Knowledge-Creating Organizations

    In the AI era, organizations should not stop at simply acquiring external knowledge. They must accumulate internal experiences, standards, cases, and judgment processes. Educational organizations are no exception. Operating educational programs is not just about managing schedules or recruiting instructors. For education to be connected to actual work performance, knowledge must remain within the organization. This includes materials such as educational program design criteria, course-specific learning objectives, frequently encountered problems in the field, questions and difficulties faced by learners, post-lecture application cases, performance indicators, and areas for improvement in the next education session. AI is strong in organizing and connecting such materials, but it is up to humans to decide what materials are important, how to interpret them, and in which direction to improve.

    human judgment supervising AI agents
    Human judgment becomes more important as AI agents produce drafts and decisions.

    Education Becomes a Process of Developing Problem-Solving Capabilities

    If AI education focuses only on tool usage, it will soon reach its limits. The buttons and functions of tools are constantly changing, and models, pricing plans, and platform strengths also change. Therefore, the center of AI education should shift from explaining functions to problem-solving. Questions that should be addressed in education include what tasks AI can take over, what tasks require human judgment, what materials should be provided to AI for better results, what standards should be used to verify AI results, how to automate repetitive tasks, and what kind of knowledge database should be created at the organizational level. By dealing with these questions, education can go beyond simple “AI utilization” and help learners re-examine their work. Organizations can begin to change their way of working through education.

    Distinguishing Between Tasks that AI Can Replace and Human Value

    AI is fast and strong in reading and creating drafts, comparing and summarizing data, and generating images. However, the results produced by AI are not always valuable. Value comes from human problem awareness, purpose, interpretation, and choice. Tasks that AI can do well can be entrusted to AI, such as drafting, data summarization, table organization, repetitive investigation, sentence refinement, idea expansion, and format conversion. However, tasks that humans should focus on are different, including determining why a task is being done, judging who needs the results, reflecting field context, reviewing risks and responsibilities, selecting the final direction, and converting the results into meaningful experiences for humans.

    organization learning with AI agents
    Organizations need learning systems that turn AI use into shared capability.

    Without Organizational Change, AI Education Alone Has Limited Effect

    Even if AI education is increased, if the organization’s work style remains the same, the effect will be small. This is because individuals will find it difficult to apply what they have learned in actual work. AI utilization is not completed by individual skills alone; work, members, culture, structure, and strategy must move together. Organizations should check the following questions together: what tasks to redesign with AI, what materials to manage as common knowledge, what authority and security standards are needed for AI use, who will take responsibility for reviewing results, how to connect educational outcomes with field application, and how to expand individual experiments into organizational processes. In an era where AI becomes a team member, the organization must also move like a team. The structure of organizational learning and work must change together, beyond individual productivity improvement.

    Efficient Education and Valuable Education Must Go Together

    AI can increase the efficiency of education. Investigation time can be reduced, educational program drafts can be created quickly, and learning materials can be diversified. However, efficiency alone is not enough. The purpose of education is not just to save time but to enable better judgment, deeper understanding, and more practical problem-solving. Efficient education is about operating education quickly, while valuable education is about helping learners behave differently in their actual work. In the AI agent era, these two must be designed together: reducing repetitive tasks with AI, systematically collecting materials, reflecting the learner’s work context, designing problem-solving tasks, connecting results with field application, and accumulating knowledge that remains after education as an organizational asset.

    AI agent era education roadmap
    Education for the AI agent era should redesign work, not only teach prompts.

    Conclusion: The Role of Educators in the AI Era

    In the AI agent era, the role of educators also expands. They move from being operators of education to designers of the organization’s work style. Future education must ask new questions, not stopping at “what AI tools to teach” but going further to “how this organization can create better results with AI.” AI processes tasks quickly, but humans create meaning and judge. Education connects these two. Efficient and valuable education in the AI agent era starts with designing this connection.

    Related Reading

    Continue with these related Thinknote English articles in the Digital Transformation cluster.

    FAQ

    What is this article about?

    This article explains a digital transformation, platform, market-structure, or technology-adoption topic with Korea-specific context and global implications.

    How should I use this guide?

    Use it to understand market signals and strategic patterns. Combine it with current market data before making business or investment decisions.

    Where can I read the original Korean article?

    The original Korean article is available here: Knowledge Workers in the AI Agent Era: From Content Producers to Judgment Designers.

  • Hermes Agent Desktop App: The Next Interface for Mainstream AI Agents

    Hermes Agent Desktop App: The Next Interface for Mainstream AI Agents

    For AI agents to become mainstream, better model performance alone is not enough. They need to meet people in the ways they already work every day. Alex Finn’s video makes this point clearly by showing the Hermes Agent desktop app.

    The video’s wording is somewhat bold. It says the Hermes desktop app is better than the CLI, Telegram, and OpenClaw. From a blog perspective, however, the important question is not which option wins. The question is what kind of interface AI agents need if they are to move beyond chatbots and become real work tools.

    Why a Desktop App Matters

    An AI agent is not simply a tool that generates answers. It reads files, runs commands, creates images, executes scheduled tasks, and carries context across multiple sessions. When that kind of tool is handled only through a command line or messenger commands, the barrier to entry is high for beginners.

    The Hermes Agent desktop app matters because it turns this complex structure into a visible workspace. Users can see sessions, artifacts, skills, toolsets, cron jobs, and profiles in one place. This is a key shift that moves AI agents from developer toys toward everyday work tools.

    The first screen of the Hermes Agent desktop app and an explanation of the limits of the existing CLI
    The first screen of the Hermes Agent desktop app. The video points out the limits of a CLI-centered user experience and emphasizes the need for a desktop UI.

    Sessions Become Work Folders for AI Agents

    Early in the video, the presenter shows how to create sessions by topic. Work with different contexts, such as content, development, and personal projects, is separated into individual sessions. This is not just tidying up chat rooms. It is closer to dividing the units of work assigned to an AI agent.

    AI agents become more useful as context grows longer. But when contexts are mixed together, they can create confusion instead. That is why splitting sessions by topic and pinning important sessions are small-looking features worth a closer look. Just as humans need project folders, agents need context folders.

    A screen for separating sessions by topic and managing context
    A screen for dividing sessions by topic. In AI-agent use, context separation affects both productivity and accuracy.

    Artifacts Turn Chat Logs Into Work Assets

    One especially interesting part of the video is artifacts. Links, files, images, and outputs created by the agent can be found again in one place. The presenter explains that this can be used like a bookmark collection or a repository for work materials.

    This feature shows the direction of the AI-agent experience. Chatbots leave conversations behind. Agents need to leave deliverables behind. Those deliverables should be easy to find later, continue using, and reuse in other sessions.

    A screen for managing artifacts and links in one place
    The artifact screen. Links, files, images, and generated outputs accumulate as work assets instead of being scattered.

    Skills and Toolsets Are Panels for Managing an Agent’s Capabilities

    One important feature of Hermes Agent is skills. Repeated work or procedures learned in a specific environment can be saved as skills and reused in later tasks. In the video, the presenter also shows a scene where he checks a custom skill generated while making a Godot game.

    Toolsets deserve attention as well. Turning groups of tools such as web search, terminal, files, image generation, and cron on or off is a way to control an agent’s permissions and abilities. The desktop UI turns these settings from commands into a management screen.

    Cron Jobs Turn AI Agents From Manual Assistants Into Automated Operators

    In the middle of the video, a cron-job management screen appears. It visually shows scheduled tasks, such as having the agent build an app every night or run work at a specified time.

    Cron jobs mark the point where AI agents move from one-off answering tools to automated operating tools. One caveat is that scheduled tasks are trustworthy only when failures, execution logs, and permission scopes are visible together. A desktop app can make this review process easier.

    A screen for visually checking and scheduling cron jobs
    The cron-job management screen. Scheduled tasks are a core feature that turns AI agents into tools for recurring-work automation.

    Multiple Profiles Are a Way to Create Role-Based AI Employees

    Later in the video, the presenter says he runs several Hermes Agents across different devices and roles. Some agents live on specific machines, while others take on different responsibilities. The desktop app makes these agent profiles easier to manage.

    This structure has important implications for the future. Instead of one general-purpose chatbot, we may increasingly operate multiple AI agents with different roles and permissions. A content agent, development agent, research agent, and monitoring agent may each have different skills and tools.

    The Real-World Example Shows an Output-Centered Experience

    In the final example, the presenter asks the agent to generate a script and thumbnail for the video. The desktop app shows which skills and tools are being used, and the outputs are visible in artifacts.

    This scene compresses the core of an AI-agent UI. Users do not need to memorize commands. They can see which tools the agent is using. Outputs remain as files or images. AI agents enter real work flows only when these three pieces come together.

    A real usage example generating a script and thumbnail
    An example of generating a video script and thumbnail. The agent’s tool-use process and outputs are shown together.

    The Question Raised by the Hermes Agent Desktop App

    The point to watch in this video is not that “Hermes won.” The more important question is where the primary interface for AI agents will be. The CLI is powerful but not mainstream. Messengers are convenient but weak for complex configuration and verification. A desktop app sits between them, offering both work management and accessibility.

    There are also cautions. AI agents can access files, browsers, terminals, and external APIs. That means the easier the UI becomes, the more important permission management and log review become. A good desktop app is not one with many buttons. It is an app that helps users understand what they allowed and what was executed.

    Related Reading

    Conclusion: The Battleground for AI Agents Is the User Experience After the Model

    The Hermes Agent desktop app clearly shows the next challenge for AI agents. The question is no longer only “what can an agent do?” It is how users can understand, manage, and repeatedly use those capabilities.

    Sessions separate context. Artifacts store outputs. Skills accumulate experience. Cron jobs automate recurring work. Profiles create role-based agents. When these elements are connected inside a desktop UI, AI agents move from developer experiments toward something closer to a real operating system for work.

    FAQ

    What does the Hermes Agent desktop app make easier?

    It lets users visually check and control sessions, artifacts, skills, toolsets, cron jobs, and profiles. Even without knowing CLI commands, users can more easily understand the operating structure of an agent.

    Is a desktop app always better than the CLI?

    Not always. Developers and advanced automation users may be faster with the CLI. The point is that, for beginners and non-developers, a desktop UI lowers the barrier to entry.

    Why is the artifact feature important?

    It makes links, images, files, and outputs created by the AI agent easy to find and reuse. This turns simple chat history into real work assets.

    What kinds of work can cron jobs handle?

    They can be used for scheduled work such as regular reports, site monitoring, data collection, blog-performance checks, and repetitive development tasks. The caveat is that failure logs and permission scopes must be checked carefully.

    What should users watch out for when using an AI-agent desktop app?

    Do not open excessive access to files, terminals, browsers, or external APIs. Check which tools are enabled, what work has run, and what approval flow is in place.

    References

    Original Korean article: Hermes Agent Desktop App: The Next Interface for Mainstream AI Agents

    Image source: Captured images used in this article are stills from the original YouTube video. They are used for review, commentary, and educational explanation, and copyright remains with the original rights holders and the channel.

  • How to Train AI Agents: Building an AI-Native Organization with Hermes Agent

    How to Train AI Agents: Building an AI-Native Organization with Hermes Agent

    Organizations that use AI agents well do not stop at choosing a good model. The more important question is: what should the agent learn, where should it remember that knowledge, and what standards should it follow while working?

    A video from Hyoyul Kim’s AI Development Team shows this question through an example of operating Hermes Agent. It creates multiple agents divided into roles such as development, design, content, and lecture assistance, gives remote instructions through Telegram, and shares context through an Obsidian Wiki.

    How to train AI agents: an opening scene where Hermes Agent is run remotely through Telegram
    An opening scene where Hermes Agent is run remotely through Telegram.

    The First Thing to Watch Is Operations, Not Installation

    The video’s title emphasizes how to “train” AI agents. The actual content is also closer to operations architecture than to installation commands. The central flow is connecting Hermes Agent to Telegram and combining it with tools such as Codex or Claude Code while dividing several agents by role.

    According to the official Hermes Agent description, Hermes is an open-source AI agent framework that runs in terminals, messaging platforms, and IDEs. It also supports skills, memory, profiles, gateways, cron, MCP, and connections to multiple model providers. The video can be read as an example of weaving these functions into a personal work system.

    The important point is not simply to “create many AI employees.” Each agent needs a role, knowledge to reference, a learning loop to repeat, and a reporting method. Otherwise, the number of chat windows increases while actual productivity does not.

    Why AI Agents Should Be Divided Like Employees

    The video introduces agents with roles such as development, UI design, testing, content, and lecture assistance. This resembles role division in a human organization. If one agent handles everything, contexts mix, instructions become longer, and results are harder to verify.

    How to train AI agents: a command center screen for managing role-based AI agents
    A command center screen for managing role-based AI agents.

    Dividing roles creates three advantages.

    1. Instructions become shorter. A development agent can focus on code and tests, while a design agent can focus on layouts and references.
    2. Standards become clearer. Each agent’s rule file or skill document can separate what it should and should not do.
    3. Verification becomes easier. The creator and reviewer can be separated by dividing a generation agent from a review agent.

    This approach also connects to the article on building an Agent OS that unifies AI tools. The essence of using AI is not individual chatbot use, but the design of work flows and knowledge flows.

    Real Deliverables Require a Supervisor Role

    One interesting part of the video is the example that “five agents built a website.” It describes several role-based agents collaborating to build a site that collects and displays short-form videos.

    How to train AI agents: a scene showing a real deliverable made by several agents
    A scene showing a real deliverable made by several agents.

    There is one caveat in this scene that should not be missed. The speaker in the video also says he did not simply take his hands off the work. The human provided the plan, supervised the direction, and checked the results.

    That is why the realistic structure for adopting AI agents is closer to this.

    • Human: owns goals, priorities, standards, and final judgment.
    • Agent: handles research, drafts, coding, repeated revisions, and organization.
    • System: handles memory, files, versions, schedules, notifications, and verification loops.

    Without this balance, AI agents can quickly produce many outputs, but it becomes difficult to know whether those outputs match the organization’s standards. As discussed in the article on harness engineering, the technology for “harnessing agents so they work well” is becoming increasingly important.

    The First Point in a Learning Loop Is Not Simply Increasing Memory

    The video’s most important message is context sharing through an Obsidian Wiki. Even if agents are made to research and learn every night, pushing everything into agent memory can actually degrade performance.

    How to train AI agents: a scene explaining context sharing through an Obsidian Wiki
    A scene explaining context sharing through an Obsidian Wiki.

    A better approach is to separate long-term memory from working memory. The agent should not always carry everything. Instead, it should retrieve relevant information from the wiki when needed.

    In practice, the following structure is safer.

    | Component | Role | Caution | |—|—|—| | Rule documents | Behavioral standards for the agent | If they are too long, execution criteria become blurry | | Wiki or notes | Long-term knowledge store | Sources and dates should be recorded | | Cron jobs | Repeated learning and storage automation | Accumulating results without verification is risky | | Review agent | Checks errors and omissions | Final responsibility should remain with humans | | Work logs | Tracks what was done | Manage them so secrets are not mixed in |

    This perspective connects to the theme of second brains and LLM Wikis. In the AI era, a knowledge system becomes both notes for humans and operating infrastructure that agents can search and reference.

    Telegram Remote Execution Is an Operations Channel, Not Just “Assign Work Anytime”

    The video explains that Hermes Agent is connected to Telegram. Slack could also be used, but the presenter chose the lighter Telegram setup as a one-person business.

    This is more than a convenience feature. A messaging platform becomes the intake window for AI-agent work. Users can assign work while on the move, receive completion notifications, and get files or outputs back.

    One caveat is that remote execution is powerful, so it needs operating principles.

    • Place approval procedures around dangerous commands.
    • Separate permissions and work scopes by agent.
    • Exclude sensitive files and credentials from task instructions.
    • Keep logs and result reviews for automated work.
    • Create checkpoints that allow rollback after failure.

    Hermes Agent’s gateways, profiles, and cron features are useful when building this operating system. But having the tools does not automatically make automation safe.

    AI-Native Organizations Need Operating Rules Before Dashboards

    Near the end of the video, a concept for an AI-native organization dashboard appears. It brings together work status, schedules, messengers, agent status, scheduled tasks, skills and plugins, and token usage in one view.

    How to train AI agents: a scene explaining an AI-native organization operations dashboard
    A scene explaining an AI-native organization operations dashboard.

    This concept is very practical. The caveat is that something must be decided before the dashboard: what to automate, how to judge success, and where humans should intervene.

    For teams beginning AI-agent operations, the following order is better.

    1. Choose three recurring tasks.
    2. Document each task’s inputs, outputs, and verification criteria.
    3. Assign only one role to each agent.
    4. Have humans review the outputs and improve the rules.
    5. After stabilization, automate through cron jobs or messaging channels.

    Rather than creating “ten AI employees” from the beginning, it is faster to make one agent consistently good at one task.

    Pre-Adoption Checklist

    Before adopting Hermes Agent or a similar AI-agent system, check the following questions first.

    • Is the recurring work assigned to this agent clear?
    • Is there a human or review agent to inspect the outputs?
    • Is there a wiki or document repository for long-term knowledge?
    • Have you decided how far secrets and permissions will be allowed?
    • Are there logs and backups that allow rollback after failure?
    • Can you track cost, token usage, and execution time?

    If these questions cannot be answered, increasing the number of agents is more likely to create confusion than automation.

    Related Reading

    Conclusion: AI-Agent Training Starts With Operations Design, Not Learning Alone

    The core question in the video is not “how many AI agents can we create?” It is how agents learn the organization’s knowledge and standards, how they collaborate, and how they are verified.

    Hermes Agent provides a useful operational foundation for this experiment. It can run through messaging platforms, separate profiles, build skills and memory, and run repeated tasks through cron jobs.

    But final results depend more on design than on the tool itself. Roles must be kept small, a knowledge repository must be built, verification loops must be attached, and human decision points must remain. Only then do AI agents become less like automated responders and more like an operating system for working together.

    FAQ

    Can Hermes Agent be used like an AI employee immediately after installation?

    No. Installation is only the start. Roles, rules, reference knowledge, and verification criteria must be defined before it can be used for real work.

    Does training an AI agent mean fine-tuning a model?

    In this article, training is closer to operational learning than fine-tuning. It means helping the agent better reference the context of repeated work through rule documents, skills, wikis, and work logs.

    Is Obsidian Wiki required?

    It does not have to be Obsidian. The important point is to have a long-term knowledge repository that agents can search and reference. Notion, a Markdown wiki, a Git repository, or an LLM Wiki can also work.

    Is a Telegram connection safe?

    The connection itself is less important than permission design. Dangerous-command approval, sensitive-information separation, log review, and permission limits must be designed together.

    How many agents should a team start with?

    One or two is appropriate at first. Start with one recurring task and one verification task, then add only roles that have stabilized.

    References

    Original Korean article: How to Train AI Agents: Building an AI-Native Organization with Hermes Agent

    Image source: Captured images used in this article are stills from the original YouTube video. They are used for review, commentary, and educational explanation, and copyright remains with the original rights holders and the channel.

  • How to Build an AI Agent Operating System: A 7-Layer Blueprint

    How to Build an AI Agent Operating System: A 7-Layer Blueprint

    Most people start using AI by opening one tool at a time. They ask ChatGPT for a draft, use Claude for a long document, try a coding assistant for development, and keep separate notes somewhere else. That works for experiments, but it breaks down when AI becomes part of daily work.

    An AI agent operating system is a way to connect those scattered tools into one repeatable workflow. It does not mean a literal computer operating system. It means a practical work architecture: memory, models, agents, dashboards, production tools, and feedback loops working together.

    What Is an AI Agent Operating System?

    An AI agent operating system is the layer that helps AI tools remember context, choose the right model, run tasks through agents, and send results back into a knowledge base. The goal is not to collect more apps. The goal is to turn AI into a system that can produce, verify, and improve work over time.

    The easiest way to understand it is to compare two workflows. In the first workflow, every AI conversation starts from zero. In the second, the AI can read your notes, follow your preferred process, use tools, create deliverables, and leave behind reusable context. The second workflow is closer to an agent operating system.

    Why Individual AI Tools Are Not Enough

    Individual AI tools are powerful, but they are usually isolated. A chatbot may write well but cannot see your whole knowledge system. A coding agent may edit files but may not know your business context. A note-taking app may store information but does not automatically turn that information into action.

    This is why many AI workflows feel impressive at first and messy later. The user becomes the connector. They copy and paste context, check results, move files, remember previous decisions, and restart the same explanation again and again. An AI agent operating system reduces that friction.

    The 7 Layers of an AI Agent Operating System

    1. Foundation: Hardware and Basic Environment

    The first layer is the environment where the system runs. This may be a laptop, a workstation, a cloud server, or a hybrid setup. The important question is not only speed. It is whether the environment can run the tools you need reliably: browsers, terminals, local files, APIs, schedulers, and AI clients.

    2. Memory: Long-Term Context Storage

    Memory is where your system keeps reusable context. This can include Markdown notes, project documents, meeting summaries, prompt patterns, decision logs, source material, and structured databases. Without memory, every AI interaction becomes a one-time conversation. With memory, agents can work from accumulated knowledge.

    3. Brain: Model Routing

    No single model is best for every task. Some models are better at writing, some at coding, some at long-context reasoning, and some at fast routine work. The brain layer routes work to the right model. A good AI operating system should make it easy to choose between cloud models, local LLMs, and specialized tools.

    4. Agents: The Actual Workers

    Agents are not just chatbots with names. They are task-oriented workers with access to tools, files, instructions, and verification steps. One agent may inspect a codebase. Another may summarize sources. Another may prepare a WordPress draft. The agent layer turns AI from conversation into execution.

    5. Command Center: A Unified Dashboard

    As workflows grow, users need a command center. This may be a desktop app, a web UI, a terminal dashboard, a Kanban board, or a messaging interface. The command center shows what is running, what was produced, what needs review, and what should happen next.

    6. Production Services: Where Real Output Lives

    AI becomes valuable when outputs leave the chat window. Production services include GitHub repositories, WordPress sites, shared drives, documents, spreadsheets, email systems, CRMs, and internal dashboards. The operating system should connect agents to these services safely, with clear approval gates.

    7. Loop: Feeding Results Back Into Memory

    The final layer is the feedback loop. After an agent completes a task, the result should not disappear. Useful decisions, reusable workflows, errors, and quality checks should return to memory. This is how the system gets better. Without a loop, automation produces output. With a loop, it produces learning.

    How to Start Building One

    1. Choose one recurring workflow, such as publishing a blog post or preparing a report.
    2. Create a simple memory folder for source material, decisions, and reusable instructions.
    3. Define which AI tools or models handle writing, coding, research, and review.
    4. Use agents only where tool access and verification matter.
    5. Create a dashboard or checklist so humans can review progress.
    6. Connect output destinations only after the local draft process is reliable.
    7. Record what worked and feed it back into the next run.

    What to Avoid

    The biggest mistake is trying to automate everything before the workflow is clear. An AI agent operating system should not be a pile of tools. It should be a map of how work moves from context to action to verification. Start small, then add layers only when they solve a real bottleneck.

    Related Reading

    FAQ

    Is an AI agent operating system the same as an AI agent platform?

    Not exactly. A platform is a product. An AI agent operating system is a workflow architecture. You can build it with several tools, including chatbots, coding agents, local files, schedulers, and publishing systems.

    Do I need local LLMs to build one?

    No. You can start with cloud models. Local LLMs become useful when privacy, cost control, or offline experimentation matters.

    What is the first practical use case?

    Choose a workflow with clear inputs and outputs, such as research-to-draft publishing, meeting-summary generation, documentation updates, or code review.

    Original Korean article: How to Build an Agent OS That Connects AI Tools