Author: Will Tygart

  • Tacoma Sister Cities: How Diplomacy Drives Global Trade

    Tacoma Sister Cities: How Diplomacy Drives Global Trade


    When a delegation from South Africa’s Garden Route District Municipality touched down in Tacoma last April, they weren’t here for tourism. They were here to talk trade — specifically, how two port-anchored communities on opposite sides of the globe can build supply chains, share skills, and move goods between them.

    The April 23–28, 2026 exchange — part of a formal partnership between Tacoma Sister Cities International and the Garden Route District — is one of the clearest recent signals of how seriously Tacoma is beginning to use its 15 sister city relationships as genuine economic infrastructure rather than ceremonial diplomacy. And for Pierce County businesses paying attention, the implications are worth understanding.

    From Handshakes to Deal Flow: What the Garden Route Visit Actually Covered

    The Garden Route District Municipality spans South Africa’s Southern Cape, coordinating seven local municipalities and representing more than 630,000 residents. Its relationship with Tacoma traces back 28 years to a connection with the city of George — but in a move that quietly made international trade news, the Tacoma City Council formally elevated that relationship to a full district-wide partnership, substantially expanding the scope of what’s possible.

    The April delegation got specific. According to the Garden Route District Municipality’s official release, discussions centered on three concrete areas:

    The global ostrich industry. South Africa’s Garden Route — particularly the Klein Karoo region — is one of the world’s dominant ostrich product hubs, producing leather, feathers, and meat that move through international luxury and food supply chains. The delegation explored how the Port of Tacoma’s freight infrastructure could facilitate new export pathways for these high-value goods into Pacific Rim markets.

    Port logistics and trade facilitation. Both communities are defined by their port identities. The delegation examined how improved coordination between their respective port operations could reduce friction in bilateral trade flows — a practical, operator-level conversation, not a ceremonial one.

    Skills transfer and educational exchange. South Cape College and Africa Skills Village entered discussions about formal academic and artisanal exchange programs with Tacoma institutions, creating the kind of human-capital connections that tend to precede sustained economic relationships.

    Community reporting from South Africa’s The Gremlin described the visit’s tone as focused on “collective approaches to boost economic growth, skills transfer and sustainable tourism” — language that sounds like an investment thesis, not a cultural exchange brochure.

    WTC Tacoma: The Infrastructure Behind the Relationships

    None of this happens without an institutional engine. The World Trade Center Tacoma has quietly built itself into the largest membership-based trade organization in the Pacific Northwest, and by some measures the fastest-growing World Trade Center in North America over the past several years.

    WTC Tacoma’s core function is converting diplomatic relationships into actual commerce. It provides trade research, business matchmaking between local firms and international partners, import/export consulting, and manages both inbound and outbound trade missions. Critically, it also runs Tacoma’s foreign direct investment attraction programs — the effort to bring capital from abroad into Pierce County projects.

    The most visible example of that FDI work is the Tacoma-Fuzhou Trade Initiative, which grew out of Tacoma’s sister city relationship with Fuzhou, China — a city Xi Jinping led as Party Secretary when the original bond was formed in 1994. In 2019, Tacoma and Fuzhou simultaneously opened trade offices in each other’s cities, with the City and Port of Tacoma contributing $100,000 to fund the Fuzhou office. China remains the single largest trading partner of the Port of Tacoma.

    The 2026 WTC Globe Awards — scheduled for September 24 at Port of Tacoma Headquarters — will mark another year of recognizing the businesses and individuals driving this work. It’s worth attending if you want to understand who’s actually moving the needle on international trade in Pierce County.

    The Port Numbers That Explain the Strategy

    Tacoma’s sister city diplomacy doesn’t happen in a vacuum. It’s backed by real freight infrastructure that gives international partners a reason to engage seriously.

    The Northwest Seaport Alliance — which combines the ports of Tacoma and Seattle — handled nearly $76 billion in waterborne trade with 176 trading partners globally in 2024. Japan, South Korea, and Taiwan all rank among the top five trading partners. The port complex handles approximately 1.8 to 2 million TEUs of container throughput annually.

    In 2026, the story is mixed but mostly positive: NWSA breakbulk cargo volumes are up 24 percent year-over-year through April, driven by project cargo and heavy lift freight. Container volumes dipped in April amid broader trans-Pacific trade disruptions, but the port’s long-term Pacific Rim positioning remains intact.

    That infrastructure is the reason why a South African delegation talks seriously about using Tacoma as a Pacific access point. The port makes the pitch credible.

    The APCC Expansion and the Cultural Backbone of Trade

    Sustained trade relationships require cultural infrastructure, not just port capacity. In Tacoma, that infrastructure runs through the Asia Pacific Cultural Center, which has been working toward a significant expansion that would add a demonstration kitchen, cultural classrooms, an Asian Pacific Islander library, office and conference space, and a large exhibition hall.

    Federal funding has advanced through the House to support that expansion — Congressman Derek Kilmer’s office confirmed the appropriations movement — giving the APCC the resources to serve as a genuine anchor for Tacoma’s AAPI business community and its international connections.

    Tacoma is one of the most racially diverse cities in Washington State, with nearly 40 percent of residents identifying as Latino, African American, Asian and Pacific Islander, Multiracial, or Native American. That demographic reality is also an economic one: the region’s API-owned small businesses, workforce bilingualism, and cultural networks form a substrate that makes international business development more viable here than in many comparable mid-sized cities.

    What This Means for Pierce County Operators

    Here’s the practical read for local business owners and operators: Tacoma’s international infrastructure is more developed than most people realize, and it’s increasingly organized around generating actual deal flow rather than ribbon-cutting ceremonies.

    The sister city program — through Tacoma Sister Cities International — can connect businesses to counterpart organizations in 15 cities across multiple continents. WTC Tacoma’s membership provides access to trade consulting and matchmaking that most small businesses couldn’t afford to replicate independently. The Economic Development Board at choosetacomapierce.org maintains a dedicated international business support function.

    The April 2026 Garden Route visit is a useful model to study. It wasn’t an abstract diplomatic exchange — it was a structured conversation about specific products (ostrich goods), specific logistics (port connections), and specific human capital pathways (skills exchange programs). That’s what mature sister city relationships look like when they’re working. Pierce County’s international trade apparatus, at its best, operates the same way.

    The WTC Globe Awards in September will be the next public moment to see who’s driving this ecosystem. Between now and then, the Garden Route partnership will either produce tangible agreements or fade into the archives of well-intentioned visits. Based on how deliberately both sides have framed this one, the early signals favor the former.

    Frequently Asked Questions

    How many sister cities does Tacoma have?

    Tacoma currently maintains 15 official sister city relationships spanning Asia, Europe, Africa, Latin America, and the Pacific. Key partners include Fuzhou (China), Kitakyushu (Japan), Cheboksary (Russia), Cienfuegos (Cuba), and — most recently elevated — the Garden Route District Municipality in South Africa.

    What does the World Trade Center Tacoma do?

    The World Trade Center Tacoma (WTC Tacoma) is the largest membership-based trade organization in the Pacific Northwest. It provides trade research, business matchmaking, export/import consulting, and manages inbound and outbound trade missions. It also coordinates Tacoma’s foreign direct investment attraction programs, including the Tacoma-Fuzhou Trade Initiative with a sister office in Fuzhou, China.

    What was the purpose of the April 2026 Garden Route delegation to Tacoma?

    The Garden Route District Municipality delegation visited Tacoma April 23–28, 2026 to explore trade opportunities in the ostrich products industry, establish port logistics connections, and build skills exchange programs with local educational institutions. The visit built on the Tacoma City Council’s formal elevation of the city’s 28-year relationship with George, South Africa to a full district-wide partnership with the Garden Route municipality.

    Why is the Port of Tacoma important for Pacific Rim trade?

    The Port of Tacoma is one of the leading deep-water ports on the U.S. West Coast, handling over $25 billion in commerce annually as part of the Northwest Seaport Alliance. China, Japan, South Korea, and Taiwan rank among its top five trading partners. In 2026, NWSA breakbulk volumes are up 24 percent year-over-year, underscoring Tacoma’s growing role as a Pacific gateway for project cargo and specialized freight.

    How can Pierce County businesses get involved in international trade through Tacoma?

    Local businesses can engage through WTC Tacoma (wtcta.org), which offers trade consulting, matchmaking, and mission programming. The Economic Development Board for Tacoma-Pierce County (choosetacomapierce.org) also connects businesses to export resources and international investor networks. The annual WTC Globe Awards — scheduled for September 24, 2026 at Port of Tacoma HQ — is a key networking event for anyone engaged in the region’s international trade ecosystem.

  • Tacoma T Line Ridership Soars Amid TCC Extension Delays

    Tacoma T Line Ridership Soars Amid TCC Extension Delays

    Tacoma’s T Line at Two: Ridership Soars, But the Road to TCC Runs Through 2043

    Two and a half years after the Hilltop Tacoma Link Extension reshaped how Pierce County moves, the numbers are in — and they’re largely good news for local transit advocates. The T Line is beating Sound Transit’s own ridership projections, running at nearly perfect on-time performance, and drawing new riders who never had a reason to take the streetcar before. But the road ahead is complicated: the next major extension won’t arrive until the late 2030s at the earliest, Sound Transit is wrestling with a .5 billion funding gap across its ST3 program, and the promise of 10-minute service intervals remains unfulfilled.

    Here’s where Tacoma’s light rail network stands in 2026, what’s working, what isn’t, and what Pierce County residents can realistically expect over the next decade.

    Ridership Numbers: Better Than Billed

    When Sound Transit opened the Hilltop extension in September 2023, the agency projected the expanded T Line would carry between 2,000 and 4,000 daily passengers by 2026. That projection’s upper bound is now the floor.

    According to Sound Transit’s publicly available ridership data, the T Line averaged 3,618 daily boardings per month in 2024 and climbed to 4,079 average daily boardings in 2025. Monthly averages increased nearly 170% between 2023 and 2025 — a recovery story that Sound Transit acting service delivery director Benjamin Marx presented to the agency’s Rider Experience and Operations Committee in September 2025, per Mass Transit Magazine.

    Pandemic-era ridership had cratered the T Line to just 1,282 average daily boardings between 2020 and 2023. The line carried 3,658 daily boardings on average in 2019 — a benchmark it has now surpassed. The system also ran 99.5% of all scheduled trips through 2025 and received no more than six rider complaints in any single month since May 2024, according to Sound Transit spokesman David Jackson.

    “I think we’re pretty pleased with how ridership is going,” Jackson said. “Light rail, in general, has recovered pretty well from pandemic declines both in Seattle and Tacoma.”

    Which Stations Are Pulling Their Weight?

    The Tacoma Dome Station remains the T Line’s workhorse — clocking roughly 312,000 boardings since 2024 and serving as the critical hub connecting riders to Sounder commuter rail, Sound Transit Express buses to Seattle, and the broader Pierce Transit network. End-of-line terminus stations almost always top ridership charts, and Tacoma Dome is no exception.

    Among the new Hilltop Extension stations, Stadium District leads with more than 158,000 boardings through mid-2025 — driven largely by Stadium High School and proximity to the business district that suffered financially during construction. The St. Joseph Station (the western terminus) has accumulated more than 151,000 boardings, while the Hilltop District Station has seen nearly 122,000. The seven Hilltop Extension stations combined account for roughly 42% of all T Line boardings since 2024.

    Tacoma City Council member Kristina Walker, who also sits on the Sound Transit board, put it plainly: “No matter where they come into the system, that’s a person that’s not in a car or in our streets.”

    The Fare Factor and What It Funds

    The T Line was completely free to ride from 2003 through September 2023. That era ended with the Hilltop Extension. Today, fares are structured on the ORCA system: .00 for adults, .00 for ORCA LIFT cardholders, .00 for seniors and disabled riders, and free for youth.

    In 2024, fare revenues on the T Line totaled ,000 — a real number, but a modest fraction of the line’s roughly million annual operating costs. Through mid-2025, fares had brought in ,000. Sound Transit is not running the T Line on fare-box recovery; this is publicly subsidized service. ORCA LIFT exists specifically to ensure cost isn’t a barrier for low-income Pierce County residents.

    The 10-Minute Promise: Still Pending

    One commitment the Hilltop Extension made but hasn’t delivered: 10-minute train intervals. The T Line currently runs every 12 minutes during peak hours — a gap Sound Transit has attributed to right-of-way constraints and operator break scheduling.

    Sound Transit’s partial remedy: extended operating hours. The T Line now runs a 17-hour weekday service window, up from a 14-hour span. “This change in service yields significantly more weekday service on the T Line,” Jackson said. The agency maintains that future infrastructure improvements will eventually support 10-minute headways — but no firm timeline exists.

    Community feedback (a consistent signal in local forums and Pierce County transit discussions) reflects appreciation for the line’s reliability and expanded reach, while noting that frequency hasn’t yet matched the extension’s ambition.

    What’s Next: The TCC Extension and ST3 Funding Reality

    The next chapter of the T Line was supposed to be the TCC T Line Extension — six new stations stretching from the current St. Joseph terminus westward through the Hilltop corridor and out to Tacoma Community College. The extension would grow the T Line from 4.2 miles and 12 stations to 8.4 miles and 18 stations, connecting a campus of roughly 13,000 students to the regional transit grid.

    Sound Transit’s official target is a 2039 delivery date, funded under the voter-approved ST3 package. But that timeline is under real pressure.

    In March 2026, Sound Transit’s board convened to address a .5 billion funding shortfall across its entire ST3 program — driven by construction cost inflation, lower-than-expected tax revenues, and pandemic economic effects. The agency’s “Enterprise Initiative” is a comprehensive effort to deliver maximum ST3 benefits within available resources, with the board evaluating approaches to the updated ST3 System Plan through summer 2026.

    For Pierce County, the TCC T Line Extension and the Tacoma Dome Link Extension (TDLE) have remained on track through the restructuring process. But the TCC extension carries a reported million project affordability gap, and Jackson confirmed the board has begun “another reassessment process” due to “continuing financial headwinds.” Some independent analyses place realistic completion as late as 2043.

    The Tacoma Dome Link Extension: A Bigger Picture

    Separate from the T Line but critical to Pierce County’s transit future, the Tacoma Dome Link Extension would add approximately 8.5 miles of elevated light rail between Federal Way and Tacoma, extending the 1 Line south. Sound Transit’s board selected a preferred alignment alternative in June 2025 and is now advancing design work and fieldwork in preparation for the Final Environmental Impact Statement.

    When TDLE opens — likely in the 2030s — Tacoma Dome Station will transform into a full light rail interchange, connecting the 1 Line to the T Line and dramatically increasing transit catchment for both systems. That convergence is arguably the most consequential long-term transit development on Pierce County’s horizon.

    Pierce Transit’s Parallel Moves

    The T Line doesn’t operate in isolation. Pierce Transit implemented a notable service change in March 2026 that directly affects T Line connectivity. The agency extended its Stream Community Line — a bus rapid transit-style route serving the Highway 7 corridor between Tacoma and Spanaway — all the way to Commerce Street Station in downtown Tacoma. New stops include Pacific Avenue at 14th Street and 19th Street. The extension runs during weekday morning and evening peak hours.

    Pierce Transit also added frequency on Routes 1 and 3, two of its highest-ridership Tacoma corridors, with 8–10 new daily trips added to each route as part of its Bus System Recovery Plan.

    Transit-Oriented Development: Following the Rails

    Light rail extensions tend to reshape neighborhoods, and the Hilltop Extension is no exception. The Stadium District and Hilltop District station areas have seen increased multifamily residential interest since 2023. The Hilltop neighborhood — historically underserved by transit despite being geographically central — is now accessible by rail for the first time, connecting Hilltop residents to employment centers at Tacoma Dome and the downtown core.

    Tacoma Council member Jamika Scott, who represents Hilltop, flagged the need to protect businesses during any future construction phases. Stadium District businesses suffered significant foot-traffic losses during the Hilltop Extension’s five-year build. That lesson will need to shape how the TCC extension is managed when it eventually breaks ground.

    The Bottom Line for Pierce County Riders

    The T Line in 2026 is a genuine success story by the metrics that matter: ridership up, reliability near-perfect, new neighborhoods connected. The harder truth is that the next leap — reaching Tacoma Community College — is over a decade away under the optimistic scenario, and potentially longer if Sound Transit’s financial pressures force further schedule adjustments. The Tacoma Dome Link Extension will be transformative, but it’s a 2030s story at best.

    For Tacomans making transit decisions today, the T Line is worth using. It’s dependable, it covers the Hilltop and Stadium corridors well, and ORCA integrates it with the broader Puget Sound network. The bigger question — whether Pierce County will have the regional rail system its density and geography deserve — will be answered in Sound Transit boardrooms over the next few years, not on the tracks.

    Frequently Asked Questions

    How many people ride the T Line each day in 2026?

    The T Line averaged roughly 4,079 daily boardings per month through mid-2025, up from 3,618 in 2024. Sound Transit had projected 2,000–4,000 daily riders by 2026; the line now runs at or above the high end of that range.

    When did the Hilltop Tacoma Link Extension open?

    The Hilltop Tacoma Link Extension opened in September 2023. The million project added 2.4 miles and six new stations, growing the T Line from 1.8 miles to 4.2 miles with 12 stations total.

    Is the T Line still free to ride?

    No. The T Line introduced fares in September 2023. Adult fare is .00. Youth ride free. Seniors and disabled riders pay .00. ORCA LIFT cardholders pay .00.

    When will the T Line reach Tacoma Community College?

    Sound Transit’s current target is 2039, though financial headwinds put that date in question. Some analyses project 2043. The extension adds six stations and grows the T Line to 8.4 miles.

    How does the T Line connect to the broader Puget Sound transit network?

    The T Line’s terminus at Tacoma Dome Station connects to Sounder commuter rail, Sound Transit Express buses, and Pierce Transit routes. Pierce Transit’s Stream Community Line was extended in March 2026 to Commerce Street Station, improving downtown connections.

  • Belfair & Hood Canal Lodging: Where to Stay Guide

    Belfair & Hood Canal Lodging: Where to Stay Guide

    Belfair sits right at the head of Hood Canal, where the long fishhook of saltwater finally runs out of room and turns into the shallow, muddy, eagle-haunted flats of Lynch Cove. This is the top of the canal, not the Great Bend – that elbow is down at Union, a different stretch with a different crowd. Up here the water goes warm and skinny on a summer afternoon, the tide pulls way back over the oyster ground, and the towns stay small: Belfair on the highway, Allyn over on Case Inlet, Tahuya out the north shore, Grapeview tucked off on its own. It is working-forest, shellfish, and shipyard-commute country more than resort country, and the lodging follows suit.

    So set your expectations the right way. You will not find a row of brand-name hotels here. What you get instead is a handful of honest options: one practical in-town motel for a work trip or a quick overnight, a cluster of Washington State Parks and DNR campgrounds for tents, RVs, and a few cabins, a couple of small seasonal waterfront resorts and marinas, and a growing list of whole-house vacation rentals strung along the saltwater. This guide walks all of them, grouped so you can find your kind of stay fast, tells you who each place is really for and the best season to go, and then points you at the live booking pages and search tools so you are always looking at current rooms and rates – not a stale screenshot.

    One housekeeping note that locals care about: if you are coming for a Puget Sound Naval Shipyard interview or an early Bremerton ferry, Belfair is your friend. You sleep at small-town North Mason prices and you are a short, easy run north to the shipyard gates in the morning. More on that below.

    In-town motel: the practical overnight

    When you do not need a view – you need a clean bed, free parking at the door, and a short drive in the morning – this is the category. It is the room a local books for a cousin who is in town to work, not to vacation.

    Belfair Motel

    The Belfair Motel is the straightforward, in-town option: a locally run, single-story motel sitting right on SR-3 (Highway 3) as you roll through the middle of town. No water view, no resort frills – just clean, updated rooms with comfortable beds, refrigerators, and Keurig coffee makers, plus a well-lit lot and free parking. Think of it as the practical pick rather than the destination.

    It is built for people who need a reliable bed more than an experience – someone driving in for a shipyard interview, a one-night stopover, or a budget-minded base camp. It is pet friendly, which matters if the dog is along. From here you are minutes from the Theler Wetlands trails, the shops and food along Highway 3, and the head of Hood Canal at Lynch Cove, with Belfair State Park a short drive south. Best window is late spring through early fall, when the canal, the wetlands, and the parks are at their peak, but for a work stay this room does the job any month. Book direct for current rooms and rates: belfairmotel.com.

    State parks and public campgrounds

    The public land is the real anchor at this end of the canal. Two Washington State Parks sit on warm saltwater beaches, and the Tahuya State Forest behind town is laced with trails and DNR camps. These are campgrounds and day-use parks, not resorts – expect picnic shelters, busy summer weekends, and rules to follow – but they put you right on the water or right on the trail for very little money. Day-use at the state parks needs a Discover Pass; campsites and cabins book ahead, and summer weekends go fast, so reserve early.

    Belfair State Park (cabins and campground)

    This is the public anchor at the very head of Hood Canal, sitting on the Lynch Cove tide flats a few miles southwest of Belfair. It is a Washington State Park, which means a real campground – primitive, standard, and full-hookup sites – plus a handful of simple rentable cabins if you want a roof and a locking door instead of a tent. The draw is the saltwater: a long, shallow swimming and wading beach that warms up on a sunny afternoon, a spit and tide flats for beach walking, and seasonal clamming and oyster picking when the canal is open.

    It is built for families and weekend campers more than for anyone chasing quiet luxury – expect kids, picnic shelters, and a busy summer. The heated cabins lock up tight and stay open year-round, which also makes this an easy, cheap off-season base when the storms roll in. Best window is late spring through early fall for the beach, but always check the current shellfish season before you count on digging dinner. Reserve sites and cabins through the official Washington State Parks system.

    Twanoh State Park (campground)

    Twanoh is a Washington State Park, not a resort, so set expectations accordingly: this is a Civilian Conservation Corps-era day-use and camping park on the south shore of Hood Canal, about eight miles west of Belfair on Highway 106. It sits on one of the warmest saltwater beaches in the state, which is the whole point. Come for wading, swimming, and shellfishing; the tide flats here are a reliable spot to dig clams and gather oysters in season, license required and shuck-on-the-beach rules in force.

    The campground is modest and old-school, a mix of standard tent sites and full-hookup spots tucked under big timber, plus a couple of kitchen shelters for groups. Best window is mid-summer, when the water actually warms up and reservations open; spring and fall are quieter but cooler, and winter is first-come with limited water. A note worth checking before you load the car: this park has restoration work scheduled, so confirm current closures and dates through the official Washington State Parks system first.

    Tahuya River Horse Camp (DNR)

    This is a state-run horse camp, not a resort, tucked into the Tahuya State Forest west of Belfair off the Belfair-Tahuya Road. The Department of Natural Resources runs it for one job: getting riders and their stock onto the trails. Sites come with corrals, fire rings, picnic tables, and potable water, and they are sized to take a decent trailer, so it is built for people hauling horses rather than tent campers looking for a view.

    From here you can reach the Tahuya River Trail and tie into the wider network that threads this forest, which is the real draw. Note that the campground itself is non-motorized, so it suits horse folks and quiet trail users more than the ORV crowd. Sites are first-come, first-served and you will need a Discover Pass on the dash. Best window is late spring through early fall, when DNR opens drive-in access on weekends from Memorial Day to Labor Day. Check the official DNR Green Mountain-Tahuya page before you load up, since access and conditions shift by season.

    Waterfront resorts, marinas, and glamping

    These are the small, mostly seasonal places that put you on the water without renting a whole house. Think simple cottages and park models, RV rows, a boat launch and moorage, kayaks downstairs, or a stocked glamping tent at a trailhead. None of them are polished hotels, and that is exactly the appeal – they are unfussy basecamps for boaters, anglers, paddlers, and riders.

    Summertide Resort and Marina

    Drive the North Shore Road out of Belfair, hug the waterline for a while, and you land at Summertide Resort and Marina in Tahuya. This is a small, seasonal place right on Hood Canal, not a polished hotel, and that is the appeal. The lineup is straightforward: a handful of cottages and park models with full kitchens and water views, an RV row, tent sites, plus the working stuff that makes a canal trip easy – a boat launch, moorage, and a general store for the bag of ice you forgot.

    It suits families and small groups who want an unfussy base on the water, and it earns its keep with boaters and anglers who need a ramp, a slip, and a beach to set crab pots from. Come in summer, when the canal warms up for swimming and the shrimp and crab seasons draw people to this end of the water. Check current cottage and RV availability and book direct on their official site.

    Tahuya Adventure Resort

    This is a campground built for people who came to ride. Tucked into the heart of the Tahuya State Forest, a short hop up the north shore from Belfair, it sits right at the doorstep of the Tahuya off-road vehicle park and its big web of trails. You can pick your comfort level: stocked glamping tents with real beds and a stove if you want a roof and a soft landing, full-hookup pull-through sites for the RV, or plain tent sites if you are happy with a fire ring and the trees. A covered camp kitchen ties the place together for groups.

    The crowd skews ORV, dirt bike, mountain bike, and horse, and the trailhead access is the whole point – though Twanoh State Park and the canal shoreline are close enough for a swim or a fishing afternoon. Summer is prime for riding and water; spring and fall trade heat for quieter trails. Check current rates and dates on their booking page before you load the trailer: tahuyaresort.com.

    Allyn House Inn (and North Bay Kayaks)

    This is waterfront lodging in the small town of Allyn, set right on the North Bay of Case Inlet near the head of Hood Canal. It is not a resort and it is not a chain motel; it is a handful of self-contained, apartment-style units a short walk from the Allyn waterfront, the dock, and a cluster of local eateries. The draw is the same family running North Bay Kayaks downstairs, so you can roll out of bed, grab a rental or book a guided paddle, and be on the water in minutes.

    It suits couples and small families who want a quiet base on the saltwater without fussing with a big property, and paddlers who want lodging and boats in one stop. Nearby you have Allyn’s waterfront park, easy launches into the protected bay, and the back roads toward Grapeview and Tahuya. Late spring through early fall is the sweet spot, when the inlet calms down, shorebirds work the tide flats, and the paddling is at its best. Check current units and rates on their official site.

    Waterfront vacation homes (whole-house rentals)

    This is the category that has grown the most around Belfair: rent the whole place, get your own stretch of beach, spread out, and cook for the group. These are owner-run houses, not resorts with a front desk, so they range from a tidy three-bedroom cottage to a five-bedroom reunion house. The common thread is private shoreline at the quiet head of the canal – bring kayaks, watch for eagles, and plan your days around the tide. Listings change hands and rates shift, so always confirm on the live booking page.

    Sunrise Canal (waterfront cottage)

    Sunrise Canal is a single owner-run vacation cottage on Belfair’s north shore, sitting right on the saltwater up at the quiet head of Hood Canal. This is a whole-house rental, not a room or a resort – a remodeled three-bedroom place with its own beach access, a stocked kitchen, water views from the living space, and a fire pit out back for the evening. It suits families or a couple of households who want their own waterfront base rather than a hotel hallway, with enough room to spread out and a stretch of shoreline to call your own for the stay.

    You are close to the good stuff without being on top of it. Belfair State Park is about ten minutes off, the Theler Wetlands trails and the Lynch Cove boat launch are right around the corner, and groceries and a meal out are a short drive. Bring kayaks and watch for eagles off the patio. Late spring through early fall is the sweet spot – warmest water, calmest paddling, longest evenings. Check current rates and open dates on the owner’s site.

    Once Upon a Tide

    This is a single owner-run waterfront vacation home on Hood Canal’s North Shore, a few minutes west of Belfair near the head of the canal. It is a two-story Cape Cod-style house sitting on roughly 100 feet of low-bank pebble beach, with a wide deck built for watching the water and the far ridgeline. It rents as a whole house, not a room, so it suits a family or two couples who want the place to themselves rather than a resort with a front desk.

    The draw here is the beach itself: an oyster bed surfaces on a good low tide, you can pull a kayak or small boat right up on the gravel, and there is a public launch about a mile down the road for anything bigger. Summer is the obvious season, since this stretch of Hood Canal warms up enough to actually swim and the minus tides are best for oystering, though the quiet shoulder months reward anyone who just wants the deck and the view. Book direct through the owner via their listing page.

    Shoofly Creek Retreat

    Shoofly Creek Retreat is one of the larger waterfront houses on the Belfair end of Hood Canal, and it is built for a crowd. This is a single big vacation home, not a resort with a front desk, sleeping somewhere around fifteen across five bedrooms with its own stretch of beach and the namesake creek running down to the water. That makes it a reunion-and-wedding-party kind of place rather than a quiet couples getaway. You get the whole house, room to spread out, and kayaks to put in right off the lawn.

    You are at the very head of the canal here, close to Belfair State Park and the local beaches, with Tahuya and the north shore an easy drive for hiking and tide-pooling. Summer is the obvious draw for swimming, crabbing, and warm-water shellfish season. But come fall and you can watch salmon push up Shoofly Creek from the backyard, which is the quieter, more local reason to book. Check current rates and dates on the official listing.

    Plan your stay by season

    The head of Hood Canal reads completely differently depending on when you come. Here is how locals match the trip to the calendar, with a sample weekend for each.

    Summer: shellfish and a saltwater swim weekend

    This one is for the family that wants to fill a bucket at low tide and still get a real swim in before dinner. Belfair sits at the head of Hood Canal, where the water goes shallow and warm and the tide pulls way back over the flats. Mid-July through August is the sweet spot: longest daylight, warmest water, and the recreational shellfish season usually open. Come for two nights and plan around the tide chart. Base yourself on the water at Summertide Resort in Tahuya, or grab a waterfront campsite or cabin at Belfair State Park with the warm swimming lagoon right there.

    • Time the tide first. Dig and swim on a good low. Check the Lynch Cove tide predictions before you commit a day.
    • Clear the shellfish, every trip. Confirm the beach is open on the Washington Department of Health biotoxin map and check season and limits with WDFW. Closures change fast – bring boots and a license.
    • Fill the in-between hours. Walk the boardwalks at Theler Wetlands, drive out to Tahuya State Forest, or run up to Allyn for a burger and a look at Case Inlet.

    Spring through early fall: Tahuya dirt-and-trail weekend

    This is a get-dirty weekend, not a spa weekend. Tahuya State Forest sits just west of Belfair and is the engine room for ORV riders, mountain bikers, and horse folks across North Mason – roughly 84 miles of trail through working DNR forest. It is a working forest, so logging and washouts move the closure map around week to week. Best window is late spring through early fall, after the gates open (roughly mid-April through October 31) and before the mud sets in. Start at the Elfendahl Pass Staging Area, the main trailhead hub off Belfair-Tahuya Road.

    • Where to stay: the Tahuya River Horse Camp for equestrians with rigs, or Tahuya Adventure Resort for ATV-friendly basecamp lodging close to the trails.
    • Permits: you need both – a Discover Pass to park on DNR land, and an ORV tab and permit for motorized rigs. Confirm current rules at the DNR page.
    • Bring: a paper trail map, spare straps and a tow strap, first aid, bug spray, and water – cell service is patchy out there.
    • Cool down: Belfair State Park and the Theler Wetlands boardwalks on Lynch Cove, or a quiet evening up at Allyn on Case Inlet.

    Spring: birding and a paddle at the head of the canal

    Spring is the right time to point yourself at the head of Hood Canal. The Union River estuary at Belfair wakes up fast as the days lengthen, and Case Inlet lies down enough to put a boat in. Make it a slow weekend: birds in the morning, a paddle on a friendly tide, oysters and a porch by evening. Start at the Theler Wetlands at first light – the boardwalk runs out through restored salt marsh, and April through May is peak for herons, eagles, osprey, swallows, and warblers. For a base, the Allyn House Inn sits on the Case Inlet waterfront with the kayak shop run by the same folks.

    • Paddle: launch onto Case Inlet from Allyn on a rising or high tide; the south end goes to mud fast, so check the tide tables first. North Bay Kayaks rents and guides if you are not hauling your own.
    • Shellfish: beaches open and close on biotoxins – confirm before you dig on the Washington Shellfish Safety Map.
    • Day two: Tahuya State Forest is ten minutes out for trails and quiet lakes, and Belfair State Park has a tidal beach.

    Fall and winter: storm-watching and better rates

    The locals’ secret about the head of Hood Canal is that it gets better after the summer crowds leave. From roughly November through February, Lynch Cove turns moody and gorgeous: low gray light, southerlies pushing whitecaps up the canal, and lodging rates that finally make sense. This is a trip for people who like weather, not sunbathing. The heated cabins at Belfair State Park lock up tight and stay open year-round, which makes them an easy, cheap off-season base right on the saltwater. Ask for a site near the shore for the best storm seats.

    • Theler Wetlands: flat boardwalk through the estuary, great in a light rain when the birds move in.
    • Tahuya State Forest: gravel-road exploring and quiet trails just west when the canal turns rough.
    • Allyn: a short drive north for a hot meal and a look at the water from the other side.

    Year-round: the PSNS-interview one-night practical stay

    This is the no-fuss play for a work trip to the head of Hood Canal. You are interviewing at the shipyard, catching an early ferry out of Bremerton, or just need a clean room and a short drive in the morning. You are not chasing a waterfront view tonight; you want to sleep, get up, and go. Belfair sits right at the top of Lynch Cove, so you are close to Bremerton and PSNS while paying small-town Belfair prices instead of in-town Bremerton rates. Book the in-town Belfair Motel straight off their site – microwave, fridge, parking at the door, easy checkout.

    • Morning, if you have an hour: coffee and a short walk at the Theler Wetlands boardwalk or down at Belfair State Park on the tideflats. Check the Lynch Cove tide first – low tide is mud, not beach.
    • Heading out: Bremerton and the PSNS gates are a quick run north; confirm the live Washington State Ferries schedule before you commit to a sailing.
    • Want water instead: if the trip turns into an overnight worth a view, the waterfront rentals on Lynch Cove and toward Allyn are the upgrade. Save those for when you are not racing a 6 a.m. boat.

    More waterfront vacation rentals

    The houses above are the ones we know and can vouch for, but the short-term-rental inventory at the head of the canal churns constantly – places come on and off the market every season. Rather than mirror listings that go stale, here are live searches that always show what is actually open right now. Set your dates and party size and book direct with the host or platform.

    Frequently asked questions

    Is Belfair on the Great Bend of Hood Canal?

    No. Belfair sits at the head of Hood Canal, at the very top of the fishhook, where the saltwater shallows out into Lynch Cove. The Great Bend – the sharp elbow where the canal turns east – is down at Union, several miles to the southwest. People mix these up all the time. If you are reading about Belfair, Allyn, Tahuya, or Lynch Cove, you are at the head of the canal; the Great Bend and Union are their own stretch with their own lodging.

    Where should I stay near Belfair for a Puget Sound Naval Shipyard trip?

    For a work stay – a PSNS interview, a contractor rotation, or an early Bremerton ferry – the in-town Belfair Motel is the practical pick. It is a clean, pet-friendly roadside motel on Highway 3 with parking at the door, and from Belfair you are a short run north to the Bremerton and shipyard area while paying small-town prices. If your trip turns into an overnight worth a view, step up to one of the waterfront rentals on Lynch Cove or over toward Allyn.

    Can I camp right on the water near Belfair?

    Yes. Belfair State Park sits on the Lynch Cove tide flats with waterfront campsites and a few heated cabins, and Twanoh State Park, about eight miles west on Highway 106, sits on one of the warmest saltwater beaches in the state. Both are Washington State Parks – reserve ahead for summer weekends, bring a Discover Pass for day use, and check current closures before you go. For RVs and cottages on the canal, Summertide Resort and Marina out the north shore in Tahuya is the waterfront option.

    When is the best time to visit Belfair and the head of Hood Canal?

    Late spring through early fall is the all-around sweet spot: warmest water for swimming, calmest paddling, and the recreational shellfish season usually open (always confirm the beach is open before you dig). Mid-summer is peak for the warm-water beaches at Belfair and Twanoh. If you would rather have lower rates and dramatic weather, late fall and winter bring storm-watching on Lynch Cove and open, heated cabins at Belfair State Park.

  • Claude Code vs Codex CLI (2026): A Hands-On Head-to-Head

    Claude Code vs Codex CLI (2026): A Hands-On Head-to-Head

    Last verified: June 2026.

    Both Claude Code and OpenAI Codex CLI are terminal-native coding agents: you run them inside a repo, they read your files, edit code, run commands, and iterate. I run both daily on real projects. This is the head-to-head I wish existed when I was deciding which one to make my default. No benchmarks-chasing, just install commands, config files, pricing math, and where each one actually earns its keep. For the broader toolchain these slot into, see our AI operator’s stack.

    Claude Code vs Codex CLI: the short answer

    If you want one sentence: Claude Code is the more mature agentic harness (subagents, hooks, skills, deep MCP, a flat-rate plan that makes heavy use affordable), while Codex CLI is the leaner, cheaper-per-token option with strong raw coding from the GPT-5.x line and a tight sandbox model. Most teams that live in the terminal all day end up on Claude Code for the workflow tooling; people who want a fast, low-cost agent on top of an existing OpenAI subscription reach for Codex.

    The honest version: they are closer than tribal arguments suggest. The deciding factors are almost never “which model is smarter this week” and almost always pricing structure, sandbox defaults, and how much workflow scaffolding you need.

    How do you install each one?

    Claude Code installs from npm and runs as the claude command:

    npm install -g @anthropic-ai/claude-code
