Techlist.io - Korean Tech Blog Curator

figma2 min readCurated summary

Figma Achieves C5 Accreditation | Figma Blog

Figma has achieved C5 accreditation, Germany’s cloud security standard developed by the Federal Office for Information Security (BSI). The milestone strengthens Figma’s credibility with customers in Germany, Austria, and Switzerland by independently validating its security, availability, confidentiality, risk management, and operational transparency. It also supports organizations with strict regulatory and compliance requirements. ## C5 Accreditation and Cloud Security - C5 provides a recognized framework for evaluating cloud service security and reliability. - Independent accreditation confirms that Figma meets rigorous requirements for: - Information security - Risk management - Service availability - Confidentiality - Operational transparency - Figma is now listed in the BSI C5 register, allowing customers to review its security controls and operational practices more easily. ## Benefits for DACH Organizations - The accreditation gives organizations greater confidence when using Figma for cloud-based collaboration. - It is particularly relevant to customers in: - Government and the public sector - Financial services - Other highly regulated industries - Customers can more easily assess Figma against internal compliance, security, and assurance requirements. ## Continued Investment in the Region - Figma’s regional initiatives include: - Full German-language localization - European Union data storage options for enterprise customers - Expanded enterprise security and compliance capabilities - Nearly 90% of DAX 40 companies use Figma to design and build products collaboratively. Figma’s C5 accreditation reinforces its position as an enterprise-ready collaboration platform for organizations across the DACH region, especially those facing complex regulatory and security demands.

Read original(opens in new tab)
woowahan5 min readCurated summary

The First Action That Determines the Success or

Woowa Brothers argues that incident impact depends not only on how quickly an outage is detected, but also on how quickly an effective First Action is executed. Analysis of more than 70 incidents showed that incidents beginning with a hotfix tended to last nearly twice as long as those beginning with a rollback. The company therefore established a standardized incident lifecycle and metrics system to make early response measurable and improve it through automation and process design. ## Why First Action Matters - Detection was generally fast in Woowa Brothers’ 2025 incidents, but customer impact often continued for a long time. - Rollbacks can immediately undo a problematic change, while hotfixes require diagnosis, coding, and redeployment. - During hotfix preparation, the service may remain impaired and customer impact continues to accumulate. - Predefined mechanical mitigations—such as rollback or scaling—are particularly effective because they can be executed without lengthy additional decisions. - First Action is defined by both: - **What** action was taken - **When** it was executed after the incident was recognized ## Standardizing Incident Response - Comparing First Actions across incidents was difficult because teams used different starting points: - The moment customer impact was recognized - The moment an incident was announced company-wide - Other team-specific interpretations - Woowa Brothers concluded that First Action could only be measured consistently if the entire incident timeline used shared definitions. - The lifecycle provides a common framework for understanding where an incident is, what action should happen next, and how long each stage takes. ## The Seven-Stage Incident Lifecycle ### Potential-Incident Lifecycle #### 1. Anomaly - A service or system shows abnormal behavior and the responsible team detects and acknowledges it. - Acknowledgment must leave objective evidence, such as: - An on-call alert acknowledgment - A customer-service response comment - An alert comment - If there is no customer impact, the process may end after internal handling. - If any part of the ordering process becomes unavailable, the event transitions into the Incident Lifecycle. ### Incident Lifecycle #### 2. Open - The service owner recognizes the event as an incident. - An incident-response channel is created and relevant technical and business organizations are invited to coordinate. #### 3. Investigating - Teams assess customer impact and investigate likely causes. - They first examine recent deployments, configuration changes, and failures in external dependencies. #### 4. Identified - Teams execute actions to reduce customer impact. - Rollbacks and scaling adjustments are prioritized as First Actions. - Multiple mitigation options may be evaluated and applied in parallel rather than waiting for a single definitive root cause. #### 5. Monitoring - Teams verify whether the applied actions are actually reducing customer impact. - If not, the process returns to investigation and mitigation for another response attempt. #### 6. Resolved - Customer impact has been eliminated and the incident is considered resolved. - Findings and actions are communicated across the organization according to an established process. #### 7. Closure Time - The team documents the root-cause analysis and tracks preventive follow-up work. - Woowa Brothers separates incident reporting from execution of corrective actions to ensure resolution leads to real operational improvement. ## Metrics for Measuring Response Performance The lifecycle is useful because it connects incident stages to time-based metrics. These metrics are intended to reveal bottlenecks and guide improvement, not serve as goals in themselves. ### MTTD: Mean Time to Detect - Measures the average time from incident occurrence until detection and acknowledgment. - Woowa Brothers includes acknowledgment evidence—similar to MTTA—because an alert alone does not prove that response has begun. - A high MTTD may indicate: - Inadequate monitoring coverage or thresholds - Excessive alert noise - Missing acknowledgment records ### MTTR: Mean Time to Repair - Measures the average time from incident acknowledgment until service recovery. - A high MTTR can indicate: - Poor First Action readiness - Insufficient service visibility - Complex recovery procedures - Slow decisions or communication bottlenecks - It points to structural improvements such as automation, standardized procedures, and clearer decision-making authority. ### MTTA: Mean Time to Action - Measures how quickly mitigation is initiated. - Rather than judging whether a response was “good,” it evaluates whether standardized response mechanisms activate promptly. - Woowa Brothers divides it into two more specific metrics. #### MTTFA: Mean Time to First Action - Measures the time until the first predefined mechanical mitigation, such as a rollback or scaling adjustment. - A high MTTFA may result from: - Complicated rollback paths - Manual scaling operations - Excessive decisions or preparation required before execution - The recommended solution is to automate and simplify First Action procedures. #### MTTEA: Mean Time to Effective Action - Measures the time from incident occurrence until abnormal metrics begin improving after an effective mitigation is applied. - It captures whether an action actually worked, not merely whether it was executed. - The relationship between MTTFA and MTTEA provides useful signals: - **MTTEA ≈ MTTFA:** the initial action was fast and immediately effective. - **MTTEA > MTTFA:** the First Action was insufficient and additional response was needed. - **MTTEA without MTTFA:** no mechanical initial action was possible, or responders relied directly on a hotfix or similar intervention. - **Increasing MTTEA:** standard scenarios or automation require improvement. The practical recommendation is to treat incident response as an organizational system rather than an individual skill. Define a shared lifecycle, prioritize fast and reversible mitigations such as rollback, automate their execution, and use metrics like MTTFA and MTTEA to continuously remove response bottlenecks.

