Tygart Media

Tag: AI Tools

  • Everett Police Is Getting a $327K Augmented Reality Training System — Funded Entirely by Federal Grant

    Everett Police Is Getting a $327K Augmented Reality Training System — Funded Entirely by Federal Grant

    Q: Is Everett Police getting augmented reality training technology?
    A: Yes. The Everett City Council is scheduled to approve a $327,573 purchase of an InVeris FATS AR augmented reality training system for EPD on May 13, 2026 — fully funded by a federal DOJ COPS grant, with no general fund money involved.

    Everett Police Department is set to receive a major training upgrade: a mobile augmented reality platform that projects digital subjects and threats into real physical spaces, letting officers practice de-escalation and crisis response scenarios in actual buildings, hallways, and parking lots — not just a shooting range.

    The Everett City Council is scheduled to approve a sole-source purchase of the InVeris FATS AR (Augmented Reality) Training System on May 13 as a consent agenda item. Total cost: $327,573.07 ($298,064.67 system cost plus $29,508.40 in tax). Funding source: a federal grant from the U.S. Department of Justice under the COPS FY25 Safer Outcomes program. No general fund money is involved.

    What the System Does

    The InVeris FATS AR system scans a real physical environment — a room, a corridor, a lobby — and overlays computer-generated characters into it. Officers see the actual space around them alongside digitally projected individuals they must interact with, de-escalate, or respond to in real time.

    According to the resolution cover sheet signed by Police Chief Robert Goetz, the system supports:

    • Multi-officer participation in the same scenario simultaneously
    • Real-time instructor control over how scenarios evolve — the instructor can introduce new elements, escalate or de-escalate situations, and change variables mid-exercise
    • Integrated after-action review with positional tracking, weapon orientation data, and performance analytics — so officers and instructors can review exactly what happened and why
    • BlueFire® smart weapon integration — training weapons communicate with the system, tracking how and when officers raise or use them

    The scenarios EPD is specifically targeting with the system: situations involving individuals experiencing mental health crises, behavioral health conditions, and other complex interactions “that require communication, decision-making, and peer intervention,” per the resolution.

    This directly connects to the department’s direction under Chief Goetz’s community policing strategy, which has emphasized de-escalation skill-building alongside enforcement. The AR system delivers that philosophy in a high-fidelity, data-recordable training environment where officers can fail safely, reset, and learn from what the system captured.

    Why It’s a Sole-Source Purchase

    The resolution asks the council to waive standard public bidding requirements. Under normal circumstances, contracts of this size go through competitive bidding. The justification here, per state law (RCW 39.04.280) and federal grant rules (2 CFR 200.320(c)): there is only one vendor that makes this system.

    The cover sheet states: “no other commercially available system meets the department’s operational requirements for multi-officer, real-world, augmented-reality training with integrated weapon functionality and instructor-controlled adaptability.”

    InVeris holds patents on the core technology — including real-world environment scanning, the BlueFire® weapon integration, and AI-driven scenario control — that competitors cannot replicate. EPD’s market research confirmed no alternative system qualifies.

    Sole-source purchases are reviewed and approved by the City Council case by case. Placing it on the consent agenda signals that city staff reviewed the sole-source documentation and found it meets the statutory threshold.

    The Federal Grant Behind It

    The COPS FY25 Safer Outcomes grant from the U.S. Department of Justice targets police departments investing in training and technology designed to reduce use-of-force incidents and improve officer-civilian outcomes.

    EPD’s grant application tied the InVeris AR system to Safer Outcomes priorities: crisis response, de-escalation, and officer decision-making training — particularly for encounters involving individuals in mental health or behavioral health situations.

    The grant covers the full system cost. Everett taxpayers are not paying for this purchase from the general fund.

    The approach aligns with a national trend in law enforcement training: moving from static range-and-role-player exercises toward immersive, data-rich scenario environments. AR lets EPD run more training sessions faster, reset immediately between scenarios, and accumulate a performance record over time that supports individual officer coaching.

    What Happens at the May 13 Meeting

    The InVeris resolution is on the consent agenda for May 13 — meaning it’s expected to pass as part of a block vote alongside routine items like claims payables and contract extensions. Consent items move without individual debate unless a council member pulls one for separate discussion.

    The May 13 meeting at City Hall begins at 6:30 p.m. The utility tax and rate ordinances are also on Wednesday’s agenda for their first readings. It is one of the more substantive midweek council sessions of the spring.

    What To Do Next

    • Watch the May 13 meeting: Live at YouTube.com/EverettCity, 6:30 p.m.
    • Read the resolution and grant materials: Available in the May 13 agenda packet at everettwa.gov/AgendaCenter.
    • Contact EPD: Police Chief Robert Goetz, RGoetz@everettwa.gov, 425-754-4540.

    Frequently Asked Questions

    Who is paying for this?

    The federal government, through a COPS FY25 Safer Outcomes grant from the U.S. Department of Justice. The full $327,573.07 cost comes from the grant. Everett’s general fund is not used.

    What is InVeris FATS AR?

    FATS stands for Firearms Augmented Training System. The AR version projects digital characters into real physical environments, allowing officers to train in actual spaces — a building, a room, an outdoor area — rather than a dedicated simulation lab. The system is the only untethered AR training platform designed for law enforcement available in the current market.

    Why isn’t this put out to competitive bid?

    The City and EPD determined that InVeris is the only vendor with a commercially available AR training system meeting their requirements for multi-officer participation, real-world scanning, and integrated smart weapon functionality. Under state law and federal grant rules, a sole-source purchase is permitted when no alternative exists. The council reviews and approves the waiver.

    What kinds of scenarios will officers train on?

    Primarily de-escalation and crisis response, including encounters with individuals experiencing mental health crises or behavioral health episodes. The system records officer behavior for after-action review and coaching. The scenarios align with EPD’s COPS FY25 Safer Outcomes grant priorities.

    Has EPD used AR training before?

    The resolution does not reference prior AR training at EPD. This would be the department’s first InVeris FATS AR system.

    When will EPD have the system?

    The council is expected to approve the purchase on May 13, 2026. Delivery and installation timelines depend on InVeris’s production schedule following a purchase order.

  • Everett’s Utility Tax and Rate Bills Go to First Reading Wednesday — Final Vote May 27

    Everett’s Utility Tax and Rate Bills Go to First Reading Wednesday — Final Vote May 27

    Q: When will Everett vote on the utility tax?
    A: The Everett City Council is scheduled to hold the final vote on CB 2605-27 (utility tax) and CB 2605-26 (utility rates) on May 27, 2026. First reading is May 13. If both ordinances pass, the new rate structure takes effect August 1, 2026.

    The ordinances that would replace Everett’s 6% water-and-sewer payment with a 12% utility tax — and update the rate tables to match — are officially on Wednesday’s City Council agenda. Two companion bills, CB 2605-27 and CB 2605-26, go to first reading at 6:30 p.m. on May 13 at City Hall, 3002 Wetmore Ave.

    If both advance through three readings without amendment, the final vote lands May 27. Rate changes would take effect August 1, 2026 — about 11 weeks away. Here’s what each bill does and why it matters to your water bill.

    The Two Bills, Explained

    CB 2605-27: The Utility Tax Ordinance

    This bill replaces the City’s existing 6% payment in lieu of taxes (PILOT) — a mechanism in place since a June 1, 1983 City Council resolution — with a 12% utility tax on the City’s water and sewer utility (Fund 401).

    The legal distinction matters: the PILOT was an internal transfer between city departments. A utility tax is a formal statutory charge under RCW 35.22.195 that shows up directly in rate calculations. The rate is doubling and the structure is changing simultaneously.

    According to the ordinance cover sheet, Finance Director Mike Bailey is the contact. The purpose, stated plainly in the bill: “to impose a 12% utility tax on the City’s water and sewer utility for the purpose of increasing revenue available for core City services.”

    CB 2605-26: The Rate Amendments

    This is the bill most residents will see on their monthly statement. It amends Everett’s established utility rates for 2025 through 2028 to account for the new utility tax, plus a $1 increase to the base filtration rate to allow the utility to retire some existing filtration debt ahead of schedule.

    The rate table in the ordinance shows what single-family sewer customers would pay each year:

    PeriodSingle Family Sewer (Monthly)
    2025$104.04
    2026 Jan–July$118.49
    2026 Aug–Dec$126.78 (if approved)
    2027$141.99
    2028+$158.51

    The August 2026 jump — from $118.49 to $126.78 — is roughly $8.29 more per month on sewer alone for a single-family home. Water and filtration rates are also amended; the full tables are in the ordinance. The City has previously estimated the total combined impact of the utility tax change at approximately $10.74 per month for a typical residential customer.

    Note: the bill’s rate table states that monthly charges “include Surface Water Quality Protection and Enhancement and the current state and city utility tax” — meaning the new rates are designed to be all-in figures once both ordinances pass.

    Why This Is Happening

    Everett is facing what city documents call a structural budget challenge: the cost of providing core services is growing faster than revenues. The projected 2027 general fund deficit has been pegged at approximately $14 million. The utility tax and rate changes are one lever the city is pulling to address it.

    Other levers under active discussion include potential regionalization of fire services through a regional fire authority (RFA), Sno-Isle library regionalization, a new levy lid lift, and annexation of the Mariner neighborhood — most of which require voter approval. The utility tax does not: it is a council-authorized charge under state law.

    The PILOT mechanism has been in place since 1983. Moving to a formal utility tax aligns Everett’s structure with how other Washington cities handle internal utility revenue transfers.

    What Happens Next

    The legislative timeline for both bills:

    • May 13: Briefing and 1st Reading (both bills)
    • May 20: 2nd Reading (CB 2605-26 public hearing also scheduled May 20)
    • May 27: 3rd and Final Reading — action vote on both ordinances

    Between now and May 27, residents can submit written public comments to the Everett City Council at council@everettwa.gov or by mail to 2930 Wetmore Ave., Suite 9A, Everett, WA 98201. Remote speakers can register via everettwa.gov/speakerform at least 30 minutes before each meeting.

    What Residents Should Know

    • No voter approval required. Unlike a levy lid lift, this is a council-only vote. There is no ballot measure.
    • Two bills, one outcome. CB 2605-27 (tax) and CB 2605-26 (rates) are companion ordinances. Both need to pass for the full rate structure to work as designed.
    • Outside-city customers are also affected. Everett operates a regional water system serving customers across much of Snohomish County. The rate ordinance covers outside-city rates as well.
    • The filtration rate increase is separate. The $1 base filtration increase included in CB 2605-26 accelerates debt retirement — a distinct financial item bundled into the same bill.
    • This has been in the works since at least April. The proposal first surfaced publicly in the City’s spring budget discussions and has been anticipated since the City disclosed its fiscal gap earlier this year.

    What To Do Next

    • Read the bills: CB 2605-27 and CB 2605-26 are available in the May 13 agenda packet at everettwa.gov/AgendaCenter.
    • Comment in writing: Email council@everettwa.gov before May 20 to ensure comments reach members ahead of the final vote.
    • Attend or watch: City Hall, 3002 Wetmore Ave., Wednesdays at 6:30 p.m. Live stream at YouTube.com/EverettCity.
    • Register to speak remotely: everettwa.gov/speakerform, at least 30 minutes before the meeting.
    • Questions about the ordinance: Finance Director Mike Bailey at mbailey@everettwa.gov.

    Frequently Asked Questions

    What is the utility tax rate being proposed?

    CB 2605-27 proposes a 12% utility tax on the City’s water and sewer utility, replacing the existing 6% payment in lieu of taxes (PILOT) that has been in place since 1983.

    When would the new rates take effect if approved?

    August 1, 2026, per CB 2605-26.

    Does this require voter approval?

    No. A utility tax is a council-authorized charge under state law (RCW 35.22.195). The City Council votes on it; it does not go to a public ballot.

    How much will this add to a typical bill?

    The City has estimated approximately $10.74 per month for a typical residential customer. The rate ordinance shows single-family sewer rates going from $118.49 to $126.78 in August 2026 — about $8.29 more per month on that line alone. Water and filtration rate changes are in the full ordinance.

    Why is the City doing this now?

    Everett projects a roughly $14 million general fund deficit in 2027. The utility tax is one of several revenue-side measures under discussion. Unlike a levy lid lift or annexation vote, it doesn’t require voter approval — making it one of the faster-moving options available to the council.

    Who does this affect beyond Everett city limits?

    Everett operates a regional water system that serves customers across much of Snohomish County. The rate ordinance covers outside-city customer rates as well as city customers.

    Is there a public hearing?

    Yes — a public hearing on the rate ordinance (CB 2605-26) is scheduled for May 20, alongside the 2nd reading. Written comments can also be submitted to council@everettwa.gov at any time before the May 27 vote.

  • Mason County Roads — May 8, 2026

    Mason County Roads — May 8, 2026

    Published: May 8, 2026 · Sources: WSDOT, Mason County Public Works, Shelton-Mason County Journal · Check WSDOT live map →

    Active Alerts — Check Before You Drive

    No WSDOT-issued emergency closures or alerts found for Mason County highways as of this morning. For real-time conditions on your specific route, use these official sources directly:

    Major Projects — Current Status

    SR-3 Freight Corridor (Belfair Bypass)

    Status: Construction expected to begin 2026, completion targeted 2028 — but funding is under threat.

    The SR-3 Freight Corridor — the bypass that will route regional freight and commuter traffic around Belfair’s main corridor — has $48.3M secured and construction is planned to begin this year. However, Governor Ferguson’s proposed transportation budget would delay final funding from the 2027-29 biennium to 2031-33, effectively pushing completion years into the future.

    Mason County Commissioners sent a letter to House Transportation Committee Chair Jake Fey urging the Legislature to restore the funding on schedule, calling the delay “an economic, safety, and infrastructure issue with real and immediate consequences.” The corridor is designed to carry local trips, freight, emergency response, school buses, and commuter traffic on separate infrastructure rather than all competing on the same road through Belfair’s center.

    Source: Shelton-Mason County Journal, February 19, 2026

    Olympic Highway North — Shelton

    Status: Design phase. Construction not before summer 2027.

    The City of Shelton’s $6 million repaving project for Olympic Highway North — from C Street to Wallace Kneeland Boulevard — is in the design and public comment phase. The road hasn’t been paved in 37 years. Consultant Transpo Group is finalizing the preferred design following a March 10 community meeting where about 50 residents weighed in on four layout options, including roundabout and bike lane configurations.

    Timeline: Final design expected to be completed this winter. Project goes out for bid in spring 2027. Construction could begin summer 2027. The project is funded by two grants including a $3.7 million grant from the state Transportation Improvement Board.

    Source: Shelton-Mason County Journal, March 19, 2026 · City of Shelton project page

    SR-3 Safety Improvements — Shelton (Craig Road to Arcadia Road)

    Status: Pre-design. No construction date set yet.

    WSDOT is planning roundabouts at Craig Road, Mill Creek Road, and Arcadia Road on SR-3 in Shelton, along with a center median to reduce left-turn conflicts and encourage safer speeds. A public comment period closed April 6. No construction timeline has been announced — this is still in pre-design. Watch WSDOT’s project page for updates.

    SR-3 Belfair Area — Widening Near Romance Hill

    Status: Ongoing widening project.

    This project extends the center turn lane and adds paved shoulders and sidewalks on both sides of SR-3 from milepost 25.3 to 27 near Belfair. Work has involved overnight lane realignments near Romance Hill. Check the WSDOT travel map for current lane status.

    Commuter Notes for Today

    • SR-3 through Belfair: No emergency closures reported. Standard congestion expected during school and commute hours at Belfair’s main intersection.
    • US-101 through Shelton/Kamilche: No active alerts this morning. Check WSDOT alerts for any weather-related changes.
    • SR-106 (Union/Belfair area): No active alerts. Permanent speed limit reduction near Union remains in effect — reduced from previous limit, watch signs through the Union section.

    Report a Road Issue

    If you see a problem on a state highway — pothole, signal outage, debris — report it directly:

    This briefing is published each morning using official WSDOT and Mason County Public Works sources. For the most current conditions at any moment, always check the WSDOT live map directly — road conditions change faster than any daily briefing can track.

  • North Mason School Levy Passes — What It Means, What It Doesn’t, and What Comes Next

    North Mason School Levy Passes — What It Means, What It Doesn’t, and What Comes Next

    Certification status: The Mason County Auditor’s Canvassing Board meeting to certify this election is scheduled for May 8, 2026 at 2:00 PM. The vote totals below are from the April 30 preliminary count. For the official certified result, check the Mason County Auditor elections page directly.

    The Vote

    North Mason School District’s four-year education programs and operations (EP&O) replacement levy passed in the April 28, 2026 special election. The Mason County Auditor’s Office reported the following preliminary totals across both Mason and Kitsap counties:

    CountyYesNoYes %
    Mason County2,0891,80853.61%
    Kitsap County414348.81%
    Combined2,1301,85153.50%

    Source: Shelton-Mason County Journal, April 30, 2026

    This was the third attempt after the levy failed twice in 2025 — in February (46.17% yes) and again in a subsequent election. The district lowered the tax rate for this third proposal to $1.01 per $1,000 of assessed value for 2027–2030, down from $1.28/$1.24/$1.21/$1.17 in the two failed proposals.

    What Superintendent Michael Said

    Superintendent Kristine Michael responded to the preliminary results Tuesday night. The Shelton-Mason County Journal quoted her directly: “We are very pleased and encouraged by these preliminary results, and we will be monitoring closely as ballots continue to be counted and certified. If this outcome holds, it reflects the trust this community is placing in our schools and our students. I do not take that trust lightly, and I will continue working to restore and strengthen the community’s confidence in our schools.”

    What the Levy Funds — and What It Doesn’t Fix Right Away

    This is where parents and community members need to read carefully. Passage of the levy does not undo the cuts that already happened.

    The district made $3 million in cuts at the end of the 2025–26 school year after the levy expired at the end of 2025. Those cuts hit athletics, student activities, and staff positions directly. The levy’s replacement funding will not arrive until April 2027 at the earliest — Superintendent Michael confirmed this timeline with the Journal before the election.

    Michael was explicit about what that means even in a passage scenario: “Those funds would allow us to avoid making additional reductions, but because we are operating with only a partial year of levy revenue even in a passage scenario, we would not be in a position to restore programs or positions already reduced.”

    In plain terms: the levy passing stops the bleeding, but it does not reverse it. Programs and positions already cut are not automatically restored. The district will need to work through its budget process for the 2027–28 school year before any restoration decisions are made.

    What the Levy Rate Means for Property Owners

    At $1.01 per $1,000 of assessed value, a home assessed at $400,000 would pay approximately $404 per year — or about $33.67 per month — toward the levy for 2027 through 2030. This is the lowest rate of the three proposals the district has put to voters.

    The History Behind This Vote

    North Mason has a difficult levy history. The district experienced two EP&O failures in 2020, which triggered significant budget cuts then as well. The current levy that expired replaced the one approved barely — at 50.3% — in 2021. The two 2025 failures set the stage for the $3 million in cuts that went into effect this school year, and for the third attempt at a lower rate that passed April 28.

    What to Watch Next

    • May 8, 2026: Mason County Auditor Canvassing Board meets at 2:00 PM to certify the election. Official certified results will be posted to the Mason County Auditor elections page.
    • 2026–27 school year: The district operates without full levy revenue. No program restorations expected this year.
    • April 2027: Earliest date levy funds begin flowing to the district.
    • 2027–28 budget process: The first realistic opportunity for the school board to consider restoring cut programs and positions, subject to budget conditions at that time.

    For ongoing North Mason School District updates, the district’s official communications are at northmasonschools.org. Election results and certification status are at the Mason County Auditor’s Office.

  • History of Anthropic

    History of Anthropic

    Last refreshed: May 15, 2026

    Redirecting… Click here if not redirected

  • Why Rural Washington’s Fiber Buildout Matters for the AI Era — A Mason County Perspective

    Why Rural Washington’s Fiber Buildout Matters for the AI Era — A Mason County Perspective

    If you’ve been following Mason County’s PUD 3 fiber expansion — the gigabit buildout reaching Cloquallum and pushing toward Belfair — you might be thinking about faster streaming or more reliable video calls. That’s real. But there’s a bigger story underneath it, one that connects directly to where work, business, and information are heading.

    The AI tools that are reshaping professional work — coding assistants, document analysis, agent automation — are bandwidth-intensive, latency-sensitive applications. They are not designed for satellite internet with 600ms ping times or DSL connections that struggle past 10Mbps. Gigabit fiber is the infrastructure layer that determines whether you can use these tools the same way someone in Seattle or Bellevue does. That gap matters more than most people realize right now.

    What AI Tools Actually Require

    The practical bandwidth requirements for AI-assisted work are modest by gigabit standards — but they are real, and they add up quickly in a household or small business where multiple people are working simultaneously.

    • Claude, ChatGPT, Gemini via browser: Low bandwidth per session, but latency matters for agentic tasks that involve multiple back-and-forth exchanges. A 200ms round-trip feels fine; 600ms feels broken during long agentic runs.
    • Claude Code and coding agents: These tools read and write files, run terminal commands, and stream outputs continuously. On a slow connection, the feedback loop that makes these tools useful breaks down.
    • Document processing pipelines: Uploading a 50-page PDF or a folder of images for analysis on a 5Mbps upload connection takes long enough to interrupt workflow. On gigabit fiber it’s nearly instant.
    • Video + AI combined workflows: Remote workers using AI transcription, real-time meeting assistants, or AI-enhanced video conferencing stack bandwidth requirements that rural connections routinely can’t sustain.

    None of this is about luxury. It’s about whether the productivity gains that AI tools deliver are accessible equally — or whether they accrue disproportionately to people already located in well-connected metro areas.

    The Mason County Context

    PUD 3’s Cloquallum fiber project has a May 31, 2026 signup deadline for residents in the service area. The broader PUD 3 gigabit buildout has been expanding through the county with the goal of bringing symmetrical gigabit service to areas that have been underserved for years.

    For Mason County property owners, fiber access is already showing up in home valuations — buyers who work remotely increasingly treat fiber availability as a binary filter. For business owners, the calculus is more direct: reliable symmetric bandwidth is now a prerequisite for the category of software tools that are compressing what small teams can produce.

    What This Looks Like in Practice

    A small business owner in Shelton or Belfair with gigabit fiber can run the same AI-assisted workflows as a marketing agency in Seattle. That means:

    • Using Claude via the API to automate document-heavy back-office work — contracts, proposals, intake forms — at a cost that’s measured in cents per task rather than hours of labor
    • Running Claude Code for software development or automation scripting without the latency that makes agentic coding tools frustrating on slow connections
    • Participating in distributed teams where AI-enhanced collaboration tools are standard — video calls with live transcription, shared AI workspaces, automated meeting summaries
    • Building content, analysis, or research pipelines that would previously have required hiring specialized staff

    None of these use cases require a computer science degree. The current generation of AI tools — particularly Claude’s May 2026 updates including managed agents and the expanded connector ecosystem — are built for people who want to use AI to get work done, not people who want to study AI.

    The Bigger Picture: Rural Participation in the AI Economy

    There’s a version of the AI transition that looks like previous technology shifts — where the productivity gains concentrate in places that already have infrastructure advantages, and rural areas fall further behind. Fiber buildouts like PUD 3’s are the infrastructure decision that determines which side of that divide Mason County lands on.

    The tools themselves are increasingly cloud-based and location-agnostic. Claude doesn’t care whether you’re in Bellevue or Belfair. The connection does.

    This is why local infrastructure decisions that might look like routine utility policy — a PUD fiber deadline, a county broadband study — are actually decisions about economic participation in what’s coming next. The May 31 signup deadline for Cloquallum fiber isn’t just a utility question. It’s an access question.

    If You’re New to AI Tools and Have the Connection

    If PUD 3 fiber has reached your area and you haven’t explored what current AI tools can actually do for your work, a few starting points:

    • The Anthropic Console — where to get an API key and start building with Claude directly
    • Claude pricing — what each plan costs and which one makes sense for individual vs. team use
    • What Claude can do as of May 2026 — the current state of the tools, including the managed agents and connector expansion that make it useful for non-developers

    The infrastructure and the tools are both moving fast. Mason County’s fiber buildout is the local side of a much larger story.

  • Claude Code Is Shipping 2–3 Releases Per Week — What the v2.1 Cadence Means for Engineering Teams

    Claude Code Is Shipping 2–3 Releases Per Week — What the v2.1 Cadence Means for Engineering Teams

    Last refreshed: May 15, 2026

    Between April 15 and April 29, 2026, the Claude Code team shipped releases from v2.1.89 to v2.1.123 — 34 version increments in 14 days, or roughly 2–3 production releases per week. For an agentic coding tool that engineering teams run in their daily development workflow, this release cadence is worth understanding, both for what it signals about the product’s development velocity and for the practical implications of staying current.

    What’s Driving the Cadence

    The v2.1 series is where Claude Code’s parallel agents architecture is being built out. The desktop redesign for parallel agents shipped on April 14, and the v2.1 releases since then represent the iterative work of making parallel agent workflows — running multiple agents simultaneously from a single workspace — stable and usable at production quality. Rapid iteration on a new architectural feature explains the compressed release schedule better than any other factor.

    The new onboarding guide for Claude Code teams, published April 28 on code.claude.com, is a related signal. Documentation for team-scale adoption typically follows (not precedes) the stability work that makes team-scale adoption advisable. Publishing the onboarding guide now suggests the team considers the core parallel agents architecture stable enough for broader engineering team adoption.

    Parallel Agents: The Architecture Change That Matters

    The April 14 desktop redesign for parallel agents is the most significant Claude Code architectural change of the quarter. Previously, Claude Code operated as a single-agent tool — one active task at a time per workspace. The parallel agents redesign allows developers to run multiple agents simultaneously, each working on independent tasks within the same workspace, with Claude coordinating between them.

    The practical applications are significant: running tests while implementing a feature, refactoring one module while debugging another, generating documentation in parallel with code review. Tasks that previously required sequential attention can now run concurrently, compressing the time from specification to working code.

    Implications for Engineering Teams Evaluating Adoption

    The combination of the new onboarding guide and the parallel agents architecture makes this the right moment for engineering teams that have been evaluating Claude Code to make a decision. The tool has moved from “impressive demo” to “documented team workflow” with the April 28 guide, and the parallel agents capability meaningfully changes the productivity math for teams doing complex, multi-threaded development work.

    For teams already using Claude Code, staying current with the v2.1 series matters more than it did in earlier versions. The 2–3 weekly releases aren’t cosmetic — they’re iterating on the parallel agents infrastructure that the most powerful new workflows depend on. Check the changelog at code.claude.com/docs/en/changelog before major projects to ensure you’re running a recent build.

    Source: Claude Code Changelog | GitHub Releases

  • Cowork Is No Longer a Research Preview — Here’s What Changes for Non-Developers Today

    Cowork Is No Longer a Research Preview — Here’s What Changes for Non-Developers Today

    Last refreshed: May 15, 2026

    Anthropic’s Cowork feature — the desktop automation tool aimed squarely at non-developers — moved out of research preview on April 29, 2026, and is now generally available on both macOS and Windows. It ships with a feature set that represents a meaningful step forward for anyone who has been running scheduled tasks, file workflows, and multi-step automations through Claude without writing a line of code.

    What’s New in the GA Release

    The GA release lands on Pro, Max, Team, and Enterprise plans. The headline additions are expanded analytics, OpenTelemetry support for enterprise observability, and role-based access controls — the last of these being the signal that Cowork is now ready for team deployments, not just individual power users.

    Persistent agent threads are now live across both mobile (iOS and Android) and desktop, which means you can start a Cowork task on your laptop and monitor or manage it from your phone. The new Customize section consolidates skills, plugins, and connectors into a single panel, replacing what was previously a scattered setup experience across multiple menus.

    Recurring and on-demand task scheduling is also included, enabling the kind of “set it and check it” automation workflows that Cowork was always promising but only partially delivering during the preview period.

    Why This Matters for Non-Developers

    Cowork’s core bet has always been that the most valuable use cases for AI automation don’t belong to engineers — they belong to operators, marketers, content teams, and business owners who know exactly what they want done but have no interest in writing Python scripts or JSON configs to get there. The GA release validates that bet with a production-grade infrastructure story: OpenTelemetry means IT and enterprise security teams can audit what the agents are doing; role-based access controls mean managers can delegate without handing over full system access.

    For the non-developer using Cowork day-to-day, the practical change is reliability. Research previews carry an implicit asterisk — “this works, mostly, until it doesn’t.” GA means the feature is supported, documented, and subject to real SLAs. Scheduled tasks that have been running through the preview period should now be more stable, and new automations can be built with the expectation that they’ll still work next month.

    The Enterprise Observability Story

    The addition of Cowork data into the Analytics API and OpenTelemetry support is worth noting separately. This is the detail that unlocks enterprise adoption at scale. Procurement and security teams at larger organizations have consistently asked for auditability before green-lighting AI automation tools. Cowork now has an answer: every agent action can be traced, logged, and routed into whatever observability stack the enterprise already runs.

    For Team and Enterprise plan subscribers, this should accelerate internal approval processes for Cowork deployments that may have stalled during the preview period.

    What Stays the Same

    The fundamental Cowork model — Claude running autonomous tasks on behalf of the user, triggered by schedule or on-demand, guided by skills and connectors — is unchanged. If you’ve been running workflows in the preview, the transition to GA should be seamless. The Customize section reorganizes the setup experience but doesn’t require rebuilding existing configurations.

    Plans and pricing remain unchanged from the research preview tier placement — Cowork is included in Pro, Max, Team, and Enterprise, with no new add-on cost announced alongside the GA release.

    The Bottom Line

    Cowork GA is the milestone that turns a promising experiment into a product you can build operational workflows around. The combination of persistent threads, role-based access, and OpenTelemetry support brings Cowork into alignment with what enterprise buyers require from any automation tool they’re willing to run at scale. For individual users, the reliability improvement and the cleaner Customize panel are the day-one wins. For teams, the observability story is the green light many have been waiting for.

    Source: Anthropic Cowork Release Notes

  • Notion AI vs Zapier AI: Which Automation Layer Wins For Your Use Case

    Notion AI vs Zapier AI: Which Automation Layer Wins For Your Use Case

    Notion AI vs Zapier AI: Which Automation Layer Wins For Your Use Case

    The 60-second version

    Zapier and Notion AI overlap in concept (automate routine work) but optimize for different operators. Zapier: massive integration catalog, no-code, simple triggers and actions, optimized for “if this, then that” patterns. Notion AI: AI reasoning native, deep workspace context, optimized for “decide what to do given context, then act.” Use Zapier for breadth of simple automations. Use Notion Agents for depth of reasoning. The two are complementary.

    When Zapier wins

    • You need many simple automations across many apps
    • Non-technical operators need to build automations themselves
    • The trigger logic is straightforward (if X, do Y)
    • You don’t have or want AI reasoning in the loop
    • You’re not heavily invested in Notion as a platform

    When Notion Agents win

    • The workflow requires understanding Notion workspace content
    • AI reasoning about whether and how to act matters
    • Schedule-driven autonomous work is the goal
    • The workflow output is in Notion or affects Notion data
    • You want agents that can compose multi-step reasoning

    What Zapier does that Notion Agents don’t

    • Thousands of app integrations out of the box
    • Visual no-code building accessible to non-developers
    • Flat-rate pricing easier to budget
    • Established for years; lots of recipes and patterns

    What Notion Agents do that Zapier doesn’t

    • AI reasoning native to the workflow
    • Workspace context understanding
    • Skills (natural-language workflow definitions)
    • Workers for custom code
    • Database fluency at the platform level

    The combined pattern

    Many operators use both:
    – Zapier for cross-app plumbing (lead from form → CRM → Slack → email)
    – Notion Agents for workspace reasoning (synthesize lead context, decide priority, draft response)
    – Sometimes Zapier triggers a Notion agent run
    Treat them as layers: Zapier moves data; Notion Agents make decisions about that data.

    Where this goes wrong

    1. Trying to use Zapier for AI reasoning. Zapier has AI features but they’re shallow compared to Notion Agents.
    2. Trying to use Notion Agents for cross-app plumbing. Possible via Workers/MCP, but Zapier’s integration catalog is broader.
    3. Picking based on price alone. The right tool for the job costs less than the wrong tool, even at higher per-task pricing.

    What to read next

    Notion Agents vs n8n Alone, n8n MCP Bridge, Workers + External APIs, AI-Native Company Patterns.

  • Notion AI vs Gemini for Workspaces: The Document AI Showdown

    Notion AI vs Gemini for Workspaces: The Document AI Showdown

    Notion AI vs Gemini for Workspaces: The Document AI Showdown

    The 60-second version

    Most “Notion AI vs Gemini” comparisons miss the actual decision: which platform does your work live in? If you’re a Notion-first team, Notion AI is the integrated answer. If you’re a Google Workspace team, Gemini integrates more deeply into Docs, Sheets, Slides, and Gmail than any third-party AI will. Trying to use both heavily creates context-splitting problems. Pick the platform first. The AI follows.

    When Notion AI wins

    • Your work lives in Notion (databases, pages, agents)
    • You use Custom Agents on schedules
    • Cross-source synthesis across Notion + connected sources matters
    • Database manipulation and Autofill is core to your workflow
    • Multi-app integration via MCP and Workers

    When Gemini for Workspace wins

    • Your work lives in Google Docs, Sheets, Slides
    • Real-time multi-user document collaboration is dominant
    • Email and calendar are the primary surfaces (Gemini’s Gmail integration is strong)
    • Sheets-heavy analysis benefits from Gemini’s native data understanding
    • You’re already paying for Google Workspace

    The stacking question

    Some teams run both. Three patterns that work:
    1. Notion as second brain, Google as collaboration layer. Notion holds structured knowledge; Google holds in-flight collaborative docs.
    2. Notion as agent layer, Google as document factory. Notion runs the agents and synthesis; Google produces the actual docs that get sent.
    3. Drive integration as the bridge. Notion AI reads Google Drive content via integration so the agent can synthesize across both surfaces.

    What Gemini does that Notion AI doesn’t

    • Real-time multi-user editing with AI assistance
    • Sheets-native analysis and chart generation
    • Deep Gmail integration
    • Slides-native design and image generation

    What Notion AI does that Gemini doesn’t

    • Scheduled autonomous agents (Custom Agents)
    • Database property Autofill at the workspace level
    • Workers for code execution
    • The Notion-style structured knowledge graph
    • MCP-based tool integration

    Where comparisons go wrong

    1. Treating raw model quality as the deciding factor. Both use strong models. Integration depth matters more.
    2. Underestimating switching costs. Moving an org for AI reasons is rarely worth it.
    3. Trying to use both heavily. Context splits. Synthesis suffers.

    What to read next

    Notion AI vs ChatGPT, Notion AI vs Microsoft Copilot, Editorial Surface Area, Google Drive Integration.