cd your-project
claude

    First run walks you through OAuth login (Pro/Max plan) or an ANTHROPIC_API_KEY. On Windows it runs natively in PowerShell now, though a lot of operators still prefer it under WSL for fewer path headaches.

    Codex CLI ships an install script and is also on npm:

    # Mac / Linux
curl -fsSL https://chatgpt.com/codex/install.sh | sh

# Windows (PowerShell)
powershell -ExecutionPolicy ByPass -c "irm https://chatgpt.com/codex/install.ps1 | iex"

# or via npm
npm install -g @openai/codex

    Then codex in your repo. Auth is either a ChatGPT login (Plus/Pro/Business) or an OpenAI API key via codex login. Both tools are open-source clients hitting hosted models, so the install is the easy part; the model access is what you are really buying.

    Which models do they run in 2026?

    Claude Code defaults to the current Claude flagship. As of June 2026 that is Opus 4.8 for the hardest reasoning, with Sonnet 4.6 as the fast everyday workhorse and Haiku 4.5 for cheap, high-volume calls. You switch in-session with /model. Opus 4.8 also exposes reasoning-effort levels (high is the default; xhigh and max push deeper on gnarly problems at higher token cost).

    Codex CLI runs the GPT-5.x coding line. GPT-5.5 is the current recommended default for complex coding and agentic work, GPT-5.4-mini is the faster/cheaper option for light tasks and subagents, and GPT-5.3-Codex remains a strong coding-tuned choice. Pick the model with codex -m gpt-5.5 or set it in your config.

    Practical read: on a clean, well-specified function both produce good code. The gap shows up on long, multi-file refactors where the agent has to hold a lot of context and recover from its own mistakes. That is a harness problem as much as a model problem, which is the next section.

    What about workflow features: subagents, hooks, and config?

    This is where Claude Code is currently ahead, and it is the real reason it tends to win for power users.

    • Subagents – Claude Code spawns isolated sub-sessions with their own context window, tool restrictions, and prompts. Great for “go research this in parallel while the main thread keeps coding.” Codex has a lighter subagent concept (often pointed at GPT-5.4-mini to keep cost down) but it is less fleshed out.
    • Hooks – Claude Code fires deterministic scripts at lifecycle points (PreToolUse, UserPromptSubmit, and more). These run real code, so they cannot hallucinate: you can hard-block a dangerous command, auto-format on every edit, or inject context before the model sees a prompt. Codex leans on its approval/sandbox policy and execpolicy rules instead of a general hook system.
    • Skills and slash commands – In Claude Code, custom slash commands have merged into skills; /your-command still works and skills add reusable, packaged capabilities. Codex uses prompt files and profiles rather than a skills layer.
    • Project memory – Both read a project instruction file. Claude Code uses CLAUDE.md; Codex uses AGENTS.md (checked in a fallback order including AGENTS.override.md and .agents.md). Keep these tight: architecture, conventions, and the few rules the agent keeps forgetting.

    Codex’s config story is clean if you like a single file: ~/.codex/config.toml holds your model, approval policy, sandbox mode, MCP servers, and named profiles you switch with codex --profile work. Claude Code spreads config across ~/.claude/ and .claude/settings.json plus per-project files, which is more surface area but more granular control.

    How do the sandbox and approval models compare?

    This matters more than most comparisons admit, because it governs how much the agent can do without asking.

    Codex CLI has an explicit, well-documented sandbox. Sandbox modes run from read-only to workspace-write (edit files in the project, network off by default) up to full access, paired with approval policies like untrusted and on-request. On Windows the native sandbox can run unelevated or elevated. The mental model is clear: pick how much rope, then approve escalations.

    Claude Code manages permissions through allow/deny rules and modes (including a plan mode that reasons without touching files, and an auto-accept mode for trusted loops). Combined with PreToolUse hooks you can build a strict policy, but it is more “assemble it yourself” than Codex’s preset sandbox tiers.

    If you are dropping an agent onto an unfamiliar or sensitive repo, start read-only in both. Codex makes that posture a one-flag default; Claude Code gives you finer-grained control once you invest in the config.

    Do both support MCP?

    Yes, and this is a genuine tie that matters. Both speak the Model Context Protocol, so you can wire in the same external tools, databases, and APIs. Codex registers STDIO or streaming-HTTP MCP servers in ~/.codex/config.toml and launches them at session start. Claude Code adds servers via claude mcp add or JSON config. If you have already built MCP integrations, neither tool locks you out. New to MCP, start with our Claude MCP setup guide and the Notion MCP setup walkthrough.

    What does each one cost?

    Pricing is where the decision often gets made, so here are the real numbers as of June 2026.

    Claude Code plans:

    • Pro – $20/mo: Sonnet 4.6 plus some Opus, roughly enough for focused daily sessions, not all-day heavy use.
    • Max 5x – $100/mo: much larger windows, real Opus headroom.
    • Max 20x – $200/mo: the heavy-user tier; effectively flat-rate firehose access.
    • API pay-as-you-go: Opus 4.7 about $5/$15 per million input/output… (current Opus tier runs higher), Sonnet 4.6 $3/$15, Haiku 4.5 $1/$5.

    Codex CLI: Included in ChatGPT Plus/Pro/Business plans (usage governed by your plan’s limits), or pay-as-you-go on the API. GPT-5.3-Codex runs about $1.75 per million input / $14 per million output, with cheaper input on cached tokens. The mini model is far cheaper for light work.

    The structural difference: Claude Code’s Max plans are flat-rate, which is why heavy users love them. People have tracked billions of tokens that would cost five figures on API metering but ran around a few hundred dollars on Max. Codex’s per-token rates are lower per unit and great if your usage is bursty or already bundled into a ChatGPT subscription, but a true all-day agent habit can run up metered cost faster than a flat plan. Estimate your monthly token volume honestly, then do the arithmetic both ways.

    So which coding agent should you actually use?

    Pick Claude Code if you want the deepest agentic workflow (subagents, hooks, skills), you are a heavy daily user who benefits from the flat-rate Max plan, or you need fine-grained, scriptable control over what the agent can do. It is the more complete operator’s harness in 2026.

    Pick Codex CLI if you want lower per-token cost, you already pay for ChatGPT and want to use that allowance, you like the clean preset sandbox/approval model, or you simply prefer the GPT-5.x output style. It is lean, fast to stand up, and genuinely capable.

    The move a lot of us make: run both. They are cheap relative to engineer time, they share MCP servers, and they have different failure modes. When one gets stuck in a loop on a hard bug, handing the same task to the other with fresh context often breaks the logjam. If you are weighing terminal agents against IDE-native ones, our Claude Code vs Cursor breakdown covers that axis.

    Frequently asked questions

    Is Claude Code or Codex CLI better for large refactors?

    Claude Code tends to hold up better on long multi-file refactors, mostly because of subagents and hooks that keep context organized and catch mistakes deterministically. Codex can do it too, especially with GPT-5.5, but you lean harder on tight AGENTS.md instructions and approval gates.

    Can I use Codex CLI without a ChatGPT subscription?

    Yes. Run codex login with an OpenAI API key and you pay per token instead of through a ChatGPT plan. Same for Claude Code with an ANTHROPIC_API_KEY if you would rather meter than subscribe.

    Do they work on Windows natively?

    Both do in 2026. Claude Code runs in PowerShell (many operators still prefer WSL for cleaner paths), and Codex CLI has a native Windows installer plus a Windows sandbox with unelevated/elevated modes. Watch out for shells that mangle /tmp or C:\ style paths in arguments.

    What is the single biggest difference?

    Pricing structure and workflow depth. Claude Code offers flat-rate Max plans and a richer harness (subagents, hooks, skills); Codex offers lower per-token rates and a cleaner preset sandbox. Model quality is close enough that those two factors usually decide it.

    Which model do they run by default?

    Claude Code defaults to the current Claude flagship (Opus 4.8 as of June 2026, with Sonnet 4.6 for everyday speed). Codex CLI recommends GPT-5.5 for complex work, with GPT-5.4-mini and GPT-5.3-Codex as alternatives. Switch in-session with /model or the -m flag.

    How do I get either tool cited or surfaced by AI engines for my own docs?

    That is a content question, not a tooling one. The same structure that makes this page answerable, short factual answers, question-shaped headers, and a visible FAQ, is what AI engines reward. See how AI engines cite content for the full playbook.

  • Claude Code vs Cursor: Which AI Editor Wins in 2026?

    Claude Code vs Cursor: Which AI Editor Wins in 2026?

    Last verified: June 2026.

    Claude Code and Cursor are the two tools most working developers actually reach for in 2026, and they are not the same kind of thing. Cursor is an AI-native code editor (a VS Code fork) where the model lives inside your IDE. Claude Code is a terminal agent that lives in your shell and edits files, runs commands, and drives git from the command line. I run both every day. This is the honest version: what each one is good at, what they cost right now, and a simple rule for picking.

    Claude Code vs Cursor: what is the actual difference?

    The short answer: Cursor is an editor you type in; Claude Code is an agent you delegate to. Cursor keeps you in the driver’s seat with autocomplete, inline edits, and a chat sidebar that sees your open files. Claude Code takes a goal (“add rate limiting to the upload endpoint and run the tests”) and works the repo autonomously in the terminal, asking permission before it touches things.

    Dimension Claude Code Cursor
    Form factor Terminal CLI (plus IDE extension, web, desktop) Full IDE (VS Code fork)
    Primary loop Delegate a task, approve actions Type code, accept suggestions
    Models Claude only (Sonnet 4.6, Opus 4.8) Multi-model: Claude, GPT, Gemini
    Best at Multi-file refactors, scripted/headless runs, git workflows Tight edit loops, autocomplete, staying in one window
    Entry price $20/mo (Pro) Free (Hobby) / $20/mo (Pro)
    Billing model Usage windows (5-hour + weekly) Credit pool ($ equal to plan price)

    How does each one actually work?

    Claude Code (terminal agent)

    You install it globally and run it from inside a project directory:

    npm install -g @anthropic-ai/claude-code