Read original(opens in new tab)
gitlabOriginal article

What’s new in Git 2.53.0? (opens in new tab)

Git 2.53.0 introduces significant performance and maintenance improvements, specifically targeting large repositories and complex history rewriting workflows. Key updates include compatibility between geometric repacking and partial clones, as well as more granular control over commit signatures during imports. These enhancements collectively move Git toward more efficient repository management and better data integrity for modern development environments. ## Geometric Repacking Support with Promisor Remotes * Git utilizes repacking to consolidate loose objects into packfiles, with the "geometric" strategy maintaining a size-based progression to minimize the computational overhead found in "all-into-one" repacks. * Previously, geometric repacking was incompatible with partial clones because it could not correctly identify or manage "promisor" packfiles, which contain the metadata for objects expected to be backfilled from a remote. * The 2.53.0 release enables geometric repacking to process promisor packfiles separately, preserving the promisor marker and preventing the tool from crashing when used within a partial clone repository. * This fix removes a major blocker for making the geometric strategy the default repacking method for all Git repositories. ## Preserving Valid Signatures in git-fast-import(1) * The `git-fast-import` tool, a backend for high-volume data ingestion and history rewriting, previously lacked the nuance to handle commit signatures during partial repository edits. * A new `strip-if-invalid` mode has been added to the `--signed-commits` option to solve the "all-or-nothing" problem where users had to choose between keeping broken signatures or stripping valid ones. * This feature allows Git to automatically detect which signatures remain valid after a rewrite and only strip those that no longer match their modified commits. * This provides a foundation for tools like `git-filter-repo` to preserve the chain of trust for unchanged commits during migration or cleaning operations. ## Expanded Data in git-repo-structure * The `structure` subcommand of `git-repo`, intended as a native alternative to the `git-sizer` utility, now provides deeper insights into repository scaling. * The command now reports the total inflated size and actual disk size of all reachable objects, categorized by type: commits, trees, blobs, and tags. * These metrics are essential for administrators managing massive repositories, as they help identify which object types are driving disk consumption and impacting performance. These updates reflect Git’s continued focus on scalability and developer experience, particularly for organizations managing massive codebases. Users of partial clones and repository migration tools should consider upgrading to 2.53.0 to leverage the improved repacking logic and more sophisticated signature handling.

pinterest4 min readCurated summary

Beyond Two Towers: Re-architecting the Serving Stack for Next-Gen Ads Lightweight Ranking Models…