cd my-project
claude

    From there you talk to it in plain language. It reads files, proposes edits as diffs, and runs shell commands only after you approve them. A few patterns I use constantly:

    • Project memory: drop a CLAUDE.md file in the repo root with build commands, conventions, and “do not touch” rules. Claude Code reads it on every run, so you stop re-explaining the same context.
    • Headless / scripted runs: claude -p "bump all deps and run the test suite" runs one-shot and exits, which is what makes it scriptable in CI or cron jobs. This is the single biggest thing Cursor cannot do.
    • Permission control: by default it asks before edits and commands. You can pre-approve safe tools so it stops prompting on every npm test.
    • Plan mode: ask it to plan before it writes, review the plan, then let it execute. This is how you avoid a runaway agent rewriting half the codebase.

    Cursor (AI IDE)

    Cursor is a download, not a package install. You open your folder and the AI is wired into the editing surface:

    • Tab completion: multi-line, context-aware autocomplete that predicts your next edit, not just the next token. This is the feature people stay for.
    • Inline edit (Cmd/Ctrl+K): select code, describe the change, get a diff in place.
    • Agent mode: a chat panel that can edit multiple files and run terminal commands, closing the gap with Claude Code from inside the IDE.
    • Model picker: switch between Claude Sonnet, GPT, and Gemini per request from a dropdown. Useful when one model is stuck and you want a second opinion without leaving the window.

    What does Claude Code cost in 2026?

    Claude Code is billed by usage windows, not per-request credits. As of June 2026:

    • Pro: $20/month. Sonnet 4.6 and Opus 4.6, roughly 10 to 40 prompts per 5-hour window depending on repo size.
    • Max 5x: $100/month. ~5x Pro limits and access to Opus 4.8.
    • Max 20x: $200/month. ~20x Pro limits, all models including Opus 4.8.
    • API (pay-per-token): Opus 4.7 at $5 input / $25 output per million tokens; Sonnet 4.6 at $3 / $15.

    The mechanic to understand: there is a 5-hour rolling session window (your budget resets from your first prompt) plus a weekly active-compute cap that only counts time the model is actually reasoning. If you hit a wall mid-afternoon, you are usually waiting for the 5-hour window to roll, not the week.

    What does Cursor cost in 2026?

    Cursor moved to a credit-pool model (the switch happened in mid-2025). Every paid plan includes a monthly credit pool equal to the plan price in dollars, and each request burns credits based on which model you pick and how heavy the request is. As of June 2026:

    • Hobby: Free. Limited tab completions and agent requests, plus a one-week Pro trial on signup.
    • Pro: $20/month ($16 annual). Frontier model access, MCP support, cloud agents, and a $20 credit pool.
    • Pro+: $60/month. ~3x the credits.
    • Ultra: $200/month. ~20x usage and priority features.
    • Teams: $40/user/month with SSO and admin controls.

    Practical note on the credit pool: model choice matters a lot. Roughly, $20 of credits buys about 225 Claude Sonnet requests or about 550 Gemini requests, because Anthropic models cost more per call than Gemini in Cursor’s pricing. If you run Claude on everything, the $20 pool drains faster than newcomers expect. This is the source of most “what happened to Cursor pricing” confusion.

    Which models do you actually get?

    This is the cleanest dividing line.

    • Claude Code is Claude-only. You get Anthropic’s frontier coding models (Sonnet 4.6 for speed/cost, Opus 4.8 for the hardest agentic work on Max). No GPT, no Gemini. If you trust Claude for code, the single-vendor integration is tighter and the agent behavior is tuned end to end.
    • Cursor is multi-model. Claude, OpenAI, and Google models from one dropdown. The advantage is hedging: if one model whiffs on a problem, switch and retry in seconds. The trade-off is that no single model is integrated as deeply as Claude is in its own first-party tool.

    Which one is better for big refactors and automation?

    Claude Code, clearly. Two reasons. First, the terminal-agent loop is built for “go do this across the whole repo” tasks, and plan mode plus CLAUDE.md keep it on rails. Second, headless mode (claude -p "...") means you can wire it into scripts, pre-commit hooks, and scheduled jobs. Cursor’s agent mode is strong inside the IDE, but it is fundamentally an interactive editor, not a thing you call from a cron line.

    Which one is better for everyday coding flow?

    Cursor, for most people. If your day is reading, editing, and iterating on code you understand, Cursor’s tab completion and inline edits keep you in one window with near-zero friction. You never leave the editor to get help. Developers who are uneasy handing a whole task to an autonomous agent also tend to prefer Cursor because they stay in control of every keystroke.

    Can you use both together?

    Yes, and a lot of people do. The common setup: Cursor as the editor, Claude Code in Cursor’s integrated terminal. You get Cursor’s autocomplete and visual diff review for hands-on work, and you drop into Claude Code when you want to delegate a multi-file job or run something headless. They do not conflict. If you are building a broader operator setup around these tools, see our AI operator’s stack for how the pieces fit, and our Claude MCP setup guide for wiring external tools and data into Claude Code via MCP.

    Claude Code vs Cursor vs Codex?

    Codex is the third option people weigh, and it sits closer to Claude Code as an agent than to Cursor as an editor. The decision usually comes down to which model family and which workflow you trust. We break that specific matchup down in Claude Code vs Codex.

    Bottom line: when to pick which

    • Pick Claude Code if you want an autonomous agent for refactors, you live in the terminal and git, you need scriptable/headless runs, and you are happy with Claude as your one model.
    • Pick Cursor if you want best-in-class autocomplete, you prefer staying inside a visual editor, you value swapping between Claude/GPT/Gemini, and you want to keep your hands on the keyboard.
    • Pick both if you can swing two subscriptions: Cursor for the edit loop, Claude Code in the terminal for delegation. Start each on the $20 tier and only upgrade the one you hit limits on.

    FAQ

    Is Claude Code or Cursor cheaper?

    Both start at $20/month (Cursor also has a free Hobby tier). The difference is the meter: Claude Code limits you by 5-hour usage windows plus a weekly cap, while Cursor gives you a $20 credit pool that drains per request based on the model. Heavy Claude usage in Cursor burns the pool faster than people expect.

    Does Cursor use Claude?

    Yes. Cursor offers Anthropic’s Claude models alongside OpenAI and Google models, selectable per request. But you are using Claude through Cursor’s integration, not Anthropic’s first-party Claude Code agent, so the agentic behavior differs.

    Can Claude Code edit files and run commands like an IDE agent?

    Yes. Claude Code reads and writes files, runs shell commands, and drives git directly from the terminal. By default it asks permission before edits and commands, and you can pre-approve safe tools to cut down the prompts.

    Which is better for beginners?

    Cursor. The visual editor, inline diffs, and autocomplete are more forgiving than a terminal agent, and the free Hobby tier lets you learn before paying. Claude Code rewards people who are already comfortable in the shell and with git.

    Do I need to know the command line to use Claude Code?

    Largely yes. Claude Code is a CLI-first tool, and while it does most of the git and shell work for you, you will be living in a terminal. There is also an IDE extension and a desktop app, but the terminal is where it is strongest.

    Can I run Claude Code in CI or on a schedule?

    Yes, via headless mode: claude -p "your task" runs once and exits, which makes it usable in CI pipelines, git hooks, and scheduled jobs. Cursor has no equivalent because it is an interactive editor.

    Will using both at once cause conflicts?

    No. A common and stable setup is Cursor as your editor with Claude Code running in Cursor’s integrated terminal. They operate on the same files without stepping on each other, as long as you are not having both edit the exact same file simultaneously.

    Related reading: how AI engines cite content and Claude in Chrome for LinkedIn automation.

  • How AI Engines Actually Cite Your Content: Grounding and GEO Guide

    How AI Engines Actually Cite Your Content: Grounding and GEO Guide

    Last verified: June 2026.

    Most “GEO” advice is recycled SEO with the word “AI” pasted on top. This guide is different. It describes what actually happens when Microsoft Copilot, Bing’s AI answers, and Google’s AI Overviews build a response and decide whose page to cite — based on running content sites that get cited tens of thousands of times a month. The short version: AI engines do not cite the page that ranks #1 for a head term. They cite the page that most directly answers the specific sub-question the model is grounding on. That distinction changes everything about what you should write.

    How grounding actually works (the part nobody explains)

    When you ask Copilot or Bing’s AI a question, the model does not answer from memory. It runs a retrieval step called grounding: it rewrites your question into one or more search queries, fetches a handful of live web results, reads them, and composes an answer with inline citations pointing back at the pages it used. Google’s AI Overviews work the same way with a technique it calls “query fan-out” — one user question becomes many narrower synthetic queries.

    Two things follow directly from this mechanism:

    • The model is not searching for your keyword. It is searching for the answer to a decomposed sub-question. A user who asks “what’s the best way to instantly index a new page” triggers grounding queries like “IndexNow API endpoint”, “submit URL to Bing programmatically”, and “IndexNow key file location”. The page that wins is the one that answers those narrow strings, not the one optimized for “indexing tips”.
    • Citations are extracted at the passage level, not the page level. The model lifts the specific sentence or table that answers the sub-question. If your answer is buried under 600 words of preamble, it loses to a page that states the fact in the first line under a matching heading.

    This is why a niche, specific page routinely out-cites a high-authority generalist. The generalist ranks; the specialist gets quoted.

    Why operational and comparison pages win over head terms

    Across real citation data, the pages that get pulled into AI answers cluster into three shapes. None of them are “ultimate guide to X”.

    1. Operational pages with real commands, configs, and error messages

    When someone asks an AI assistant “how do I fix [specific error]” or “what’s the exact command to do X”, the model needs a page that contains the literal command, the literal config, or the literal error string. Generic advice cannot be cited because there is nothing concrete to quote. A page that says:

    curl "https://www.bing.com/indexnow?url=https://example.com/new-page/&key=YOUR_KEY"
# 200 = received (not "indexed"), 422 = URL/key mismatch, 429 = too many submits

    …is citation gold, because the model can extract that block verbatim and the user can act on it. The error-code annotations matter: questions about failures (“IndexNow 422”, “why am I getting 429”) are high-intent and low-competition, and a page that names the exact codes owns them.

    2. Comparison pages (“X vs Y”)

    “Which is better, X or Y” is one of the most common shapes of AI query, and comparison content is structurally easy to cite because it maps cleanly to a decision. If you maintain honest, current head-to-head pages, you become the default source the model reaches for when a user is choosing between tools. This is exactly why we keep dedicated comparison pages like Claude Code vs Cursor and Claude Code vs Codex — they answer a decision the model is constantly being asked to make, and a table of differences is trivially quotable.

    3. Fresh, dated pages on fast-moving topics

    For anything that changes — pricing, model versions, API limits, feature availability — grounding strongly favors recency. The model would rather cite a page dated this month than an “authoritative” page from two years ago that might be wrong. A visible “Last verified” date and a real publish/update timestamp are not decoration; they are a relevance signal the retrieval layer reads.

    The losing move is chasing broad head terms. “Best AI coding assistant” is saturated, generic, and rarely the literal grounding query. The winning move is to own the long, specific, operational and comparison strings that the fan-out actually generates.

    IndexNow: how to get cited the same day you publish

    Grounding can only cite pages the engine knows about. The bottleneck for new content is crawl latency — and IndexNow collapses it. IndexNow is an open protocol (backed by Microsoft Bing and Yandex) that lets you push a URL to the index the instant you publish, instead of waiting for a crawler to wander by.

    Setup is two steps:

    1. Host a key file. Generate a key of 8-128 hex characters and place it at your site root as a UTF-8 text file named {key}.txt containing exactly that key. Example: https://example.com/daa44a2c....txt. This proves you own the host.
    2. Ping on publish. Single URL via GET: 
      curl "https://api.indexnow.org/indexnow?url=https://example.com/new-page/&key=YOUR_KEY"

      Or batch up to 10,000 URLs in one POST:

      curl -X POST "https://api.indexnow.org/indexnow" \
  -H "Content-Type: application/json" \
  -d '{"host":"example.com","key":"YOUR_KEY","urlList":["https://example.com/a/","https://example.com/b/"]}'

    A 200 means the endpoint received your URL (not that it is indexed yet). Submitting to api.indexnow.org shares the ping with all participating engines, so you do not need to hit Bing and Yandex separately. Most WordPress SEO plugins (Rank Math, Yoast, SEOPress) have IndexNow built in — turn it on and it fires automatically on every publish and update. The practical payoff: pages can enter Bing’s crawl queue within hours, which means they are eligible to be grounded and cited the same day, not next week.

    One caveat worth stating plainly: IndexNow accelerates indexing, which is a precondition for citation. It does not force a citation. You still need the page to be the best answer to the sub-question. But for fresh, time-sensitive content, same-day indexing is often the difference between getting cited while the topic is hot and showing up after the conversation has moved on.

    How to actually measure your AI citations

    For a long time AI citations were invisible — you could see referral clicks in analytics but not the citations themselves (most AI answers are zero-click). That changed. As of February 2026, Bing Webmaster Tools ships an AI Performance report (public preview) that shows when your pages are cited across Microsoft Copilot, Bing’s AI answers, and partner surfaces. It is the first direct, free window into AI citation behavior, and you should be reading it weekly.

    The four metrics that matter:

    • Total citations — how many times your site was cited as a source in AI answers over the period.
    • Average cited pages — the daily average count of unique URLs from your site that got referenced. This tells you whether citations are concentrated on one page or spread across the site.
    • Grounding queries — sample query phrases the AI used to retrieve and cite you. This is the single most actionable field in the report. It is a literal list of the sub-questions you are winning, which tells you exactly which operational/comparison angles to expand next.
    • Page-level citation activity — citations by URL, so you can see which pages are doing the work.

    Two limitations to keep in mind so you read the data honestly: the report does not show click data (you see citations, not visits from them), and it aggregates Copilot with Bing summaries, so you cannot isolate one surface from the other. For Google’s AI Overviews there is still no equivalent citation dashboard — the closest proxy is watching impressions and referral patterns in GA4 and Search Console, plus spot-checking your target queries by hand.

    The workflow that works: pull the grounding-queries list, find the patterns, and feed them straight back into your content plan. If you are getting cited for “claude mcp setup” variants, that is a signal to deepen pages like the Claude MCP setup guide and adjacent operational walkthroughs, not to chase a new head term.

    A repeatable checklist for citation-optimized pages

    Everything above reduces to a build pattern. For any page you want AI engines to cite:

    • Lead with the answer. Put a short, factual, quotable answer in the first 1-2 sentences under each heading. Assume the model reads only that passage.
    • Use question-shaped headings. H2s and H3s that mirror real queries (“How does IndexNow work?”, “How do I measure AI citations?”) match the grounding query and give the extractor a clean anchor.
    • Be specific and operational. Real commands, real config, real numbers, real error codes and fixes. Concrete text is extractable; vague advice is not.
    • Add a visible FAQ near the end. Plain question/answer pairs are the single most citation-friendly format, because each pair is a self-contained answer to a discrete sub-question. You do not need JSON-LD schema for this to work — visible Q&A text is what the model reads.
    • Date it and keep it current. A “Last verified” line plus genuine updates on fast-moving topics buys you the recency edge in grounding.
    • Push it with IndexNow so it is indexable the same day, then watch the AI Performance report to see which sub-questions it wins.

    If you want the larger system this fits into — the full toolchain for operating as an AI-first publisher, from MCP servers to publishing pipelines — start with the AI operator’s stack.

    FAQ

    Do AI engines cite the page that ranks #1 on Google?

    Not reliably. AI engines run their own grounding retrieval and cite the page that most directly answers the specific decomposed sub-question, which is often a niche, operational page rather than the head-term winner. Ranking helps your page be discoverable, but the citation goes to whichever passage best answers the exact grounding query.

    What is grounding in AI search?

    Grounding is the retrieval step where an AI assistant rewrites your question into search queries, fetches live web pages, reads them, and builds an answer with inline citations to those pages. It is why current, specific pages can get cited even by a model whose training data predates them.

    Does IndexNow guarantee my page will be cited by AI?

    No. IndexNow guarantees fast indexing, which is a precondition for being cited. The page still has to be the best, most specific answer to the sub-question the model is grounding on. Think of IndexNow as removing the crawl-latency excuse, not as buying a citation.

    How do I measure how often AI cites my site?

    Use the AI Performance report in Bing Webmaster Tools (public preview since February 2026). It shows total citations, average cited pages per day, sample grounding queries, and citation counts by URL across Microsoft Copilot and Bing AI answers. It does not yet show click-through from those citations, and there is no equivalent dashboard for Google AI Overviews.

    Do I need JSON-LD or schema markup to get cited?

    No. Citation extraction works on visible, well-structured text — question-shaped headings, short factual answers, and a plain visible FAQ. Schema can help search features generally, but it is not required for AI grounding to read and quote your page.

    What kind of pages get cited most?

    Three shapes dominate: operational pages with real commands, configs, and error fixes; comparison pages that resolve a “X vs Y” decision; and fresh, dated pages on fast-moving topics like pricing and model versions. Broad head-term content tends to get skipped because it rarely matches the literal grounding query and offers nothing concrete to quote.

  • Notion MCP Setup with Claude: Complete Config + the Errors Nobody Documents

    Notion MCP Setup with Claude: Complete Config + the Errors Nobody Documents

    Last verified: June 2026.

    There are two ways to connect Notion to Claude over the Model Context Protocol (MCP), and almost every tutorial only covers one of them. Worse, none of them tell you why the connection succeeds but Claude still says it cannot find any of your pages. This guide covers both paths – the hosted OAuth connector and the self-hosted token route – with the exact config, the scopes that matter, the rate limit you will hit, and the specific error strings that show up when something is wrong. It is written from actually running this, not from reading the docs.

    Which Notion MCP should you use: hosted or self-hosted?

    Short answer: use the hosted MCP at https://mcp.notion.com/mcp for almost everything. It uses OAuth, so you never handle a token, and it respects your existing Notion permissions automatically. Use the self-hosted npm server with an internal integration token only when you need headless, unattended automation (a cron job, a server with no human to click “Allow”), because the hosted server requires an interactive OAuth approval that a background process cannot complete.

    Factor Hosted (mcp.notion.com) Self-hosted (npm + token)
    Auth OAuth (interactive) Internal integration token (ntn_)
    Permissions Inherits your full Notion access Only pages you explicitly share
    Setup time ~2 minutes ~10 minutes
    Headless / cron No (needs a human to approve) Yes
    Best for Claude Desktop, Claude Code, daily use Servers, scripts, multi-user backends

    How do I connect Notion to Claude using the hosted MCP?

    This is the fast path. No token, no npm.

    Claude Desktop / Claude.ai: Open Settings > Connectors, click Add custom connector (or pick Notion if it appears in the directory), and paste the URL https://mcp.notion.com/mcp. A Notion OAuth window opens. Approve it, choose which workspace and which top-level pages the connector may see, and you are done. The scope you pick in that OAuth screen is the whole ballgame – see the gotcha below.

    Claude Code (CLI): one command.

    claude mcp add --transport http notion https://mcp.notion.com/mcp

    Then run /mcp inside Claude Code to trigger the OAuth login. After approving, verify it is live:

    claude mcp list

    You should see notion with a connected status. If it shows failed or needs auth, run /mcp again and complete the browser flow – the CLI cannot proceed past OAuth on its own.

    How do I set up the self-hosted Notion MCP with an integration token?

    Use this when you need automation that runs without a human. Three steps: create the integration, get the token, then wire it into your MCP config.

    1. Create the integration and copy the token

    1. Go to https://www.notion.so/my-integrations and click New integration. You must be a Workspace Owner – if the button is greyed out, that is why.
    2. Name it, select the workspace, and choose Internal integration type.
    3. On the integration’s settings page, set Capabilities: Read content, plus Update/Insert content if you want Claude to write. If you only grant Read, every write attempt fails with a permission error later – this is a common self-inflicted wound.
    4. Click Show, then copy the Internal Integration Token. New tokens start with ntn_ (older ones start with secret_ and still work). Treat it like a password.

    2. Add it to your MCP config

    For Claude Desktop, edit claude_desktop_config.json (macOS: ~/Library/Application Support/Claude/; Windows: %APPDATA%\Claude\). Add:

    {
  "mcpServers": {
    "notion": {
      "command": "npx",
      "args": ["-y", "@notionhq/notion-mcp-server"],
      "env": {
        "NOTION_TOKEN": "ntn_your_token_here"
      }
    }
  }
}

    Restart Claude Desktop completely (quit, do not just close the window). On Windows, if npx is not found, use the full path to npx.cmd or run via cmd /c – the config does not inherit your shell PATH.

    3. The step everyone forgets: share the pages

    An internal integration starts with access to nothing. Creating it and pasting the token is not enough. For every page or database you want Claude to touch, open it in Notion, click the … menu (top right), choose Connections (or Add connections), and select your integration. Access is inherited by child pages, so sharing a top-level page covers its whole subtree. Skip this and Claude will connect cleanly and then truthfully report that it cannot see any content.

    What are the most common Notion MCP errors and how do I fix them?

    These are the failure messages you will actually see, and what each one means.

    “Could not find page” / Claude returns zero results from a workspace that clearly has pages

    Cause, in order of likelihood: (1) you did not share the page with the integration (self-hosted), or you scoped the OAuth grant too narrowly (hosted); (2) the page is in a different workspace than the one the integration is tied to. Fix: re-check the Connections menu on the specific page, or re-run the OAuth flow and widen the page selection. An integration token is bound to one workspace – it cannot see another.

    API token is invalid (HTTP 401 unauthorized)

    The token is wrong, was regenerated, or has a stray space/newline from copy-paste. Re-copy it with the Show button, paste it into the env block with no surrounding whitespace, and restart the client. If you rotated the token in Notion, the old one dies immediately – update every config that used it.

    Validation error / “body failed validation” (HTTP 400)

    Claude tried to write a property type that does not match the database schema – for example sending plain text into a Select, or a malformed date. This is not a connection problem. Tell Claude the exact property names and types, or ask it to fetch the database schema first before writing.

    “Rate limited” / HTTP 429

    Notion enforces roughly 3 requests per second per integration (averaged, with short bursts tolerated). Bulk operations – “update 200 rows,” “scan every page” – blow straight through this. The fix is pacing, not a bigger plan: have Claude batch in small groups and add a short delay between calls. If you are scripting around the MCP, honor the Retry-After header on a 429 instead of hammering.

    spawn npx ENOENT (server will not start, self-hosted)

    Node/npx is not on the PATH the client sees. Install Node, then point command at the absolute path to npx (or npx.cmd on Windows). This is the number-one self-hosted startup failure.

    MCP server shows “failed” in claude mcp list right after adding it

    For the hosted server this almost always means OAuth was never completed – run /mcp and approve in the browser. For the self-hosted server it means the process crashed on launch; run the npx command manually in a terminal to see the real stack trace.

    What can Claude actually do with Notion once connected?

    With read + write capabilities granted, Claude can search your workspace, read pages and databases, create pages, append blocks, and update properties on existing rows. Practical things that work well: “summarize this Notion doc,” “create a row in my tasks database with these fields,” “find every page mentioning X and list the links,” “turn this conversation into a meeting-notes page.” Things that get awkward: very large pages (the response can get truncated – verify the write actually landed by fetching it back), and bulk edits that trip the rate limit. A reliable habit is to treat Notion as the source of truth and have Claude verify by re-fetching after any write, because timeouts on big pages can commit silently and still return a malformed response.

    Security notes from running this in production

    • Scope the OAuth grant tightly. The hosted connector inherits whatever you approve. If you only need one project area, share only that top-level page, not the whole workspace.
    • Never hardcode the token in a file you might commit. Keep ntn_ tokens in an env var or your OS secret store, and reference them from config. If a token leaks, revoke it in my-integrations immediately – revocation is instant.
    • Grant the minimum capability. If Claude only needs to read, do not enable insert/update. You can always widen it later.
    • Audit which integrations have access to sensitive databases periodically; the Connections menu on each page shows the current list.

    If you are wiring up several connectors at once, the mechanics generalize – see our broader Claude MCP setup guide for the config patterns that apply across servers, and the AI operator’s stack for how Notion fits alongside the other tools day to day. If your reason for connecting Notion is to get your own content cited by AI systems, the structure of the pages matters as much as the wiring – see how AI engines cite content.

    FAQ

    Do I need a paid Notion plan to use the MCP?

    No. The API and integrations work on free Notion workspaces. You do need to be a Workspace Owner to create an internal integration.

    Why does Claude say it connected but can’t find my pages?

    Almost always the page-sharing step. A self-hosted integration has access to nothing until you add it via the page’s Connections menu. For the hosted connector, you scoped the OAuth approval too narrowly – re-run it and select more pages.

    What is the Notion API rate limit?

    About 3 requests per second per integration, averaged over time with small bursts allowed. Exceeding it returns HTTP 429. Pace bulk operations and respect the Retry-After header.

    What does the ntn_ prefix mean on my token?

    It is the current internal integration token format. Tokens created today start with ntn_; older secret_ tokens still function and do not need to be replaced.

    Can the hosted Notion MCP run in a headless cron job?

    No. The hosted server requires interactive OAuth approval, which an unattended process cannot complete. Use the self-hosted npm server with an ntn_ token for headless automation.

    How do I let Claude write to Notion, not just read?

    Enable Update content and Insert content under the integration’s Capabilities (self-hosted), or approve write scope during OAuth (hosted). Read-only is the default and will reject every write with a permission error.

    Where do I put the Notion MCP config for Claude Desktop?

    In claude_desktop_config.json – ~/Library/Application Support/Claude/ on macOS, %APPDATA%\Claude\ on Windows. Add a notion entry under mcpServers and fully restart the app.

    Can one integration access two workspaces?

    No. An internal integration is bound to the single workspace it was created in. For a second workspace, create a second integration (or a second OAuth grant on the hosted connector).

    Related reading from operators who run AI tooling daily: Claude Code vs Cursor, Claude Code vs Codex, and Claude in Chrome for LinkedIn automation.

    Frequently Asked Questions

    What is the Notion MCP server for Claude?

    The Notion MCP server is a connector that lets Claude read, search, and interact with your Notion workspace through the Model Context Protocol. With it connected, you can ask Claude to find pages, summarize databases, draft content into Notion, or retrieve information — all without copying and pasting anything manually.

    What is the difference between the Notion OAuth connector and the self-hosted token route?

    The OAuth connector (available in Claude Desktop’s built-in integrations) is the fastest path — authorize once and Claude gets read access to pages you share with the integration. The self-hosted route uses a Notion Internal Integration token in your claude_desktop_config.json, giving you more control over scopes and works in Claude Code environments where OAuth connectors aren’t available.

    Why does Claude say it can’t find my Notion pages after connecting?

    The most common reason is that you haven’t shared the specific pages or databases with your Notion integration. Notion’s permission model requires explicit page-level grants — a successful connection does not automatically give access to all your content. Go to the page in Notion, click the three-dot menu, choose ‘Add connections’, and select your integration.

    What scopes does the Notion MCP integration need?

    For read operations: Read content and Read user information. For write operations: Update content and Insert content. Avoid requesting more scopes than you need — the minimum set reduces the blast radius if a token is ever compromised. Set scopes when creating your Notion Internal Integration at notion.so/my-integrations.

    Does the Notion MCP integration work with Claude Code?

    Yes. Add it via ‘claude mcp add notion npx @notionhq/notion-mcp-server’ and set your NOTION_API_KEY as an environment variable. Claude Code picks it up on the next session. The self-hosted token route works in both Claude Desktop and Claude Code; the OAuth connector is currently Desktop-only.

    What rate limits does the Notion API have?

    Notion’s API enforces a rate limit of 3 requests per second per integration. For typical conversational use this is invisible, but if you ask Claude to crawl a large database or process many pages in sequence, you may see 429 errors. The fix is to add a short sleep between bulk operations or use Notion’s pagination to fetch in smaller batches.

    📖 Related Claude Guides


  • How to Connect Any Tool to Claude with MCP: Complete Setup Guide

    How to Connect Any Tool to Claude with MCP: Complete Setup Guide

    Last verified: June 2026

    MCP (Model Context Protocol) is how you give Claude hands. Out of the box Claude can talk; with an MCP server connected, it can read your files, query a database, hit an API, or drive a browser. This guide covers the two places you actually wire servers up: the claude_desktop_config.json file for the Claude Desktop app, and the claude mcp add command for Claude Code (the terminal/IDE tool). It ends with the troubleshooting section the official docs skip: path problems, JSON syntax traps, servers that silently never load, and the Windows quirks that cost people an afternoon.

    Everything below is checked against the current Claude Code MCP docs and tested commands. If you want the wider picture of how MCP fits into a working setup, see the AI operator’s stack.

    What is MCP and what is an MCP server?

    MCP transport options at a glance

    Transport Use case Config location Works with
    stdio Local tools, CLIs, scripts claude_desktop_config.json or claude mcp add Claude Desktop, Claude Code
    SSE (HTTP) Remote servers, cloud services URL in config Claude Desktop, Claude Code
    Streamable HTTP Production remote MCP URL in config Claude Desktop, Claude Code

    MCP is an open standard for connecting AI models to external tools and data. An MCP server is a small program that exposes a set of tools (functions Claude can call) over that protocol. Claude is the client; the server is the thing that actually does the work, like reading a Postgres table or creating a GitHub issue.

    There are two transport types you will deal with in practice:

    • stdio (local): the server runs as a process on your machine. Claude talks to it over standard input/output. Best for filesystem access, local databases, and custom scripts. This is what most “install this MCP server” instructions mean.
    • HTTP (remote): the server lives on the internet at a URL. Best for cloud services (Notion, Sentry, Stripe, GitHub). Often uses OAuth. SSE is the older remote transport and is now deprecated; use HTTP for new remote servers.

    The same server can usually be added to both Claude Desktop and Claude Code. The mechanics differ: Desktop uses a JSON file you edit by hand, Claude Code gives you a CLI that writes the config for you.

    How do I add an MCP server to Claude Desktop?

    Claude Desktop reads a single JSON file. You edit it, fully quit the app, and reopen. There is no in-app “add server” button for custom servers as of June 2026, so the file is the source of truth.

    Where is claude_desktop_config.json?

    • macOS: ~/Library/Application Support/Claude/claude_desktop_config.json
    • Windows: %APPDATA%\Claude\claude_desktop_config.json (paste that into the File Explorer address bar; it expands to C:\Users\YOU\AppData\Roaming\Claude\)

    The fastest way to open it: in Claude Desktop go to Settings > Developer > Edit Config. That button creates the file if it does not exist and opens the folder. If the file is brand new it may be empty or just {}.

    The config file structure

    Everything lives under a top-level mcpServers object. Each key is a name you choose; each value describes how to launch the server. Here is a complete, working file with a local filesystem server and a remote Notion server:

    {
  "mcpServers": {
    "filesystem": {
      "command": "npx",
      "args": [
        "-y",
        "@modelcontextprotocol/server-filesystem",
        "C:\\Users\\YOU\\Documents"
      ]
    },
    "notion": {
      "command": "npx",
      "args": ["-y", "@notionhq/notion-mcp-server"],
      "env": {
        "NOTION_TOKEN": "secret_your_token_here"
      }
    }
  }
}

    Three fields do all the work:

    • command the executable to run (npx, node, python, uvx, or an absolute path to a binary).
    • args an array of arguments. Each flag and value is its own array element. "--port 8080" as a single string will not work; use "--port", "8080".
    • env an object of environment variables (API keys, tokens). Optional.

    After saving, completely quit Claude Desktop (on Windows, right-click the system tray icon and choose Quit; closing the window is not enough) and reopen it. You should see a tools/connector indicator in the chat input. For a full Notion walkthrough including the token, see connecting Notion to Claude with MCP.

    How do I add an MCP server to Claude Code (CLI)?

    Claude Code does not make you hand-edit JSON. The claude mcp command manages servers for you and writes to the right file. This is the part people get wrong most often, so here is the exact, verified syntax.

    claude mcp add

    The general form for a local (stdio) server is:

    claude mcp add [options] <name> -- <command> [args...]

    The -- is load-bearing. Everything before it is for Claude Code; everything after it is the command that launches your server. Real examples:

    # Local filesystem server