Two-Tower models make retrieval and lightweight ranking highly efficient by scoring user and item embeddings with a dot product, but they cannot represent rich user-item interactions or deep feature crossings. This post describes an ads-serving redesign that introduces general-purpose GPU models while preserving end-to-end latency. The main strategy is to reduce data movement, move filtering logic onto the GPU, and optimize inference from an initial 4-second p90 latency to about 20 milliseconds. ## Why Move Beyond Two-Tower Models - Two-Tower architectures independently encode users and items, enabling fast scoring across millions of candidates. - Their decoupled structure limits: - User-item interaction features - Target attention - Early feature crossing - Deep architectures requiring simultaneous access to user and candidate data - More expressive models require GPU-based general-purpose inference rather than specialized dot-product or ANN retrieval. - The existing retrieval stack was not designed to transfer large candidate and feature sets to a GPU, creating a major latency challenge. ## Restructuring the Serving Funnel The traditional funnel consisted of: - Feature expansion for thousands of candidates - Retrieval and Two-Tower lightweight ranking - Heavy ranking and auction processing for the top documents Adding GPU inference directly to this flow would require fetching, serializing, transferring, and returning features for tens of thousands of documents. The authors therefore redesigned the entire early-stage serving pipeline instead of optimizing the model alone. ## Segmenting the Inventory for Feature Fetching Feature retrieval was a major latency source, often taking longer than model inference for workloads ranging from 10,000 to 100,000 documents. - **High-value inventory:** Roughly 1 million documents responsible for a substantial share of revenue have their features embedded in the PyTorch model as registered buffers. - Features become part of the model state, similar to weights. - They remain in GPU high-bandwidth memory. - Requests avoid remote feature-service calls and host-to-device transfers. - The model file must be periodically updated to refresh features. - Future work may include GPU-based caching. - **Long-tail inventory:** The remaining roughly 1 billion documents use a high-performance key-value store with in-host caching. - The post focuses on the first strategy, which is already running in production. ## Moving Business Logic onto the GPU Previously, the model returned scores for approximately 100,000 candidates, while CPU-side code handled utility calculation, filtering, diversity, deduplication, and top-k selection. - The new PyTorch model performs these operations directly: - Combines pCTR, pCVR, bid, and other signals into utility scores. - Applies diversity and filtering rules. - Performs top-k selection. - The GPU returns only the final winners—typically around 1,000 documents—instead of all candidate scores. - This reduces device-to-host data transfer and takes advantage of GPU parallelism. - The approach works because lightweight-ranking business rules are sufficiently simple to express with tensor operations. ## Reducing GPU Inference Latency Initial GPU inference measured roughly 4,000 ms at p90, far too slow for real-time serving. Several systems optimizations reduced this to approximately 20 ms: - **Multiple CUDA streams:** Separate streams for workers allow host-to-device transfers, computation, and device-to-host transfers to overlap. - **Worker alignment:** Worker threads are matched and pinned to physical CPU cores to reduce context switching and lock contention. - **Kernel fusion:** Triton kernels combine operations such as linear layers and activations, reducing memory traffic. - **BF16 computation:** Brain Floating Point 16 lowers memory usage and accelerates arithmetic compared with FP32. - **Profiling tools:** PyTorch Profiler and NVIDIA Nsight Systems were used to identify bottlenecks. ## Practical Recommendation Deploying more expressive ranking models requires rethinking the serving architecture around data movement and execution placement. Embedding frequently used features, executing business logic on the GPU, and applying low-level CUDA and kernel optimizations can make complex neural ranking feasible without increasing end-to-end latency.

Read original(opens in new tab)
discord2 min readCurated summary

How to Customize Your Discord Profile

Discord profiles are designed to help users express their identity through avatars, server affiliations, gaming interests, statuses, and visual effects. The post explains where to edit these settings on desktop and mobile, then outlines customization options ranging from profile widgets to Shop items and Nitro features. Overall, it encourages users to tailor their profile to make a memorable first impression. ## Editing Your Discord Profile - On desktop, open **User Settings** using the gear icon, then select **Edit Profiles**. - On mobile, open the **You** tab and tap **Edit Profile**. - Click or tap your profile icon to preview how others see your profile. ## Choosing an Avatar - Use **Change Avatar** in the profile editor to upload an image from your device. - Nitro members can use animated avatars. - Canceling an avatar upload before confirming prevents the upload from counting toward Discord’s rapid-upload throttle. - Users can also display a **Server Tag** next to their name and on their profile. - Server Tags are available when a server has enough boosts and its administrators enable the feature. ## Showing Off Your Games Desktop users can add Profile Widgets that highlight their gaming interests, including: - Favorite Game - Games in Rotation - Games I Like - Want to Play These widgets let users showcase current games, backlogs, and recommendations. ## Sharing Activities and Statuses - Users can add a short custom status message from their profile icon. - Statuses can be set to expire after a chosen period or remain indefinitely. - Connected accounts can automatically display activities such as: - Games played on PlayStation or Xbox - Music listened to on Spotify - Anime watched through Crunchyroll ## Customizing Profiles Through the Shop The Discord Shop provides cosmetic additions that affect profiles and other parts of the app: - **Avatar Decorations:** Frames and animated effects around avatars, visible in profiles and text chats. - **Profile Effects:** Large animations displayed when someone opens a profile. - **Nameplates:** Decorative designs shown behind display names in server member lists and direct messages. ## Nitro Profile Features Nitro members receive additional customization options, including access to more advanced profile features and the ability to maintain multiple profiles.

Read original(opens in new tab)
cloudflare3 min readCurated summary

Google’s AI advantage: why crawler separation is the only path to a fair Internet

Google’s dominance in search gives it a structural advantage in generative AI: publishers must allow Googlebot to preserve search visibility, while Google can also reuse that access for AI products. The authors argue that this blurs search indexing and AI data collection, deprives publishers of traffic and compensation, and disadvantages competing AI companies. They support the CMA’s proposed UK conduct rules but say the only fair solution is to separate crawling for search from crawling for generative and agentic AI. ## CMA’s Strategic Market Status designation - The UK’s Digital Markets, Competition and Consumers Act 2024 allows the CMA to designate firms with substantial, entrenched market power as having Strategic Market Status. - In October 2025, Google received this designation for general search and search advertising, where it holds roughly 90% of the UK market. - The designation covers AI Overviews and AI Mode, allowing the CMA to impose legally enforceable conduct requirements on Google’s search ecosystem. - The authors view the CMA’s consultation as an important first step toward clearer rules for AI crawling and publisher control. ## Problems with Google’s dual-purpose crawler - Publishers cannot realistically block Googlebot because doing so could reduce their visibility in Google Search and damage advertising revenue. - Google uses the same search access not only for indexing and referrals, but also to ground AI Overviews, AI Mode, and broader generative AI services. - These AI features may reproduce publisher content while sending little or no traffic back to the original sites. - This threatens ad-supported publishing models and can put Google in direct competition with the publishers whose content it uses. - Unlike other AI companies, Google can obtain large amounts of content without negotiating payment, because publishers are effectively unable to refuse its search crawler. ## Google’s crawling advantage Cloudflare’s data indicates that Googlebot accesses substantially more unique pages than other major AI crawlers: - About 1.7 times more than ClaudeBot and GPTBot. - About 3 times more than Meta-ExternalAgent. - About 3.3 times more than Bingbot. - About 5.1 times more than Amazonbot. - Nearly 15 times more than Applebot. - Nearly 167 times more than PerplexityBot. - More than 700 times more than CCBot. - More than 1,800 times more than archive.org_bot. - Googlebot crawled roughly 8% of the sampled unique URLs during the two-month observation period. ## Limits of robots.txt and the need for separate controls - Publishers are much less likely to block Googlebot in `robots.txt` because of its importance for search referrals. - `robots.txt` expresses preferences but does not technically enforce crawler behavior; publishers must rely on bots to comply. - Web Application Firewalls can technically block unwanted crawlers, but this does not solve the core problem when search and AI access are tied to the same Googlebot identity. - The authors therefore argue that publishers need a meaningful, independent way to permit Google Search indexing while refusing the use of their content for generative AI. The proposed CMA rules should go further by requiring effective separation between search crawling and AI crawling. Publishers should be able to opt out of generative AI use without sacrificing search visibility, creating fairer conditions for content creators and competing AI developers.

Read original(opens in new tab)
cloudflare3 min readCurated summary

Building vertical microfrontends on Cloudflare’s platform

Cloudflare’s new Vertical Microfrontends (VMFE) Worker template lets independent teams map separate Workers to different URL paths on one domain. Unlike horizontal microfrontends, each team owns an entire vertical slice—including its framework, frontend, deployment pipeline, and operations. The approach enables technology flexibility and team autonomy while using view transitions and preloading to preserve a seamless user experience. ## Vertical Microfrontend Architecture - Applications are divided by URL path rather than by components on a single page: - `/` → Marketing - `/docs` → Documentation - `/blog` → Blog - `/dash` → Dashboard - Routes can be split into more granular verticals, such as: - `/dash/product-a` → Worker A - `/dash/product-b` → Worker B - Each route can be an entirely separate frontend project with its own: - Framework and libraries - Codebase - CI/CD pipeline - Owning team - This allows teams to choose technologies suited to their needs—for example, Astro for marketing and React for a dashboard. - It also reduces the risk of monolithic releases, where one team’s regression can force multiple teams to roll back. - Cloudflare applies a similar model internally, routing users from its core dashboard to separate products such as Zero Trust based on URL paths. ## Creating a Unified Experience - Independent applications must still appear cohesive to users. - Users generally accept distinct experiences between marketing, documentation, and dashboards. - However, related areas within one product—such as `/dash/product-a` and `/dash/product-b`—should not expose their separate repositories or Workers. - The goal is to hide implementation boundaries while preserving independent ownership. ## CSS View Transitions - Navigating between separately deployed Workers can otherwise produce a brief blank screen while the next document loads. - CSS View Transitions can preserve shared elements, such as navigation, during page changes. - The transition API allows teams to: - Keep DOM elements visible across navigations - Animate differences between the old and new pages - Make multi-page applications feel more like a single-page application - A small CSS rule can assign a transition name to the navigation and apply an eased animation to the page transition. ## Document Preloading - Seamless animation is not enough; navigation should also feel immediate. - The Speculation Rules API lets compatible browsers prefetch likely future document navigations. - Teams can define a `script` with `type="speculationrules"` and list URLs for related vertical slices, such as links in shared navigation. - Chrome, Edge, and Opera support the newer API, while Firefox and Safari currently do not. Cloudflare’s VMFE approach is most useful when teams need independent ownership and technology choices without sacrificing a unified product experience. Path-based Worker routing, shared visual conventions, view transitions, and selective prefetching provide the foundation for making separate applications behave like one.

Read original(opens in new tab)
tossOriginal article

6 Principles to Increase Marketing (opens in new tab)