claude mcp add filesystem -- npx -y @modelcontextprotocol/server-filesystem ~/Documents

# Local server with an environment variable
claude mcp add --env AIRTABLE_API_KEY=YOUR_KEY airtable -- npx -y airtable-mcp-server

# Remote HTTP server
claude mcp add --transport http notion https://mcp.notion.com/mcp

# Remote HTTP server with an auth header
claude mcp add --transport http github https://api.githubcopilot.com/mcp/ --header "Authorization: Bearer YOUR_PAT"

    Option ordering matters. All flags (--transport, --env, --scope, --header) must come before the server name. Put a flag after the name and you will get a confusing parse error or the flag will be passed to your server instead of to Claude Code.

    Scopes: local, project, user

    The --scope flag decides where the config is written and who sees it:

    • local (the default) loads only in the current project, private to you. Stored in ~/.claude.json keyed by the project path.
    • project loads in the current project and is shared with your team. Stored in a .mcp.json file at the project root that you commit to git.
    • user loads across all your projects, private to you. Also stored in ~/.claude.json.
    # Available across all your projects
claude mcp add --scope user --transport http sentry https://mcp.sentry.dev/mcp

# Shared with your team via .mcp.json in the repo
claude mcp add --scope project filesystem -- npx -y @modelcontextprotocol/server-filesystem .

    When the same server name exists at multiple scopes, local wins over project, which wins over user. The whole entry from the winning scope is used; fields are not merged.

    claude mcp list, get, and remove

    # List every configured server and its connection status