Toss, a leader in the Korean fintech space, demonstrates that high marketing performance can be achieved without resorting to aggressive or deceptive copy. By analyzing hundreds of A/B tests within their app, they have identified specific UX writing patterns that prioritize user trust while significantly boosting engagement. The core conclusion is that clarity, psychological ease, and guaranteed rewards consistently outperform complex value propositions and exaggerated claims. ### The Power of One Core Message * Focusing on a single, immediate action is more effective than listing multiple service benefits. * In one test, replacing a complex benefit-driven headline with a simple "Take a 10-question test" resulted in a 10x increase in click-through rates (CTR). * Complexity creates friction; users are more likely to engage when they understand exactly what the next step entails without distractions. ### Prioritizing Guaranteed Rewards * Users show a stronger preference for "guaranteed small wins" over "potential big wins." * A campaign promising a "Minimum 100 won" reward saw 20x more exposure than one promising "Up to 1 million won," as large numbers can trigger skepticism or feel unattainable. * Phrases like "You will definitely get 1" outperform "Get as many as you want" because they provide a concrete promise rather than a vague possibility. ### Reducing Cognitive Load Through "Light" Language * The choice of verbs significantly impacts the perceived effort of a task. * Using "Prepare for travel insurance" instead of "Sign up for travel insurance" reduces the psychological burden, as "sign up" implies a long, bureaucratic process. * "Light" verbs make the service feel faster and easier to complete, encouraging immediate action. ### Strategic Information Framing * Clearly defining the nature of information—whether it is a "collection," a "list," or "new"—helps users categorize the value quickly. * Highlighting that a feature is "new" rather than explaining the specific benefits of the feature increased CTR by 6x. * Using terms like "View collection" for loan products provides a sense of organized efficiency that appeals to users looking for consolidated information. ### Specificity in Action and Conditions * Ambiguity leads to hesitation; providing exact numbers (e.g., "4 missions" or "8 blanks") increases conversion rates. * Specifying the number of tasks makes a goal feel attainable and removes the fear of an open-ended time commitment. * Quantifying the effort required (e.g., "takes 3 minutes") allows users to make an instant, friction-less decision to participate. ### Utilizing Intuitive, Everyday Experiences * Copy that mirrors real-life physical actions is more intuitive for users. * Changing a button from "View answer" to "Pick an answer" (accompanied by a stamp emoji) for an OX quiz significantly increased engagement by making the digital action feel more tactile and familiar. * Leveraging common vocabulary ensures that users do not have to "translate" marketing speak into practical reality. To maximize conversion, designers and writers should move away from broad marketing claims and toward radical specificity. By removing ambiguity and promising certain, low-effort outcomes, you can build a more effective and honest user experience.

cloudflare2 min readCurated summary

Introducing Moltworker: a self-hosted personal AI agent, minus the minis

Moltworker adapts the self-hosted Moltbot personal AI assistant to run on Cloudflare without requiring users to buy a dedicated Mac mini. It combines a Cloudflare Worker, Sandbox SDK, Browser Rendering, R2, AI Gateway, and Cloudflare Access to provide a globally available, secured deployment. The result is a managed infrastructure layer around Moltbot’s standard Gateway runtime while preserving its integrations and persistent state. ## Running a Personal Agent on Cloudflare - Cloudflare Workers increasingly supports Node.js APIs natively, reducing the need for compatibility hacks and making it easier to run existing JavaScript and TypeScript packages. - An internal test of the 1,000 most popular NPM packages found that only 15 relevant packages failed to run in Workers. - Although much of Moltbot runs inside a container, improved Workers compatibility is useful for building agent logic closer to users. - Cloudflare’s Developer Platform provides the main infrastructure components: - **Sandboxes** for securely running untrusted code. - **Browser Rendering** for automated headless browser interactions. - **R2** for persistent object storage. - Cloudflare’s global network for scalability and security. ## Moltworker Architecture - Moltworker consists of: - An entrypoint Worker serving as an API router and proxy. - Cloudflare Access protecting the Worker and administration interface. - A Sandbox container running Moltbot’s standard Gateway and integrations. - R2 for persistent storage. - This structure separates the public API and administrative layer from the isolated environment where the agent executes. ## AI Gateway Integration - Cloudflare AI Gateway proxies requests between Moltbot and AI providers. - It provides: - Centralized request visibility. - Cost monitoring, logs, and analytics. - Provider and model switching without changing Moltbot code. - Fallback providers or models for improved reliability. - Secrets can be managed through: - **Bring Your Own Key (BYOK)**, where provider credentials are stored centrally. - **Unified Billing**, where users purchase credits and Cloudflare handles provider billing. - Integration requires creating an AI Gateway instance, enabling a provider such as Anthropic, and setting `ANTHROPIC_BASE_URL`; Moltbot itself does not need code changes. ## Sandbox-Based Execution - The Sandbox SDK runs agent code in isolated environments built on Cloudflare Containers. - It provides simplified APIs for: - Executing commands. - Managing files and directories. - Running background processes. - Exposing services. - Executing code in contexts such as Python. - The SDK abstracts container lifecycle, networking, filesystem, and process-management concerns behind TypeScript APIs. Moltworker offers a way to run a capable personal AI agent online with managed security, storage, browser automation, and model access—without maintaining dedicated hardware.

Read original(opens in new tab)
grammarlyOriginal article

How to Use AI Agents: A Simple Guide to Getting Started (opens in new tab)