claude mcp list

# Show the full config for one server
claude mcp get github

# Remove a server
claude mcp remove github

    claude mcp list is your first diagnostic. It shows each server as connected, pending, or failed. Project-scoped servers from a .mcp.json you have not approved yet show as Pending approval until you run claude interactively and accept them.

    Other useful commands

    # Add from a raw JSON blob (handy when copying from a server's README)
claude mcp add-json weather '{"type":"stdio","command":"npx","args":["-y","weather-mcp"]}'

# Import everything you already set up in Claude Desktop (macOS / WSL)
claude mcp add-from-claude-desktop

    Inside a running Claude Code session, type /mcp to see live server status, tool counts, and to trigger OAuth login for remote servers that need it.

    Troubleshooting: the errors the docs skip

    Most MCP failures are not exotic. They are paths, quoting, and the app not restarting. Work this list top to bottom.

    Server not loading / no tools appear

    1. Did you actually restart? Claude Desktop only reads the config at launch. Fully quit (tray icon > Quit on Windows, Cmd+Q on macOS) and reopen. In Claude Code, run claude mcp list to see the real status instead of guessing.
    2. Is the command on PATH? The single most common stdio failure is npx, node, python, or uvx not being found by the app. GUI apps often have a narrower PATH than your terminal. Fix it by using an absolute path. Find it with which npx (macOS/Linux) or where npx (Windows), then put that full path in command.
    3. Read the logs. Claude Desktop writes per-server logs. macOS: ~/Library/Logs/Claude/. Windows: %APPDATA%\Claude\logs\. Look for mcp-server-NAME.log. The actual error (missing module, bad token, wrong path) is almost always sitting right there.

    spawn ENOENT or “command not found”

    This means the OS could not find the executable named in command. It is a PATH problem, not a Claude problem. Use the absolute path (see above). On Windows specifically, see the npx note below.

    JSON syntax errors (the silent killer)

    If claude_desktop_config.json has a single syntax error, Claude Desktop loads zero servers and usually says nothing. The usual culprits:

    • Trailing commas. JSON forbids a comma after the last item in an object or array. "args": ["a", "b",] is invalid.
    • Smart quotes. If you edited the file in a word processor, curly quotes (the slanted kind) break the parser. Use a code editor and straight quotes only.
    • Unescaped Windows backslashes. In JSON, \ is an escape character, so every backslash in a Windows path must be doubled: C:\\Users\\YOU\\Documents. A single backslash silently corrupts the string.

    Paste the whole file into any JSON validator before restarting. Thirty seconds there saves an hour of staring.

    Claude Code: flag passed to the wrong place

    If claude mcp add behaves strangely, you almost certainly put a flag after the server name or forgot the --. Reread the order: claude mcp add [flags] NAME -- COMMAND ARGS. The -- separates Claude Code’s flags from your server’s command.

    Windows quirks

    • npx needs a wrapper in some setups. If a bare "command": "npx" fails on Windows, launch it through cmd: "command": "cmd" with "args": ["/c", "npx", "-y", "the-server-package"]. This resolves a class of “npx works in my terminal but not in Claude” failures.
    • Use the right config root. It is %APPDATA%\Claude\ (which is AppData\Roaming), not AppData\Local. Mixing these up means you are editing a file the app never reads.
    • Git Bash mangles paths. If you run commands through Git Bash, it can rewrite paths like /c/Users or absolute paths inside arguments. Prefer PowerShell or cmd for claude mcp add, or pass paths exactly as Windows expects them.
    • WSL is a separate world. A server installed inside WSL is not visible to a Windows-native Claude Desktop, and vice versa. Keep both on the same side.

    Remote server returns 401 / 403

    The server needs authentication. In Claude Code, run /mcp and complete the OAuth flow in your browser. If you hardcoded an Authorization header and it is rejected, the token is wrong for that endpoint; remove the header and let OAuth handle it instead.

    Frequently asked questions

    What is an MCP server in one sentence?

    A small program that exposes tools (functions like read-file or query-database) to Claude over the Model Context Protocol, so Claude can take real actions instead of only producing text.

    What is the difference between Claude Desktop and Claude Code for MCP?

    Claude Desktop is the chat app and you configure servers by hand-editing claude_desktop_config.json, then restarting. Claude Code is the terminal/IDE tool and you configure servers with the claude mcp add command, which writes the config for you.

    Where is the Claude Desktop config file?

    macOS: ~/Library/Application Support/Claude/claude_desktop_config.json. Windows: %APPDATA%\Claude\claude_desktop_config.json. The quickest way to open it is Settings > Developer > Edit Config inside the app.

    Why is my MCP server not showing up?

    In order of likelihood: you did not fully restart the app, the command is not on the app’s PATH (use an absolute path), or there is a JSON syntax error such as a trailing comma, a smart quote, or an unescaped Windows backslash. Check the per-server log in the Claude logs folder for the exact error.

    What does the double dash do in claude mcp add?

    The -- separates Claude Code’s own flags from the command that launches your server. Flags like --transport and --env go before it; the actual launch command (npx -y some-server) goes after it.

    What is the default scope for claude mcp add?

    local. The server loads only in the current project and stays private to you. Use --scope user to make it available in every project, or --scope project to share it with your team via a committed .mcp.json.

    Is SSE or HTTP the right transport for remote servers?

    HTTP. SSE still works but is deprecated. Use --transport http for any new remote server unless its documentation specifically requires SSE.

    How do I remove an MCP server?

    In Claude Code, run claude mcp remove NAME. In Claude Desktop, delete that server’s entry from the mcpServers object in claude_desktop_config.json and restart the app.

    Where to go next

    Once your servers connect cleanly, the leverage comes from using them well. For how this fits a daily workflow, read the AI operator’s stack; if you are choosing between coding environments, see Claude Code vs Cursor. And if you want a concrete first server to wire up, the Notion MCP setup is a clean, high-value place to start.

    Frequently Asked Questions

    What is MCP and why does it matter for Claude?

    MCP (Model Context Protocol) is an open standard that lets Claude connect to external tools, databases, APIs, and services. Without MCP, Claude can only work with text in the conversation window. With an MCP server connected, Claude can read your files, query a live database, hit an API, or control a browser — turning it from a chat interface into an autonomous agent.

    How do I add an MCP server to Claude Desktop?

    Edit the claude_desktop_config.json file (found at ~/Library/Application Support/Claude/ on Mac, %APPDATA%/Claude/ on Windows). Add your server under the ‘mcpServers’ key with a ‘command’, ‘args’, and optional ‘env’ block. Save the file and restart Claude Desktop. The server appears in Claude’s tool list if it loaded correctly.

    How do I add an MCP server to Claude Code?

    Run ‘claude mcp add [args…]’ from your terminal. For a remote SSE server use ‘claude mcp add –transport sse ‘. List configured servers with ‘claude mcp list’. Servers added this way are scoped to your user profile unless you use the –project flag.

    Why does my MCP server connect but Claude can’t see my data?

    The most common cause is scope or permission gaps. For Notion, verify your integration has been granted access to the specific pages/databases — the connection succeeds even without page access. For file servers, check that the path in your config resolves correctly from the shell Claude launches (not your interactive shell). For OAuth servers, re-authorize and confirm token scopes.

    What is the difference between stdio and SSE MCP transports?

    stdio runs the MCP server as a local subprocess — Claude launches the command you specify and communicates over stdin/stdout. This is used for local tools and CLIs. SSE (Server-Sent Events) connects to a remote HTTP server. Use stdio for local tools like filesystem access or database clients; use SSE or Streamable HTTP for cloud services or shared team servers.

    Which MCP servers should I start with?

    The highest-value first connections are: filesystem (read/write your local files), a database client for your primary DB, and a service you interact with daily (Notion, Slack, GitHub, Linear). The Notion MCP server is a clean first project — see the dedicated setup guide on this site for the exact config and common errors.

    📖 Related Claude Guides


  • Local AI Without NPU: Turn a $400 Laptop Into an AI PC

    Local AI Without NPU: Turn a $400 Laptop Into an AI PC

    All fall, Microsoft has been selling one idea: the future is the AI PC — a Copilot+ machine with a dedicated neural chip (an NPU), Recall, Click to Do, a thousand dollars and up, and your old laptop need not apply.

    I had a $400 budget laptop on my desk — an AMD Ryzen 5 7520U, 16 GB of RAM, no NPU — and a hunch that the whole framing was backwards. The AI-first laptop was never about the chip. It’s about architecture.

    A few hours later, that $400 laptop had a private AI brain, voice control, and a control panel I run from my phone. On the things that actually matter for operating a machine, it does more than the Copilot+ PC it’s supposedly too cheap to be. Here’s the exact build.

    The thesis: AI-first is architecture, not a chip

    The trick is to stop asking your laptop to be the supercomputer. Split the job:

    • The brain lives in the cloud. The heavy reasoning runs on a frontier model (I use Claude) with effectively unlimited horsepower. No NPU on Earth competes with that.
    • The body lives on your laptop. Your machine becomes the always-on hands: it holds your private data, runs small models locally for anything sensitive, and executes the actions the brain decides on.

    An NPU optimizes a handful of on-device Windows features. Architecture gives you an actual operator. Guess which one you feel every day.

    Step 0 — Make it always-on

    An operator rig is a little server, and servers don’t nap. My laptop kept sleeping and killing background jobs, so the first move was to take that off the table (while plugged in):

    powercfg /change monitor-timeout-ac 0
powercfg /change standby-timeout-ac 0
powercfg /setacvalueindex SCHEME_CURRENT SUB_BUTTONS LIDACTION 0
powercfg /setactive SCHEME_CURRENT

    Screen never blanks, never sleeps, and it keeps running with the lid closed — while still sleeping on battery as a safety. Now it’s a real always-on host.

    Step 1 — A private AI brain that lives on the laptop

    The local engine is Ollama; the chat interface is open-webui (running in Docker). If you want the multi-agent version of this idea, I’ve also written up building a free AI agent army with Ollama and Claude. The only thing standing between me and a private, offline ChatGPT was one wrong setting — open-webui was pointed at a dead address. The fix was to aim it at the host:

    docker run -d --name open-webui --restart always -p 3000:8080 \
  -v open-webui:/app/backend/data \
  -e OLLAMA_BASE_URL=http://host.docker.internal:11434 \
  ghcr.io/open-webui/open-webui:main

    The proof: a 3-billion-parameter model (Llama 3.2) introduced itself in about 10 seconds at ~12 tokens/second — on the CPU, no NPU, no discrete GPU. Fast enough for real Q&A, drafting, and summaries. Seven models sit ready on disk, and the whole thing is reachable from my phone over a private network.

    Everything here runs offline. For anything I don’t want leaving the machine, that’s the entire point.

    Step 2 — Voice that never leaves the machine

    A local Whisper speech-to-text container (OpenAI-compatible API) became a push-to-talk dictation tool: hold a key, talk, release, and the text drops into whatever app is focused. I verified the pipeline without even touching the mic — Windows text-to-speech generated a clip, the local Whisper transcribed it, and it round-tripped clean:

    Spoken: “Testing one two three. This is the private local transcription engine.”
    Whisper heard: “Testing 1-2-3. This is the private local transcription engine.”

    Windows has built-in dictation (Win+H) and Copilot voice too — but those ship your audio to the cloud. The local version does the same job, and your voice never leaves the laptop.

    Step 3 — Turn your phone into the control panel

    Using Tailscale (a private mesh network), every service on the laptop is reachable from my phone — without exposing anything to the public internet. I added a tiny web page (one small nginx container) as a mobile operator console: one tap to the local AI, automations, status, and finance dashboards. Pin it to the home screen and the laptop is in your pocket.

    The honest scoreboard vs. a Copilot+ PC

    Capability Copilot+ PC ($1,000+) This $400 laptop
    Private AI running on the device Limited (small NPU models) ✅ Full Ollama stack, 7 models
    An AI that operates the machine ❌ ✅ Runs commands, edits files, fixes things
    Private, offline voice dictation ❌ (cloud) ✅ Local Whisper
    Phone control panel ❌ ✅ Tailscale operator console
    Recall / Click to Do / Cocreator ✅ (needs the NPU) ❌
    Screenshots everything you do ⚠️ Recall does, by design ✅ No — nothing is recorded

    I’m being fair: the NPU-only features are genuinely off the table on cheap hardware. But for operating your computer — and for privacy — the architecture beats the chip.

    Why this matters more than it looks

    The quiet headline isn’t “I saved money.” It’s where the data lives. Microsoft’s flagship AI-PC feature, Recall, works by screenshotting everything you do. This build does the opposite: the sensitive payload stays on your machine, and the cloud is used only for the heavy thinking that doesn’t need your private files.

    That’s not just a hobbyist’s preference. It’s the exact requirement for anyone in a regulated field — healthcare, legal, finance — who can’t send client data to a third party but still wants real AI leverage. The cheap laptop isn’t the story. The architecture is.

    Frequently asked questions

    Do I need a Copilot+ PC or an NPU to run local AI?

    No. Any laptop with around 16 GB of RAM and a modern CPU can run small local models. An NPU accelerates certain Windows features but is not required for Ollama or local chat.

    Is local AI actually private?

    Yes. With Ollama, the model runs on your own machine and works with no internet connection — nothing is sent to a cloud service.

    What is the difference between Ollama and open-webui?

    Ollama is the engine that runs the models. open-webui is the friendly chat interface that sits in front of it.

    How fast is a local model on a budget laptop?

    On a CPU-only AMD Ryzen 5 with 16 GB of RAM, a 3-billion-parameter model answered at roughly 12 tokens per second — fine for quick questions, drafting, and summaries. Larger models run slower.

    Can I use it from my phone?

    Yes. Over a private Tailscale network you can reach your laptop’s AI and tools from your phone without exposing anything to the public internet.

    Is this better than a Copilot+ PC?

    For operating your machine and for privacy, this setup does more. For NPU-specific Windows features like Recall and Click to Do, a Copilot+ PC is required.

    Want this on your machine?

    Tygart Media builds privacy-first, local-AI operator setups — especially for teams in regulated industries that need real AI leverage without sending data to the cloud. Reach out and we’ll scope it to your hardware.

  • Using Claude in Chrome with LinkedIn: What It Is Good For (and What to Avoid)

    Using Claude in Chrome with LinkedIn: What It Is Good For (and What to Avoid)

    Last verified: June 2026.

    What Claude in Chrome can and can’t do on LinkedIn

    Task Verdict Notes
    Summarize a profile ✅ Safe and useful Read-only, no automation signal
    Draft a personalized DM ✅ Safe and useful You review and send manually
    Research a company page ✅ Safe and useful Read-only extraction
    Summarize a post or thread ✅ Safe and useful Read-only, no interaction
    Auto-post to your feed ❌ High risk Violates ToS, triggers automation detection
    Auto-connect with multiple people ❌ High risk Account restriction risk
    Bulk message sending ❌ High risk Spam detection, potential ban

    The Claude for Chrome extension lets Claude see and act inside your browser. The obvious temptation is to point it at LinkedIn and have it post for you. Do not do that. Here is what the extension is genuinely useful for on a professional network – and the one job you should never hand it.

    What to avoid: automated feed posting

    Driving the browser to auto-post feed content is a high-risk move. Professional networks actively detect automation, it violates their terms of service, and it can get an account throttled or suspended. If you want scheduled feed posts, use a social scheduler’s official API – that is the supported, durable path, and the one that will not get your account flagged. The browser is an assistant, not a posting robot.

    What it is actually good for

    1. Paste-assist for long-form Articles

    This is the real opportunity. Social schedulers – and every third-party tool – can only push short feed posts through the official API. Native long-form Articles and Newsletters have no public publishing endpoint, so they stay a manual copy-paste. That matters because AI engines cite long-form Articles far more often than short posts, by a wide margin. The most citation-valuable format is the one no tool can automate. That is exactly where an in-browser assistant earns its place: with you in the loop, it can help move a finished, formatted draft into the Article composer and tidy the formatting – turning a tedious manual paste into a guided one.

    2. Multi-account navigation

    If you operate a personal profile plus several company pages, the extension can help you move between already-authenticated sessions and keep track of which identity you are acting as – reducing the “posted from the wrong account” mistakes that come with juggling many pages by hand.

    3. Research, review, and drafting

    Reading a profile and summarizing it, scanning a feed for the day’s relevant threads, or drafting a thoughtful comment for your approval are all squarely in bounds. The assistant prepares; you decide and click.

    How to do it safely

    • Keep a human in the loop on anything that publishes or sends – review before you submit.
    • Never bulk-send connection requests, messages, or comments. That is the behavior detectors look for.
    • Use the official scheduler API for anything recurring; reserve the browser for the manual, assistive steps.
    • Treat the extension as read-and-prepare by default, act-and-publish only with your explicit click.

    Frequently asked questions

    Can Claude auto-post to LinkedIn for me?

    Not safely, and you should not try. Use a social scheduler’s API for feed posts. The browser extension is for assistive, human-in-the-loop work – especially the long-form Articles that no API can publish.

    Why can’t scheduling tools publish Articles or Newsletters?

    Because the platform exposes no public API for them. Feed posts have an endpoint; long-form does not. That limitation is shared by every tool, which is why the manual paste persists.

    Is browser automation against the rules?

    Automated posting and bulk outreach generally violate the terms and risk the account. Assistive, human-approved use – drafting, summarizing, helping you paste – is the safe lane. When in doubt, keep a person on the trigger.

    For the bigger picture of how this fits a full content operation, see The AI Operator’s Stack.

    Frequently Asked Questions

    What is the Claude for Chrome extension?

    Claude for Chrome (Claude in Chrome) is a browser extension that lets Claude see and interact with the page currently open in your browser. It can read page content, summarize what’s visible, draft responses based on what it sees, and in some configurations take actions like clicking or filling forms — depending on what permissions are active.

    Can I use Claude to automate LinkedIn posts?

    You should not. Professional networks like LinkedIn actively detect browser automation, and auto-posting violates their Terms of Service. Using Claude in Chrome to drive automated feed posting can result in account throttling or permanent suspension. Claude is useful for drafting post content, but you should always review and publish manually.

    What is Claude in Chrome actually useful for on LinkedIn?

    Legitimate high-value uses include: summarizing a prospect’s profile before a sales call, researching a company page, drafting a personalized connection request or DM based on what you read on a profile, and summarizing a post or comment thread. All of these are read-and-assist operations that don’t trigger automation signals.

    Does using Claude in Chrome on LinkedIn violate their terms of service?

    Read-only operations (summarizing, researching, drafting) generally do not violate LinkedIn’s terms. Automated actions (clicking, posting, connecting, messaging at scale) do. The key distinction is whether Claude is taking actions on LinkedIn’s platform autonomously versus helping you draft content that you then review and submit yourself.

    How is Claude in Chrome different from a LinkedIn scraper?

    Claude in Chrome reads what’s visible on the page you have open — it is not a bulk scraper that crawls hundreds of profiles automatically. It operates within your active browser session, one page at a time, and does not bypass LinkedIn’s normal page rendering. A scraper typically makes API calls or headless browser requests at volume; Claude in Chrome is a single-session reading assistant.

    What Claude model powers Claude in Chrome?

    Claude in Chrome uses Anthropic’s Claude models — currently Claude Sonnet 4.6 is the primary model for browser interactions, balancing capability and speed. Anthropic may update the underlying model over time. You can check your current model in the extension settings.

    📖 Related Claude Guides