AI agents represent a shift from reactive, prompt-based AI to proactive, goal-oriented systems capable of planning and executing multi-step tasks with minimal oversight. By operating in a continuous loop of gathering context, selecting tools, and evaluating results, these agents can manage complex workflows that previously required manual follow-up. The most effective implementation strategy involves starting with small, repeatable processes and gradually increasing agent autonomy as reliability is proven through feedback and testing. ### The Mechanism of Agentic AI * Unlike traditional generative AI that responds to isolated instructions, agents possess "agency," allowing them to decide the next best action to reach a defined objective. * Agents function through an iterative operational cycle: they analyze relevant context, select an action, utilize available tools, and evaluate the outcome to determine if the goal is met. * Advanced writing agents, such as those integrated into workplace tools, can proactively suggest revisions for tone, logical progression, and specificity by maintaining contextual awareness across a document's lifecycle. ### Deploying Agents via Repeatable Workflows * Initial use cases should focus on contained, well-understood tasks rather than end-to-end process overhauls to ensure the agent’s logic can be easily monitored. * In research and organization, agents can be tasked with continuously gathering and categorizing sources, updating citations as new data becomes available. * Communication workflows benefit from agents that can reference historical conversation threads to draft follow-ups, summarize long discussions, and adjust meeting agendas dynamically. * Content creation agents can manage the transition from rough notes to structured outlines, applying specific tone and clarity feedback across multiple versions of a draft. ### Integration and Tool Selection * Effective deployment often requires no coding experience, as agentic capabilities are increasingly built into existing word processors, email clients, and project management platforms. * Using familiar software ecosystems reduces the technical barrier to entry and allows for easier scaling of the agent’s behavior over time. * Project management agents can be utilized to monitor task progress, adjust timelines based on changing conditions, and surface high-priority items automatically. ### Establishing Goals and Ownership * Success depends on defining specific end states rather than vague instructions; for example, asking an agent to "flag logical gaps and suggest supporting evidence" is more effective than asking it to "improve writing." * Defining clear ownership ensures the agent knows which parameters to prioritize, such as maintaining a consistent brand voice while revising for conciseness. * Testing should begin with small-scale scenarios, like a single recurring email update, to allow for the refinement of instructions and priorities based on real-world performance. ### Scaling Autonomy and Oversight * Once an agent demonstrates consistent accuracy in a narrow task, its scope can be broadened to include related steps, such as tracking data throughout the week to prepare a draft before being prompted. * Increased autonomy does not mean a lack of control; humans should remain in the loop to provide feedback, which the agent uses to refine its future decision-making logic. * The transition from prompts to progress is achieved by allowing agents to work across different tools and contexts as they prove their ability to handle more complex judgment calls. To get the most out of AI agents, treat them as collaborative partners by starting with a narrow focus and providing specific, goal-oriented feedback. Rather than handing off entire processes immediately, focus on delegating repeatable tasks where the agent’s ability to plan and adapt can yield the highest immediate value.

grammarlyOriginal article

Agentic AI vs. generative AI: What’s the Difference and When to Use Each (opens in new tab)

While generative AI focuses on creating content like text and images through prompt-based prediction, agentic AI represents a shift toward autonomous goal achievement and execution. By combining the creative output of large language models with a continuous loop of perception and action, these technologies allow users to move from simply generating drafts to managing complex, multi-step workflows. Ultimately, the two systems are most effective when used together, with one providing the ideas and the other handling the coordination and follow-through. ### Distinguishing Creative Output from Autonomous Agency * Generative AI functions as a responder that produces new content—such as text, code, or visuals—by predicting the most likely next "token" or piece of data based on a user’s prompt. * Agentic AI possesses "agency," meaning it can take a high-level goal (e.g., "prepare a client kickoff") and determine the necessary steps to achieve it with minimal guidance. * While tools like Midjourney or GitHub Copilot focus on the immediate delivery of a specific creative asset, agentic systems act as proactive partners that can use external tools, manage schedules, and make independent decisions. ### The Underlying Mechanics of Prediction and Action * Generative models rely on Large Language Models (LLMs) trained on massive datasets to identify patterns and chain together original sequences of information. * Agentic systems operate on a "perceive, plan, act, and learn" loop, where the AI gathers context from its environment, executes tasks across different applications, and adjusts its strategy based on the results. * The generative process is typically a direct path from input to output, whereas the agentic process is iterative, allowing the system to adapt to changes and feedback in real-time. ### Practical Applications in Content and Workflow Management * Generative use cases include transforming rough bullet points into polished emails, summarizing long documents into flashcards, and adjusting the tone of a message to be more professional. * Agentic use cases involve higher-level orchestration, such as monitoring document revisions, consolidating feedback from multiple stakeholders, and automatically sending follow-up reminders. * In a project management context, an agentic system can draft a project plan, identify owners for specific tasks, and update timelines as milestones are met or missed. ### Navigating Technical and Operational Limitations * Generative AI is susceptible to "hallucinations" because it prioritizes probabilistic output over factual reasoning or logic. * Agentic AI introduces complexity regarding security and permissions, as the system needs authorized access to various apps and tools to perform actions on a user's behalf. * Current agentic systems still require human oversight for critical decision-making to ensure that autonomous actions align with the user's intent and organizational standards. To maximize efficiency, you should utilize generative AI for the creative phases of a project—such as brainstorming and drafting—while delegating administrative overhead and coordination to agentic AI. As these technologies continue to converge, the focus of AI utility is shifting from the volume of content produced to the successful execution of complex, real-world results.

kakao2 min readCurated summary

Recruiting new Kakao AI Ambassadors ‘

Kakao is recruiting 100 participants for its expanded KANANA 429 AI ambassador program. The five-month program introduces separate tracks for AI experts, creators, and university students, offering opportunities to test Kakao AI services, create content, and provide feedback. Applications close at noon on February 19, 2026. ## Program Purpose and Name - KANANA 429 promotes Kakao’s AI technologies and gathers user feedback. - “429” references the HTTP status code “Too Many Requests,” representing people with abundant enthusiasm and ideas about AI. - The program builds on Kakao’s first ambassador cohort, which included 20 participants. ## Results from the Previous Cohort - Participants communicated through KakaoTalk Open Chat. - They attended monthly offline meetups, informal group activities, and networking sessions with Kakao employees. - They previewed new Kakao AI services and exchanged feedback. - The cohort produced roughly 100 reviews and other pieces of content about Kakao’s AI services, models, and technologies. - Kakao selected and awarded five outstanding ambassadors. ## New Tracks and Benefits - **AI experts:** Test Kakao’s latest AI services and models and write in-depth reviews. - **Creators:** Produce content demonstrating practical ways to use Kakao AI. - **University students:** Promote the program on and off campus and collect user opinions. - The activity period has increased from three to five months. - Selected ambassadors receive AI service usage opportunities worth approximately 1 million won, along with additional benefits and special merchandise. ## Application and Schedule - Applicants must publish content related to Kakao AI and submit its URL through the recruitment page. - Applications are accepted until noon on February 19, 2026. - Every applicant receives a one-month free Kakao Emoticon Plus subscription. - Selected participants will be notified individually through Kakao’s official KakaoTalk channel on March 4. - The opening ceremony is scheduled for March 13 at Kakao AI Campus. Kakao is seeking applicants who are genuinely interested in AI and willing to communicate openly while helping shape and spread its AI services.

Read original(opens in new tab)
microsoft4 min readCurated summary

Diagnosing instability in production-scale agent reinforcement learning

Hugging Face has integrated its Post-Training Toolkit into TRL, bringing production-ready diagnostics to reinforcement learning and agent post-training pipelines. The work identifies a late-phase instability specific to tool-using, on-policy agents: variance can grow in post-tool contexts even while loss, reward, entropy, and global KL remain stable. Targeted tail, distributional, and effective-sample-size diagnostics can expose this failure before it becomes divergence. ## Production Monitoring for Long-Running Agents - Modern agent training runs over long horizons, uses external tools, and adapts continuously. - Failures often develop gradually rather than appearing as a single catastrophic event. - Standard aggregate metrics can hide rare but increasingly severe updates. - The proposed monitoring approach: - Computes diagnostics in-stream. - Separates text-only and post-tool interactions. - Aggregates statistics across workers. - Uses lightweight rolling windows and percentile tracking at fixed intervals. ## Tool-Conditioned Variance Amplification - Tool calls expand the state space through external transitions, exposing the policy to contexts it may rarely encounter in the reference distribution. - Training states can be modeled as: `d(s) = (1−α)·d_text(s) + α·d_tool(s)` - As the proportion of tool-conditioned states, `α`, increases, more updates occur where the reference policy assigns low probability to sampled actions. - This causes importance-weighted updates to develop increasingly large tails. - The mechanism is distinct from global entropy collapse or optimizer instability, though those factors may interact with it. ## Minimal Reproduction and Tail Diagnostics - A small on-policy experiment with an instruction-tuned open-weight model reproduced the pattern. - The 95th percentile of absolute per-token log-ratios, `|r|`, was tracked separately for text-only and post-tool contexts. - Findings included: - Text-only tail magnitudes remained stable or declined. - Post-tool tails grew steadily under fixed-policy baselines. - Drift-aware training substantially reduced tail growth. - Constraining tool outputs also suppressed the effect. - Aggregate loss, reward, and entropy remained stable while the tail was expanding. ## Distributional Shift in the Right Tail - Empirical CDFs across early, middle, and late training showed a change in distribution shape rather than a simple threshold crossing. - In tool-conditioned contexts: - The right tail flattened and stretched. - More probability mass moved toward high-magnitude updates. - Drift-aware baselines muted or reversed the shift. - This supports a distributional explanation rather than an artifact of choosing a particular percentile. ## Importance Ratios and Effective Sample Size - For ratio-based on-policy objectives, gradient variance is related to: `Var[ĝ] ∝ E[(π_θ(a|s) / π_ref(a|s))²]` - When `π_ref(a|s)` is small in tool-conditioned states, a small number of updates can dominate the estimator. - Larger batches and improved baselines may reduce noise but do not fix poor support overlap. - Effective sample size (ESS) provides a supporting signal: - ESS declines as importance weights become concentrated. - It is sensitive to window size and batch structure. - Its trends align with post-tool tail growth, but absolute values should not be over-interpreted. ## Delayed Failure and Misdiagnosis - Instability appears first in tool-conditioned contexts and may remain invisible in global metrics for a long time. - By the time aggregate metrics change, substantial variance amplification may already have accumulated. - The problem is often incorrectly attributed solely to optimizer behavior or inadequate global variance reduction. - Such interventions may delay failure without addressing the underlying support mismatch. - The mechanism is less pronounced when tool outputs are tightly constrained, policies are effectively frozen after tool calls, or interaction diversity plateaus early. The practical recommendation is to add slice-aware, tail-focused diagnostics to production TRL pipelines. Monitoring post-tool log-ratio percentiles, distributional changes, and supporting ESS trends can provide an early warning system for instability that global loss, reward, entropy, and KL metrics miss.

Read original(opens in new tab)
dropbox3 min readCurated summary

Engineering VP Josh Clemm on how we use knowledge graphs, MCP, and DSPy in Dash

Dropbox VP Josh Clemm argues that useful workplace AI requires a unified context engine capable of securely understanding and retrieving information across many SaaS applications. Dropbox Dash combines custom connectors, multimodal content processing, knowledge graphs, hybrid search, and personalized access-control-aware ranking to make that possible. Clemm favors indexed retrieval over purely federated approaches because preprocessing enables richer context, faster search, and company-wide access, though it requires substantial engineering and infrastructure. ## Building Dash’s Context Engine - Custom connectors crawl third-party applications while handling: - Rate limits - API differences - Application-specific permissions and ACLs - Incoming content is normalized, often into Markdown, and enriched with: - Titles and metadata - Extracted links - Embeddings - Other key information - Different media types require different processing: - Documents can be text-extracted and indexed. - Images may require CLIP or multimodal models. - PDFs combine text, figures, and other elements. - Audio is transcribed. - Videos may require scene-by-scene multimodal analysis when dialogue is insufficient. - Dash models relationships between content as a knowledge graph: - Meetings can connect to documents, participants, transcripts, and previous notes. - Cross-application relationships provide richer context for search and agents. - Data is stored in secure systems using: - BM25 lexical search - Dense-vector storage - Hybrid retrieval - Multiple ranking stages personalize results and enforce user-specific permissions. ## Indexed Retrieval Versus Federated Retrieval - Federated retrieval queries external systems at runtime. - Its advantages include: - Fast initial implementation - Minimal storage requirements - Relatively fresh data - Easy addition of MCP servers and connectors - Its drawbacks include: - Inconsistent API speed, quality, and ranking - Limited access to company-wide content - Expensive post-processing and reranking - Large token usage when agents reason over returned results - Indexed retrieval preprocesses content during ingestion. - Its advantages include: - Access to shared company connectors - Enriched datasets created offline - Faster queries - More opportunities for recall and ranking experiments - Its costs include: - Significant custom connector development - Freshness challenges - High hosting costs - Difficult storage and architecture choices involving vector search, BM25, hybrid retrieval, or graph RAG. ## Making MCP Practical at Scale - MCP can simplify tool integration, but tool definitions consume substantial context-window space. - Large tool descriptions and retrieval results contribute to context rot and reduce agent effectiveness. - Dash aims to limit context usage to roughly 100,000 tokens. - MCP-based agents can also be slow: simple queries may take up to 45 seconds, while direct index retrieval returns results within seconds. - Dropbox’s approach is to wrap its index in a consolidated “super tool,” reducing the need to expose many separate tools to the agent. ## Broader AI Engineering Practices - The talk also covers Dropbox’s use of: - LLMs as evaluators or judges - Prompt optimization with DSPy - Tool calling and MCP design - These techniques complement the underlying context engine rather than replacing the indexing, enrichment, graph modeling, and permission systems required for reliable workplace AI. A practical takeaway is that organizations building AI over proprietary data should treat retrieval as a full data-platform problem. Start with robust connectors and permissions, enrich content before retrieval, model relationships across sources, and use MCP selectively where indexed retrieval can provide faster and more controlled results.

Read original(opens in new tab)
grammarlyOriginal article

AI Assistants vs. AI Agents: What’s the Difference and When to Use Each (opens in new tab)

While AI assistants and agents often share the same large language model foundations, they serve distinct roles based on their level of autonomy and task complexity. Assistants operate on a reactive "prompt-response" loop for immediate, single-step tasks, whereas agents function as semi-independent systems capable of planning and executing multistep workflows to achieve a broader goal. Ultimately, the most effective AI strategy involves leveraging assistants for quick, guided interactions while utilizing agents to manage complex, coordinated projects that require memory and tool integration. ### Reactive vs. Proactive AI Architectures * Assistants are reactive tools that follow a "prompt-response" loop, similar to a tennis match where the user must always serve to initiate action. * Agents are proactive and semi-independent; once given a high-level goal, they can decompose it into actionable steps and execute them with minimal step-by-step direction. * In a practical scenario, an assistant might summarize meeting notes upon request, whereas an agent can organize those notes, assign tasks in a project management tool, and schedule follow-ups automatically. ### Technical Capabilities and Coordination * Both tools utilize Large Language Models (LLMs) to understand natural language, but agents incorporate advanced features like long-term memory and cross-app integrations. * Memory allows agents to retain feedback and results from previous interactions to deliver better outcomes over time, while integrations enable them to act on the user's behalf across different software platforms. * The two systems often work in tandem: the assistant acts as the front-facing interface (the "waiter") for user commands, while the agent acts as the back-end engine (the "kitchen") that performs the orchestration. ### Balancing Control and Complexity * AI assistants provide high user control and instant setup, making them ideal for "out of the box" tasks like grammar checks, rephrasing text, or answering quick questions. * AI agents excel at reducing cognitive load by managing "moving parts" like deadline tracking, organizing inputs from different stakeholders, and maintaining project states across various tools. * Grammarly’s implementation of agents serves as a technical example, moving beyond simple text revision to offer context-aware suggestions that help with brainstorming, knowledge retrieval, and predicting audience reactions. To maximize productivity, users should delegate isolated, high-control tasks to AI assistants while allowing AI agents to handle the background orchestration of complex projects. Success with these tools depends on maintaining human oversight, using assistant-led prompts to provide the regular feedback that agents need to refine their autonomous workflows.