# Freek

All blogposts on freek.dev

This is one page of public article previews, not the complete archive. Follow Next page to continue. Summaries are not the original full articles.

## ★ Detecting suspicious logins in your Laravel app

DevFeed: [★ Detecting suspicious logins in your Laravel app](<https://devfeed.tech/articles/detecting-suspicious-logins-in-your-laravel-app-147122.md>)

Original publisher: [Read original article](<https://freek.dev/3230-detecting-suspicious-logins-in-your-laravel-app>)

Author: Freek Van der Herten (freek@spatie.be)

Published: 2026-11-20T10:01:17Z

Content type: article

Language: en

Sources: [Freek](<https://devfeed.tech/sources/freek-dev-all-blogposts.md>)

Topics: [Laravel](<https://devfeed.tech/topics/laravel.md>), [Laravel Boost](<https://devfeed.tech/topics/laravel-boost.md>), [codex](<https://devfeed.tech/topics/codex.md>)

Tags: [ai](<https://devfeed.tech/tags/ai.md>), [ai-coding-agent](<https://devfeed.tech/tags/ai-coding-agent.md>), [authentication](<https://devfeed.tech/tags/authentication.md>), [block](<https://devfeed.tech/tags/block.md>), [boost](<https://devfeed.tech/tags/boost.md>), [browser](<https://devfeed.tech/tags/browser.md>), [composer](<https://devfeed.tech/tags/composer.md>), [country](<https://devfeed.tech/tags/country.md>), [credential-stuffing](<https://devfeed.tech/tags/credential-stuffing.md>), [credentials](<https://devfeed.tech/tags/credentials.md>), [device](<https://devfeed.tech/tags/device.md>), [email](<https://devfeed.tech/tags/email.md>), [failed](<https://devfeed.tech/tags/failed.md>), [geolocation](<https://devfeed.tech/tags/geolocation.md>), [history](<https://devfeed.tech/tags/history.md>), [ip](<https://devfeed.tech/tags/ip.md>), [laravel](<https://devfeed.tech/tags/laravel.md>), [location](<https://devfeed.tech/tags/location.md>), [login](<https://devfeed.tech/tags/login.md>), [medium](<https://devfeed.tech/tags/medium.md>), [mobile-networks](<https://devfeed.tech/tags/mobile-networks.md>), [open-source](<https://devfeed.tech/tags/open-source.md>), [security](<https://devfeed.tech/tags/security.md>), [spatie](<https://devfeed.tech/tags/spatie.md>)

### AI overview

laravel-suspicious-login scores assessed logins by configurable signals, so several indicators can be weighed together instead of blocking on an unfamiliar IP alone. Its DefaultPreset checks signals including new devices, countries and IPs, impossible travel, repeated failures, credential stuffing and suspicious user agents; successful and failed attempts are logged, but failed attempts are not scored. Presets set risk thresholds and actions: in the example, a new country sends an email, while a new country plus a new device reaches high risk and emails then blocks the login. Blocking is session-based unless another authentication flow supplies its own action. Device and country checks rely on prior successful, unblocked logins, so they do not flag a first login; country checks require location data and can be triggered by travel or VPNs. The excerpt recommends monitoring before enabling blocking. Presets can also vary by user, and email handling can be customized through Laravel mailables, views and events.

### Source excerpt

Imagine someone logs in to your account from the other side of the world. If you're travelling, that might be perfectly normal. But if you're sitting at home in your hometown, it's suspicious. Someone might have gotten hold of your credentials. We've released laravel-suspicious-login to notify users about suspicious logins and let you decide what happens next. It looks at signals such as the browser, location and earlier failed attempts. You can email the user, block the login or run your own actions. You can install it with Composer, or let your AI coding agent do it. The package includes a Laravel Boost skill for installing and customizing it. Adding up the signals Let's take a look at how the package detects signals that might indicate a suspicious login. An unfamiliar IP address isn't much of a reason to reject a login. Mobile networks change addresses all the time. Several signals together can be more useful. Each check adds a configurable number of points when it flags a login. For example, with DefaultPreset, working geolocation and an existing login history, these checks could contribute: New device +25 New IP address +10 New country +30 --- Total 65 Assuming the other checks pass, that's medium risk. The default thresholds in config/suspicious-login.php are: 'risk_thresholds' => [ 'medium' => 40, 'high' => 70, ], The default preset also checks for impossible travel, repeated failed attempts, credential stuffing and suspicious user agents. The package also logs all login attempts, both successful and failed, so you can review a user's login history. Assessed logins include their score and the reasons behind it. Failed logins are recorded, but aren't scored. Choosing when to block A preset class combines the checks, thresholds and actions in one PHP class. Here's a small example for a session-based application. A new country should trigger an email. A new country together with a new device should also block the login. Let's look at this example preset impleme

## When Is a Workday Done?

DevFeed: [When Is a Workday Done?](<https://devfeed.tech/articles/when-is-a-workday-done-142436.md>)

Original publisher: [Read original article](<https://freek.dev/3226-when-is-a-workday-done>)

Author: Freek Van der Herten (freek@spatie.be)

Published: 2026-11-18T14:01:18Z

Content type: opinion

Language: en

Sources: [Freek](<https://devfeed.tech/sources/freek-dev-all-blogposts.md>)

Topics: [Artificial Intelligence](<https://devfeed.tech/topics/ai.md>)

Tags: [agents](<https://devfeed.tech/tags/agents.md>), [ai](<https://devfeed.tech/tags/ai.md>), [ai-agents](<https://devfeed.tech/tags/ai-agents.md>), [burnout](<https://devfeed.tech/tags/burnout.md>), [mindset](<https://devfeed.tech/tags/mindset.md>), [productivity](<https://devfeed.tech/tags/productivity.md>), [work-life-balance](<https://devfeed.tech/tags/work-life-balance.md>), [workday](<https://devfeed.tech/tags/workday.md>)

### AI overview

AI agents have increased the author's productivity, while the effort of keeping up with everything can make work exhausting. The author is learning to work more intentionally, focus on what matters, and recognize when they have done enough. This is based on a brief excerpt, so it does not establish the full article's methods or conclusions.

### Source excerpt

AI agents have changed the rhythm of my workday. I can get more done than ever, but keeping up with everything can be exhausting. I'm learning to work more intentionally, stay focused on what matters and know when I've done enough. Read more

## Giving AI Agents a Better Way to Debug CSS

DevFeed: [Giving AI Agents a Better Way to Debug CSS](<https://devfeed.tech/articles/giving-ai-agents-a-better-way-to-debug-css-140309.md>)

Original publisher: [Read original article](<https://freek.dev/3225-giving-ai-agents-a-better-way-to-debug-css>)

Author: Freek Van der Herten (freek@spatie.be)

Published: 2026-11-17T12:30:30Z

Content type: tutorial

Language: en

Sources: [Freek](<https://devfeed.tech/sources/freek-dev-all-blogposts.md>)

Topics: [CSS](<https://devfeed.tech/topics/css.md>), [AI in frontend development](<https://devfeed.tech/topics/ai-in-frontend-development.md>), [Tool](<https://devfeed.tech/topics/tool.md>)

Tags: [agents](<https://devfeed.tech/tags/agents.md>), [ai](<https://devfeed.tech/tags/ai.md>), [browser](<https://devfeed.tech/tags/browser.md>), [cascade](<https://devfeed.tech/tags/cascade.md>), [chrome-devtools-mcp](<https://devfeed.tech/tags/chrome-devtools-mcp.md>), [codex](<https://devfeed.tech/tags/codex.md>), [css](<https://devfeed.tech/tags/css.md>), [debug](<https://devfeed.tech/tags/debug.md>), [diagnose](<https://devfeed.tech/tags/diagnose.md>)

### AI overview

Chrome DevTools MCP exposes a `get_css_styles` tool that lets Codex inspect the matched CSS rules and overridden declarations for an element in the browser. The article says this gives agents evidence about the styles actually applied, helping them diagnose cascade and specificity issues instead of guessing from source files. The supplied text is an excerpt, so it does not establish setup details or broader coverage.

### Source excerpt

Amit Merchant shows how to connect Chrome DevTools MCP to Codex and use its get_css_styles tool to inspect matched CSS rules and overridden declarations in the browser. This lets agents diagnose cascade and specificity issues using the styles actually applied to an element instead of guessing from source files. Read more

## Tests as data: ensuring AI-generated code does what we want

DevFeed: [Tests as data: ensuring AI-generated code does what we want](<https://devfeed.tech/articles/tests-as-data-ensuring-ai-generated-code-does-what-we-want-134495.md>)

Original publisher: [Read original article](<https://freek.dev/3223-tests-as-data-ensuring-ai-generated-code-does-what-we-want>)

Author: Freek Van der Herten (freek@spatie.be)

Published: 2026-11-15T12:30:23Z

Content type: article

Language: en

Sources: [Freek](<https://devfeed.tech/sources/freek-dev-all-blogposts.md>)

Topics: [AI-assisted coding](<https://devfeed.tech/topics/ai-assisted-coding.md>), [Test automation](<https://devfeed.tech/topics/test-automation.md>)

Tags: [acceptance-tests](<https://devfeed.tech/tags/acceptance-tests.md>), [agents](<https://devfeed.tech/tags/agents.md>), [ai](<https://devfeed.tech/tags/ai.md>), [ai-generated-code](<https://devfeed.tech/tags/ai-generated-code.md>), [ai-generated-software](<https://devfeed.tech/tags/ai-generated-software.md>), [coding-agents](<https://devfeed.tech/tags/coding-agents.md>), [data](<https://devfeed.tech/tags/data.md>), [review](<https://devfeed.tech/tags/review.md>), [software](<https://devfeed.tech/tags/software.md>), [stored](<https://devfeed.tech/tags/stored.md>), [testing](<https://devfeed.tech/tags/testing.md>), [tests](<https://devfeed.tech/tags/tests.md>)

### AI overview

Matteo Vaccari proposes storing readable acceptance tests as data instead of embedding expectations in test code. Separating those expectations from the test runner is intended to make them easier to review and harder for coding agents to change unintentionally. The excerpt gives no implementation details or evidence of how well the approach works.

### Source excerpt

Matteo Vaccari explains how readable acceptance tests, stored as data rather than test code, can define what we expect from AI-generated software. Separating those expectations from the test runner makes them easier to review and protect from unwanted changes by coding agents. Read more

## Using Laravel Boost for package development with Orchestra Testbench

DevFeed: [Using Laravel Boost for package development with Orchestra Testbench](<https://devfeed.tech/articles/using-laravel-boost-for-package-development-with-orchestra-testbench-131292.md>)

Original publisher: [Read original article](<https://freek.dev/3219-using-laravel-boost-for-package-development-with-orchestra-testbench>)

Author: Freek Van der Herten (freek@spatie.be)

Published: 2026-11-12T12:30:29Z

Content type: article

Language: en

Sources: [Freek](<https://devfeed.tech/sources/freek-dev-all-blogposts.md>)

Topics: [Laravel Boost](<https://devfeed.tech/topics/laravel-boost.md>), [Developer experience](<https://devfeed.tech/topics/developer-experience.md>)

Tags: [best-practices](<https://devfeed.tech/tags/best-practices.md>), [laravel](<https://devfeed.tech/tags/laravel.md>), [laravel-boost](<https://devfeed.tech/tags/laravel-boost.md>), [package](<https://devfeed.tech/tags/package.md>), [php](<https://devfeed.tech/tags/php.md>), [spatie](<https://devfeed.tech/tags/spatie.md>), [testbench](<https://devfeed.tech/tags/testbench.md>), [testing](<https://devfeed.tech/tags/testing.md>)

### AI overview

The excerpt says Laravel Boost can be adapted for package development by pairing it with Orchestra Testbench. It highlights tweaks that direct Boost to read and write in the package root, let it run through a custom artisan file, and tailor its workflow to packages rather than full Laravel applications. The excerpt does not provide the specific configuration steps.

### Source excerpt

Rias Van der Veken shows how to make Laravel Boost work nicely in package development by pairing it with Orchestra Testbench. The article covers a few smart tweaks so Boost reads and writes in the package root, works through a custom artisan file, and stays tailored for package workflows instead of full Laravel apps. Read more

## Your Laravel queue workers keep 8 copies of your app in memory

DevFeed: [Your Laravel queue workers keep 8 copies of your app in memory](<https://devfeed.tech/articles/your-laravel-queue-workers-keep-8-copies-of-your-app-in-memory-129375.md>)

Original publisher: [Read original article](<https://freek.dev/3218-your-laravel-queue-workers-keep-8-copies-of-your-app-in-memory>)

Author: Freek Van der Herten (freek@spatie.be)

Published: 2026-11-11T12:31:09Z

Content type: article

Language: en

Sources: [Freek](<https://devfeed.tech/sources/freek-dev-all-blogposts.md>)

Topics: [Laravel](<https://devfeed.tech/topics/laravel.md>)

Tags: [horizon](<https://devfeed.tech/tags/horizon.md>), [laravel](<https://devfeed.tech/tags/laravel.md>), [memory](<https://devfeed.tech/tags/memory.md>), [opcache](<https://devfeed.tech/tags/opcache.md>), [package](<https://devfeed.tech/tags/package.md>), [performance](<https://devfeed.tech/tags/performance.md>), [queue](<https://devfeed.tech/tags/queue.md>), [queues](<https://devfeed.tech/tags/queues.md>), [servers](<https://devfeed.tech/tags/servers.md>), [spatie](<https://devfeed.tech/tags/spatie.md>), [throughput](<https://devfeed.tech/tags/throughput.md>), [workers](<https://devfeed.tech/tags/workers.md>)

### AI overview

Laravel queue workers and Horizon supervisors each keep a compiled copy of the app in memory, so multiple processes can consume substantial memory on smaller servers. The post introduces queue-prefork, which shares opcache across forked workers and is described as reducing memory use without changing job throughput. The supplied text gives no measurements or implementation details.

### Source excerpt

This post explains why Laravel queue workers and Horizon supervisors each keep their own compiled copy of your app in memory, and how that adds up fast on smaller servers. It also introduces queue-prefork, a package that shares opcache across forked workers and dramatically cuts memory usage without changing job throughput. Read more

## Every public API should have a feedback endpoint for agents

DevFeed: [Every public API should have a feedback endpoint for agents](<https://devfeed.tech/articles/every-public-api-should-have-a-feedback-endpoint-for-agents-129376.md>)

Original publisher: [Read original article](<https://freek.dev/3222-every-public-api-should-have-a-feedback-endpoint-for-agents>)

Author: Freek Van der Herten (freek@spatie.be)

Published: 2026-11-10T21:19:45Z

Content type: article

Language: en

Sources: [Freek](<https://devfeed.tech/sources/freek-dev-all-blogposts.md>)

Topics: [API](<https://devfeed.tech/topics/api.md>), [MSP MCP](<https://devfeed.tech/topics/msp-mcp.md>), [human in the loop agent](<https://devfeed.tech/topics/human-in-the-loop-agent.md>)

Tags: [agents](<https://devfeed.tech/tags/agents.md>), [ai](<https://devfeed.tech/tags/ai.md>), [api](<https://devfeed.tech/tags/api.md>), [feedback](<https://devfeed.tech/tags/feedback.md>), [mcp](<https://devfeed.tech/tags/mcp.md>)

### AI overview

Inspired by a proposal for agent-facing API feedback, the author added a tool to the MCP servers for Oh Dear, There There, and Mailcoach. When an agent cannot complete a task because MCP or API functionality is missing, it can send feedback directly to the provider. The excerpt describes reporting missing functionality; it does not specify how feedback is processed or whether it leads to changes.

### Source excerpt

I like this idea very much. Inspired by this tweet, I added a tool to the MCP servers for Oh Dear, There There, and Mailcoach that lets agents report missing MCP or API functionality. If an agent can't complete a task because something is missing, it can send that feedback directly to us. J Jack Sharkey @jsharkey 𝕏 Every public API should have a feedback endpoint for agents When my agent struggles to use your API, it should be able to submit structured feedback directly Your agent should consume that feedback, fix the API + docs, ship an update, and notify my agent Remove the human from the loop and let the agents work! Worth sharing Read on X ↗

## Ding, toasts with real spring physics

DevFeed: [Ding, toasts with real spring physics](<https://devfeed.tech/articles/ding-toasts-with-real-spring-physics-123892.md>)

Original publisher: [Read original article](<https://freek.dev/3216-ding-toasts-with-real-spring-physics>)

Author: Freek Van der Herten (freek@spatie.be)

Published: 2026-11-09T12:31:06Z

Content type: article

Language: en

Sources: [Freek](<https://devfeed.tech/sources/freek-dev-all-blogposts.md>)

Topics: [Svelte](<https://devfeed.tech/topics/svelte.md>)

Tags: [behaviors](<https://devfeed.tech/tags/behaviors.md>), [interactive](<https://devfeed.tech/tags/interactive.md>), [javascript](<https://devfeed.tech/tags/javascript.md>), [layout](<https://devfeed.tech/tags/layout.md>), [library](<https://devfeed.tech/tags/library.md>), [notification](<https://devfeed.tech/tags/notification.md>), [physics](<https://devfeed.tech/tags/physics.md>), [react](<https://devfeed.tech/tags/react.md>), [spring](<https://devfeed.tech/tags/spring.md>), [svelte](<https://devfeed.tech/tags/svelte.md>), [themes](<https://devfeed.tech/tags/themes.md>), [toast](<https://devfeed.tech/tags/toast.md>), [ui](<https://devfeed.tech/tags/ui.md>)

### AI overview

Ding is a toast notification library featuring spring physics, with support for React, Svelte, and plain DOM. Its site offers interactive demos covering layouts, sounds, themes, and toast behaviors.

### Source excerpt

Ding is a toast notification library with playful spring physics, built to work with React, Svelte, or plain DOM. The site includes interactive demos for layout, sounds, themes, and different toast behaviors. Read more

## The Next Dependency Problem Is Inside Your AI Agent

DevFeed: [The Next Dependency Problem Is Inside Your AI Agent](<https://devfeed.tech/articles/the-next-dependency-problem-is-inside-your-ai-agent-122601.md>)

Original publisher: [Read original article](<https://freek.dev/3215-the-next-dependency-problem-is-inside-your-ai-agent>)

Author: Freek Van der Herten (freek@spatie.be)

Published: 2026-11-08T12:30:37Z

Content type: opinion

Language: en

Sources: [Freek](<https://devfeed.tech/sources/freek-dev-all-blogposts.md>)

Topics: [AI Agent](<https://devfeed.tech/topics/ai-agent.md>), [Agent Skills](<https://devfeed.tech/topics/agent-skills.md>), [Dependabot](<https://devfeed.tech/topics/dependabot.md>), [Library](<https://devfeed.tech/topics/library.md>)

Tags: [agent](<https://devfeed.tech/tags/agent.md>), [agents](<https://devfeed.tech/tags/agents.md>), [ai](<https://devfeed.tech/tags/ai.md>), [ai-agent](<https://devfeed.tech/tags/ai-agent.md>), [apm](<https://devfeed.tech/tags/apm.md>), [code](<https://devfeed.tech/tags/code.md>), [dependabot](<https://devfeed.tech/tags/dependabot.md>), [dependencies](<https://devfeed.tech/tags/dependencies.md>), [dependency](<https://devfeed.tech/tags/dependency.md>), [dependency-injection](<https://devfeed.tech/tags/dependency-injection.md>), [mcp](<https://devfeed.tech/tags/mcp.md>), [mcp-servers](<https://devfeed.tech/tags/mcp-servers.md>), [plugins](<https://devfeed.tech/tags/plugins.md>), [skills](<https://devfeed.tech/tags/skills.md>), [tooling](<https://devfeed.tech/tags/tooling.md>), [versioning](<https://devfeed.tech/tags/versioning.md>)

### AI overview

AI agent skills, prompts, plugins, and MCP servers are becoming dependencies that should be versioned and managed like application code. The excerpt identifies APM as a way to install reproducible agent tooling and says Dependabot can keep those dependencies up to date.

### Source excerpt

Amit Merchant argues that skills, prompts, plugins, and MCP servers are becoming dependencies of AI agents, and should be versioned and managed like application code. He also highlights APM as a way to install reproducible agent tooling, with Dependabot now able to keep those dependencies up to date. Read more

## Composer 2.11

DevFeed: [Composer 2.11](<https://devfeed.tech/articles/composer-2-11-109518.md>)

Original publisher: [Read original article](<https://freek.dev/3210-composer-211>)

Author: Freek Van der Herten (freek@spatie.be)

Published: 2026-10-30T12:30:47Z

Content type: release

Language: en

Sources: [Freek](<https://devfeed.tech/sources/freek-dev-all-blogposts.md>)

Topics: [Composer](<https://devfeed.tech/topics/composer.md>)

Tags: [composer](<https://devfeed.tech/tags/composer.md>), [dependencies](<https://devfeed.tech/tags/dependencies.md>), [faster](<https://devfeed.tech/tags/faster.md>), [performance](<https://devfeed.tech/tags/performance.md>), [php](<https://devfeed.tech/tags/php.md>), [policy](<https://devfeed.tech/tags/policy.md>), [security](<https://devfeed.tech/tags/security.md>), [security-fixes](<https://devfeed.tech/tags/security-fixes.md>)

### AI overview

Composer 2.11 adds a configurable cooldown dependency policy that withholds newly published package versions for a period. The release also includes security fixes and faster dependency resolution; the excerpt provides no further details about either.

### Source excerpt

Composer 2.11 adds a cooldown dependency policy that withholds newly published package versions for a configurable period. The release also includes several security fixes and faster dependency resolution. Read more

## The last 24 hours in PHP land, as observed by a monitoring service

DevFeed: [The last 24 hours in PHP land, as observed by a monitoring service](<https://devfeed.tech/articles/the-last-24-hours-in-php-land-as-observed-by-a-monitoring-service-98819.md>)

Original publisher: [Read original article](<https://freek.dev/3207-the-last-24-hours-in-php-land-as-observed-by-a-monitoring-service>)

Author: Freek Van der Herten (freek@spatie.be)

Published: 2026-10-24T12:30:36Z

Content type: news

Language: en

Sources: [Freek](<https://devfeed.tech/sources/freek-dev-all-blogposts.md>)

Topics: [Monitoring](<https://devfeed.tech/topics/monitoring.md>), [PHP](<https://devfeed.tech/topics/php.md>)

Tags: [alerts](<https://devfeed.tech/tags/alerts.md>), [critical](<https://devfeed.tech/tags/critical.md>), [data](<https://devfeed.tech/tags/data.md>), [ecosystem](<https://devfeed.tech/tags/ecosystem.md>), [monitoring](<https://devfeed.tech/tags/monitoring.md>), [ohdear](<https://devfeed.tech/tags/ohdear.md>), [outages](<https://devfeed.tech/tags/outages.md>), [php](<https://devfeed.tech/tags/php.md>), [php-vulnerabilities](<https://devfeed.tech/tags/php-vulnerabilities.md>), [security](<https://devfeed.tech/tags/security.md>), [vulnerabilities](<https://devfeed.tech/tags/vulnerabilities.md>)

### AI overview

Oh Dear reports that site outages peaked at 18.8% during the recent critical PHP vulnerabilities, while down alerts rose to 25 times their normal level. The excerpt presents a monitoring service's snapshot of the ecosystem's response but provides no further detail on timing, causes, or measurement methods.

### Source excerpt

Oh Dear shares hard numbers on how the recent critical PHP vulnerabilities rippled through the ecosystem, with site outages peaking at 18.8 percent and down alerts rising to 25 times the normal level. It is a useful, data-backed snapshot of a chaotic day in PHP land from a monitoring service's point of view. Read more

## When Retries Make Things Worse: Protecting Your System From Overload

DevFeed: [When Retries Make Things Worse: Protecting Your System From Overload](<https://devfeed.tech/articles/when-retries-make-things-worse-protecting-your-system-from-overload-90319.md>)

Original publisher: [Read original article](<https://freek.dev/3206-when-retries-make-things-worse-protecting-your-system-from-overload>)

Author: Freek Van der Herten (freek@spatie.be)

Published: 2026-10-19T12:11:16Z

Content type: article

Language: en

Sources: [Freek](<https://devfeed.tech/sources/freek-dev-all-blogposts.md>)

Topics: [rate-limiting](<https://devfeed.tech/topics/rate-limiting.md>), [Concurrency](<https://devfeed.tech/topics/concurrency.md>), [make](<https://devfeed.tech/topics/make.md>)

Tags: [architecture](<https://devfeed.tech/tags/architecture.md>), [best-practices](<https://devfeed.tech/tags/best-practices.md>), [concurrency](<https://devfeed.tech/tags/concurrency.md>), [jitter](<https://devfeed.tech/tags/jitter.md>), [limits](<https://devfeed.tech/tags/limits.md>), [outage](<https://devfeed.tech/tags/outage.md>), [performance](<https://devfeed.tech/tags/performance.md>), [php](<https://devfeed.tech/tags/php.md>), [resilience](<https://devfeed.tech/tags/resilience.md>), [retries](<https://devfeed.tech/tags/retries.md>), [test](<https://devfeed.tech/tags/test.md>)

### AI overview

The article explains how a slow dependency can trigger an outage and describes using deadlines, concurrency limits, retry budgets, and jitter to protect useful work. It includes PHP examples and a controlled overload test design.

### Source excerpt

How a slow dependency becomes an outage, and how deadlines, concurrency limits, retry budgets, and jitter protect useful work. A practical deep dive with PHP examples and a controlled overload test design. Read more

## Why I think we should write our own PR descriptions

DevFeed: [Why I think we should write our own PR descriptions](<https://devfeed.tech/articles/why-i-think-we-should-write-our-own-pr-descriptions-85787.md>)

Original publisher: [Read original article](<https://freek.dev/3205-why-i-think-we-should-write-our-own-pr-descriptions>)

Author: Freek Van der Herten (freek@spatie.be)

Published: 2026-10-13T10:31:12Z

Content type: opinion

Language: en

Sources: [Freek](<https://devfeed.tech/sources/freek-dev-all-blogposts.md>)

Topics: [Pull Request](<https://devfeed.tech/topics/pull-request.md>), [ai code review](<https://devfeed.tech/topics/ai-code-review.md>), [Loop Engineering](<https://devfeed.tech/topics/loop-engineering.md>)

Tags: [agents](<https://devfeed.tech/tags/agents.md>), [ai](<https://devfeed.tech/tags/ai.md>), [best-practices](<https://devfeed.tech/tags/best-practices.md>), [code-review](<https://devfeed.tech/tags/code-review.md>), [communication](<https://devfeed.tech/tags/communication.md>), [developer-experience](<https://devfeed.tech/tags/developer-experience.md>), [ownership](<https://devfeed.tech/tags/ownership.md>), [review](<https://devfeed.tech/tags/review.md>), [summary](<https://devfeed.tech/tags/summary.md>)

### AI overview

Ryan Chandler argues that people should write their own pull request descriptions even when AI agents do most of the implementation. He emphasizes ownership, review context, and the value of concise explanations from the person driving a change over lengthy AI-generated summaries.

### Source excerpt

Ryan Chandler makes a strong case for keeping PR descriptions human-written, even when agents handle most of the implementation. The piece focuses on ownership, review context, and why a concise explanation from the person driving the change is more useful than a long AI-generated summary. Read more

## Readonly Property Defaults in PHP 8.6: A Four-Year-Old Restriction Finally Lifts

DevFeed: [Readonly Property Defaults in PHP 8.6: A Four-Year-Old Restriction Finally Lifts](<https://devfeed.tech/articles/readonly-property-defaults-in-php-8-6-a-four-year-old-restriction-finally-lifts-85150.md>)

Original publisher: [Read original article](<https://freek.dev/3204-readonly-property-defaults-in-php-86-a-four-year-old-restriction-finally-lifts>)

Author: Freek Van der Herten (freek@spatie.be)

Published: 2026-10-12T10:30:50Z

Content type: article

Language: en

Sources: [Freek](<https://devfeed.tech/sources/freek-dev-all-blogposts.md>)

Topics: [PHP](<https://devfeed.tech/topics/php.md>), [extension property](<https://devfeed.tech/topics/extension-property.md>)

Tags: [php](<https://devfeed.tech/tags/php.md>), [php-8-6](<https://devfeed.tech/tags/php-8-6.md>), [php8](<https://devfeed.tech/tags/php8.md>), [property](<https://devfeed.tech/tags/property.md>), [readonly](<https://devfeed.tech/tags/readonly.md>), [rfc](<https://devfeed.tech/tags/rfc.md>), [syntax](<https://devfeed.tech/tags/syntax.md>)

### AI overview

An overview of PHP 8.6's readonly property defaults RFC, including the reason for the previous restriction, the role of interface properties in revisiting it, and practical edge cases.

### Source excerpt

A clear overview of PHP 8.6's readonly property defaults RFC, why the old restriction existed, and why interface properties made it worth revisiting. It also covers the practical edge cases, so you know where the new syntax helps and where it still does not. Read more

## Laravel Context: The Hidden Information That Follows Your Code

DevFeed: [Laravel Context: The Hidden Information That Follows Your Code](<https://devfeed.tech/articles/laravel-context-the-hidden-information-that-follows-your-code-84665.md>)

Original publisher: [Read original article](<https://freek.dev/3203-laravel-context-the-hidden-information-that-follows-your-code>)

Author: Freek Van der Herten (freek@spatie.be)

Published: 2026-10-11T10:31:02Z

Content type: article

Language: en

Sources: [Freek](<https://devfeed.tech/sources/freek-dev-all-blogposts.md>)

Topics: [Laravel](<https://devfeed.tech/topics/laravel.md>), [context](<https://devfeed.tech/topics/context.md>)

Tags: [architecture](<https://devfeed.tech/tags/architecture.md>), [context](<https://devfeed.tech/tags/context.md>), [developer](<https://devfeed.tech/tags/developer.md>), [laravel](<https://devfeed.tech/tags/laravel.md>), [logging](<https://devfeed.tech/tags/logging.md>), [php](<https://devfeed.tech/tags/php.md>), [threading](<https://devfeed.tech/tags/threading.md>), [trace](<https://devfeed.tech/tags/trace.md>)

### AI overview

A walkthrough of Laravel's Context feature, which carries execution-scoped information through an application. It describes how this supports logging, queued jobs, and trace data without passing that information through every method call.

### Source excerpt

A clear walkthrough of Laravel's Context feature and how it lets execution-scoped information travel through your app. It also explains why that matters for logging, queued jobs, and keeping trace data available without threading it through every method call. Read more

## Migrating Pinkary from Laravel Forge to Laravel Cloud

DevFeed: [Migrating Pinkary from Laravel Forge to Laravel Cloud](<https://devfeed.tech/articles/migrating-pinkary-from-laravel-forge-to-laravel-cloud-84466.md>)

Original publisher: [Read original article](<https://freek.dev/3202-migrating-pinkary-from-laravel-forge-to-laravel-cloud>)

Author: Freek Van der Herten (freek@spatie.be)

Published: 2026-10-10T10:30:41Z

Content type: article

Language: en

Sources: [Freek](<https://devfeed.tech/sources/freek-dev-all-blogposts.md>)

Topics: [Laravel](<https://devfeed.tech/topics/laravel.md>), [Cloud](<https://devfeed.tech/topics/cloud.md>), [Eloquent ORM](<https://devfeed.tech/topics/eloquent.md>)

Tags: [database](<https://devfeed.tech/tags/database.md>), [deployment](<https://devfeed.tech/tags/deployment.md>), [laravel](<https://devfeed.tech/tags/laravel.md>), [migration](<https://devfeed.tech/tags/migration.md>), [migrations](<https://devfeed.tech/tags/migrations.md>), [mysql](<https://devfeed.tech/tags/mysql.md>), [sqlite](<https://devfeed.tech/tags/sqlite.md>)

### AI overview

The write-up describes migrating Pinkary from Laravel Forge to Laravel Cloud, including issues caused by differences between SQLite and MySQL, query rewrites, and storage assumptions in the codebase.

### Source excerpt

A practical engineering write-up on moving Pinkary from Laravel Forge to Laravel Cloud. It walks through the real migration issues they hit, including SQLite to MySQL differences, query rewrites, and storage assumptions in the codebase. Read more

## ★ Typed routes from Laravel to React with Wayfinder

DevFeed: [★ Typed routes from Laravel to React with Wayfinder](<https://devfeed.tech/articles/typed-routes-from-laravel-to-react-with-wayfinder-83877.md>)

Original publisher: [Read original article](<https://freek.dev/3088-typed-routes-from-laravel-to-react-with-wayfinder>)

Author: Freek Van der Herten (freek@spatie.be)

Published: 2026-10-09T12:04:12Z

Content type: tutorial

Language: en

Sources: [Freek](<https://devfeed.tech/sources/freek-dev-all-blogposts.md>)

Topics: [Laravel](<https://devfeed.tech/topics/laravel.md>), [JavaScript](<https://devfeed.tech/topics/javascript.md>), [Livewire](<https://devfeed.tech/topics/livewire.md>), [React](<https://devfeed.tech/topics/react.md>)

Tags: [backend](<https://devfeed.tech/tags/backend.md>), [frontend](<https://devfeed.tech/tags/frontend.md>), [laravel](<https://devfeed.tech/tags/laravel.md>), [react](<https://devfeed.tech/tags/react.md>), [typescript](<https://devfeed.tech/tags/typescript.md>), [wayfinder](<https://devfeed.tech/tags/wayfinder.md>)

### AI overview

The post explains how Laravel Wayfinder generates typed TypeScript functions for Laravel routes and controllers. It describes how parameter checking, generated imports, and a Vite plugin help keep frontend calls aligned with backend changes.

### Source excerpt

I've been writing about There There a lot lately. It's a helpdesk we're building at Spatie, born from two decades of running our own customer support for our open source work and SaaS apps. After all that time being the customer of other helpdesks, we finally started on the one we actually wanted to use. Our take on AI here is to aim it at the support agent, not the customer. The human owns the conversation. The model makes the reply a little cleaner and a little faster. There There is in private beta, and you can apply for early access at there-there.app. We're building There There with Laravel and Inertia. One package we've come to rely on is Laravel Wayfinder. It generates typed TypeScript functions for every route and controller in your Laravel app, so the frontend talks to the backend without a single hardcoded URL. This post is about why that matters. Using Wayfinder A React codebase quickly fills up with URL strings. Every fetch, every form action, every link points to a route by way of a template literal. Then you rename a route in Laravel, or add a required parameter, and nothing breaks at compile time. You find out in production, or when a teammate clicks the wrong thing. Wayfinder fixes this by generating a function per named route. You import it and call .url() to build the URL. Here's a snippet from our team membership toggle. import { add as addTeamMember, remove as removeTeamMember, } from '@/routes/app/settings/workspace/teams/members'; removeTeamMember.url({ team: team.ulid, user: member.ulid }); addTeamMember.url({ team: team.ulid, user: member.ulid }); Two things are worth pointing out. First, the parameters are type-checked. If you rename the user route parameter to member, TypeScript catches every caller. Second, the route names map cleanly to import paths, so finding them is just autocomplete. Wayfinder also generates a typed function per controller. We use that when we talk to an endpoint via plain fetch, outside of an Inertia visit. Here's th

## ★ Laravel AI SDK in practice: the agent behind There There

DevFeed: [★ Laravel AI SDK in practice: the agent behind There There](<https://devfeed.tech/articles/laravel-ai-sdk-in-practice-the-agent-behind-there-there-77398.md>)

Original publisher: [Read original article](<https://freek.dev/3089-laravel-ai-sdk-in-practice-the-agent-behind-there-there>)

Author: Freek Van der Herten (freek@spatie.be)

Published: 2026-10-08T10:30:24Z

Content type: tutorial

Language: en

Sources: [Freek](<https://devfeed.tech/sources/freek-dev-all-blogposts.md>)

Topics: [Laravel](<https://devfeed.tech/topics/laravel.md>), [agent orchestration](<https://devfeed.tech/topics/agent-orchestration.md>), [human in the loop agent](<https://devfeed.tech/topics/human-in-the-loop-agent.md>)

Tags: [agent](<https://devfeed.tech/tags/agent.md>), [ai](<https://devfeed.tech/tags/ai.md>), [laravel](<https://devfeed.tech/tags/laravel.md>)

### AI overview

The article shows how Spatie uses Laravel AI SDK to power an AI assistant in its helpdesk product, There There. It describes agent configuration, prompt rendering, callable tools with typed JSON schemas, and delegating ticket operations to domain actions.

### Source excerpt

Over the past few weeks I've posted a couple of times about There There, the helpdesk we're building at Spatie. After two decades of running our own customer support, we decided to stop compromising on tools and build the one we actually want to use. A lot of the fun is on the AI side. We're not using it to replace support agents, we're using it to make them faster. The human reads the ticket, thinks, and clicks a button. The model pulls up relevant history, drafts a reply, tags the ticket, closes a duplicate. There There is in private beta right now, and you can apply for early access at there-there.app. The whole AI layer is built on the new Laravel AI SDK. It's been a joy to work with, and I'd like to walk through how we use it. Using the Laravel AI SDK Everything starts with an agent class. Ours is called ThereThereAgent. It declares which model to use, what the system prompt looks like, which tools the model can call, and what conversation history to replay. Here's a trimmed version. use Laravel\Ai\Attributes\MaxSteps; use Laravel\Ai\Attributes\Temperature; use Laravel\Ai\Contracts\Agent; use Laravel\Ai\Contracts\Conversational; use Laravel\Ai\Contracts\HasTools; use Laravel\Ai\Promptable; #[Temperature(0.3)] #[MaxSteps(10)] class ThereThereAgent implements Agent, Conversational, HasTools { use Promptable; public function __construct( protected Workspace $workspace, protected User $user, protected ?Ticket $contextTicket = null, protected array $conversationHistory = [], ) {} public function model(): string { return config('ai-pricing.default.name'); } public function instructions(): string { return view('prompts.ai.there-there-agent-system', [ 'workspace' => $this->workspace, 'user' => $this->user, 'contextTicket' => $this->contextTicket, ])->render(); } public function tools(): iterable { return [ new ChangeTicketStatusTool($this->workspace), new AssignTicketTool($this->workspace), new AddNoteToTicketTool($this->workspace), new ManageTicketTagsTool($this->work

## ★ Keeping Laravel and TypeScript in sync with data objects

DevFeed: [★ Keeping Laravel and TypeScript in sync with data objects](<https://devfeed.tech/articles/keeping-laravel-and-typescript-in-sync-with-data-objects-66897.md>)

Original publisher: [Read original article](<https://freek.dev/3090-keeping-laravel-and-typescript-in-sync-with-data-objects>)

Author: Freek Van der Herten (freek@spatie.be)

Published: 2026-10-07T10:30:50Z

Content type: tutorial

Language: en

Sources: [Freek](<https://devfeed.tech/sources/freek-dev-all-blogposts.md>)

Topics: [Laravel](<https://devfeed.tech/topics/laravel.md>), [TypeScript](<https://devfeed.tech/topics/typescript.md>), [Continuous Delivery (CD)](<https://devfeed.tech/topics/continuous-delivery.md>), [Visual Studio Code](<https://devfeed.tech/topics/visual-studio-code.md>)

Tags: [build](<https://devfeed.tech/tags/build.md>), [laravel](<https://devfeed.tech/tags/laravel.md>), [spatie](<https://devfeed.tech/tags/spatie.md>), [typescript](<https://devfeed.tech/tags/typescript.md>)

### AI overview

The article demonstrates how a Laravel and TypeScript application can keep backend and frontend types synchronized. It uses Spatie packages to generate TypeScript definitions from PHP data classes, then connects regeneration to Vite file updates so frontend callers receive updated types and compiler feedback.

### Source excerpt

At Spatie we build SaaS apps with Laravel on the backend and Inertia with React on the frontend. That split means two type systems have to agree about every payload that crosses between them. Laravel data going out, TypeScript picking it up. There There, the helpdesk we're building, is built exactly like that. Tickets, messages, members, custom sidebar sections, all of it crosses the bridge. We'd go insane maintaining those types by hand. So we don't. There There is in private beta right now, and you can apply for early access at there-there.app. Two Spatie packages make this painless. spatie/laravel-data shapes outgoing payloads into typed PHP classes, and spatie/laravel-typescript-transformer turns those classes into TypeScript definitions at build time. Let me show what that looks like in practice. Keeping types in sync A payload starts life as a Data class. Here's our MemberData, which we send down every time we render the member detail page. use Spatie\LaravelData\Data; use Spatie\TypeScriptTransformer\Attributes\TypeScript; #[TypeScript] class MemberData extends Data { public function __construct( public int $id, public string $ulid, public string $name, public string $email, public ?string $avatar_url, public WorkspaceMemberRole $role, public string $joined_at, public bool $restricted_channel_access = false, ) {} public static function fromPivotUser(User $user): self { return new self( id: $user->id, ulid: $user->ulid, name: $user->name, email: $user->email, avatar_url: $user->getAvatarUrlWithFallback(), role: WorkspaceMemberRole::from($user->pivot->role), joined_at: $user->pivot->created_at->toIso8601String(), restricted_channel_access: (bool) $user->pivot->restricted_channel_access, ); } } The #[TypeScript] attribute is the opt-in. Any PHP class that carries it is picked up by the transformer. The constructor properties become the TypeScript type, including the enum WorkspaceMemberRole, the nullable string, and the boolean with a default. The transformer it

## ★ Exceptions that explain themselves

DevFeed: [★ Exceptions that explain themselves](<https://devfeed.tech/articles/exceptions-that-explain-themselves-65720.md>)

Original publisher: [Read original article](<https://freek.dev/3091-exceptions-that-explain-themselves>)

Author: Freek Van der Herten (freek@spatie.be)

Published: 2026-10-06T10:30:47Z

Content type: tutorial

Language: en

Sources: [Freek](<https://devfeed.tech/sources/freek-dev-all-blogposts.md>)

Topics: [Custom exceptions](<https://devfeed.tech/topics/custom-exceptions.md>), [Exception handling](<https://devfeed.tech/topics/exception-handling.md>), [Eloquent ORM](<https://devfeed.tech/topics/eloquent.md>)

Tags: [custom](<https://devfeed.tech/tags/custom.md>), [custom-exceptions](<https://devfeed.tech/tags/custom-exceptions.md>), [exceptions](<https://devfeed.tech/tags/exceptions.md>), [explain](<https://devfeed.tech/tags/explain.md>), [laravel](<https://devfeed.tech/tags/laravel.md>)

### AI overview

The article recommends using a dedicated custom exception class for each domain error, with a static factory method for each failure reason. It demonstrates how this approach makes throw sites clearer, preserves typed context in error messages, and keeps expected domain errors out of Laravel error reporting.

### Source excerpt

There There, the helpdesk we're building at Spatie, is a project of learned habits. Twenty-some years of writing Laravel apps has taught us which patterns pay off and which ones quietly rot. One that keeps earning its keep is a custom exception class for every domain error. This is a small pattern, but it's one of those things that makes a codebase nicer to live in. There There is in private beta right now, and you can apply for early access at there-there.app. Exceptions that explain themselves The conventional answer for a domain error is something like throw new InvalidArgumentException("Only notes can be deleted"). It works, the test passes, the user sees a 500 page. But then three months later you try to catch just this specific error and you can't, because InvalidArgumentException is thrown from a dozen other places. Our pattern is one class per domain error, with a static factory method per reason. Here's the one that fires when someone tries to delete a message that isn't a note. namespace App\Domain\Tickets\Exceptions; use App\Domain\Tickets\Models\Message; use Exception; use Illuminate\Contracts\Debug\ShouldntReport; class CouldNotDeleteMessage extends Exception implements ShouldntReport { public static function onlyNotesCanBeDeleted(Message $message): self { return new self("Could not delete message id {$message->id} of type {$message->type->value}. Only messages of type `note` can be deleted."); } } Two things worth calling out. The static method name spells out the failure reason in English, which makes the throw site read like a sentence: throw CouldNotDeleteMessage::onlyNotesCanBeDeleted($message). And the method takes the typed context as a parameter, which makes the message impossible to build without the relevant data. Here's the throw site, inside our DeleteNoteAction. class DeleteNoteAction { public function execute(Message $message): void { if (! $message->isNote()) { throw CouldNotDeleteMessage::onlyNotesCanBeDeleted($message); } // ... delete

## ★ Streaming AI replies from Laravel to React

DevFeed: [★ Streaming AI replies from Laravel to React](<https://devfeed.tech/articles/streaming-ai-replies-from-laravel-to-react-65084.md>)

Original publisher: [Read original article](<https://freek.dev/3092-streaming-ai-replies-from-laravel-to-react>)

Author: Freek Van der Herten (freek@spatie.be)

Published: 2026-10-05T10:30:47Z

Content type: tutorial

Language: en

Sources: [Freek](<https://devfeed.tech/sources/freek-dev-all-blogposts.md>)

Topics: [Laravel](<https://devfeed.tech/topics/laravel.md>), [React](<https://devfeed.tech/topics/react.md>), [json lines format](<https://devfeed.tech/topics/json-lines-format.md>), [vercel ai sdk](<https://devfeed.tech/topics/vercel-ai-sdk.md>), [Event-Streaming](<https://devfeed.tech/topics/event-streaming.md>), [Real-time AI interactions](<https://devfeed.tech/topics/real-time-ai-interactions.md>)

Tags: [agent](<https://devfeed.tech/tags/agent.md>), [ai](<https://devfeed.tech/tags/ai.md>), [ai-sdk](<https://devfeed.tech/tags/ai-sdk.md>), [buffer](<https://devfeed.tech/tags/buffer.md>), [cache](<https://devfeed.tech/tags/cache.md>), [helpdesk](<https://devfeed.tech/tags/helpdesk.md>), [json](<https://devfeed.tech/tags/json.md>), [laravel](<https://devfeed.tech/tags/laravel.md>), [llm](<https://devfeed.tech/tags/llm.md>), [react](<https://devfeed.tech/tags/react.md>), [real-time](<https://devfeed.tech/tags/real-time.md>), [replies](<https://devfeed.tech/tags/replies.md>), [sdk](<https://devfeed.tech/tags/sdk.md>), [stream](<https://devfeed.tech/tags/stream.md>), [streaming](<https://devfeed.tech/tags/streaming.md>), [string](<https://devfeed.tech/tags/string.md>)

### AI overview

A tutorial shows how a Laravel service streams AI chat replies and tool-call events to a React frontend using newline-delimited JSON. It explains buffering partial lines in the browser, updating the chat interface as events arrive, and saving the completed assistant message.

### Source excerpt

A couple of posts back I walked through the agent and tools we built on top of the Laravel AI SDK for There There, the helpdesk we're putting together at Spatie. I ended that post on a small cliffhanger. We hand the agent off to a streaming service that turns the SDK's response stream into events the frontend can consume. That's this post. A quick reminder on our angle. After two decades of running our own customer support, we wanted a helpdesk where AI makes support agents faster, not one that tries to replace them. The human reads, thinks, and directs. The model drafts and retrieves in real time while they watch. There There is in private beta right now, and you can apply for early access at there-there.app. Streaming from Laravel to React The obvious way to hand an LLM response to the browser is to wait for it to finish, then render the whole thing. That's easy, but it makes the agent feel sluggish. What we actually want is for the reply to appear word by word, and for the agent's own reasoning (like which tool it's calling) to be narrated along the way. The Laravel AI SDK exposes each step of a conversation as a typed event. We iterate over that stream and emit newline-delimited JSON for the frontend, one line per event. Here's the core of our AgentStreamingService. public function stream(Agent&HasTools $agent, string $message, AgentChat $chat): StreamedResponse { return response()->stream(function () use ($agent, $message, $chat): Generator { yield from $this->streamAgent($agent, $message, $chat); }, 200, [ 'Content-Type' => 'application/x-ndjson', 'Cache-Control' => 'no-cache', ]); } private function streamAgent(Agent&HasTools $agent, string $message, AgentChat $chat): Generator { set_time_limit(120); $fullContent = ''; $toolCalls = []; foreach ($agent->stream($message) as $event) { if ($event instanceof ToolCall) { yield json_encode(['type' => 'tool_call', 'tool_name' => $event->toolCall->name])."\n"; } if ($event instanceof TextDelta) { $fullContent .= $even

## How to Stop an AI Agent from Destroying Your Laravel App

DevFeed: [How to Stop an AI Agent from Destroying Your Laravel App](<https://devfeed.tech/articles/how-to-stop-an-ai-agent-from-destroying-your-laravel-app-64625.md>)

Original publisher: [Read original article](<https://freek.dev/3117-how-to-stop-an-ai-agent-from-destroying-your-laravel-app>)

Author: Freek Van der Herten (freek@spatie.be)

Published: 2026-10-04T10:30:38Z

Content type: tutorial

Language: en

Sources: [Freek](<https://devfeed.tech/sources/freek-dev-all-blogposts.md>)

Topics: [Laravel](<https://devfeed.tech/topics/laravel.md>), [AI Agent](<https://devfeed.tech/topics/ai-agent.md>)

Tags: [agent](<https://devfeed.tech/tags/agent.md>), [ai](<https://devfeed.tech/tags/ai.md>), [best-practices](<https://devfeed.tech/tags/best-practices.md>), [hardening](<https://devfeed.tech/tags/hardening.md>), [how-to](<https://devfeed.tech/tags/how-to.md>), [isolation](<https://devfeed.tech/tags/isolation.md>), [laravel](<https://devfeed.tech/tags/laravel.md>), [practical](<https://devfeed.tech/tags/practical.md>), [production](<https://devfeed.tech/tags/production.md>), [security](<https://devfeed.tech/tags/security.md>), [workflow](<https://devfeed.tech/tags/workflow.md>)

### AI overview

The post describes safeguards for protecting Laravel projects from destructive AI agent behavior, drawing on the PocketOS incident. It covers deny rules, credential isolation, and production guardrails.

### Source excerpt

A practical post on hardening Laravel projects against destructive AI agent behavior. It walks through the PocketOS incident and shows concrete safeguards like deny rules, credential isolation, and production guardrails. Read more

## I'm Using GPUI For Everything

DevFeed: [I'm Using GPUI For Everything](<https://devfeed.tech/articles/i-m-using-gpui-for-everything-64428.md>)

Original publisher: [Read original article](<https://freek.dev/3200-im-using-gpui-for-everything>)

Author: Freek Van der Herten (freek@spatie.be)

Published: 2026-10-03T10:31:04Z

Content type: article

Language: en

Sources: [Freek](<https://devfeed.tech/sources/freek-dev-all-blogposts.md>)

Topics: [Publishing](<https://devfeed.tech/topics/publishing.md>)

Tags: [gpui](<https://devfeed.tech/tags/gpui.md>), [rust](<https://devfeed.tech/tags/rust.md>), [tooling](<https://devfeed.tech/tags/tooling.md>), [video](<https://devfeed.tech/tags/video.md>)

### AI overview

A Syntax team video discusses why they are using GPUI across more of their work and what makes it appealing for modern tooling.

### Source excerpt

A video by the Syntax team on why they're using GPUI across more and more of their work. It offers a practical look at what makes GPUI appealing for modern tooling.

## 15 years of Packagist: Over 200 billion package installs

DevFeed: [15 years of Packagist: Over 200 billion package installs](<https://devfeed.tech/articles/15-years-of-packagist-over-200-billion-package-installs-63489.md>)

Original publisher: [Read original article](<https://freek.dev/3199-15-years-of-packagist-over-200-billion-package-installs>)

Author: Freek Van der Herten (freek@spatie.be)

Published: 2026-10-01T10:30:28Z

Content type: article

Language: en

Sources: [Freek](<https://devfeed.tech/sources/freek-dev-all-blogposts.md>)

Topics: [Composer](<https://devfeed.tech/topics/composer.md>), [supply-chain-security](<https://devfeed.tech/topics/supply-chain-security.md>)

Tags: [composer](<https://devfeed.tech/tags/composer.md>), [package](<https://devfeed.tech/tags/package.md>), [packagist](<https://devfeed.tech/tags/packagist.md>), [php](<https://devfeed.tech/tags/php.md>), [supply-chain](<https://devfeed.tech/tags/supply-chain.md>), [supply-chain-security](<https://devfeed.tech/tags/supply-chain-security.md>)

### AI overview

A retrospective on Packagist's first 15 years, covering its early Composer experiments, more than 200 billion package installs, recent supply chain security work, and future plans.

### Source excerpt

A look back at Packagist's first 15 years, from the first Composer experiments to more than 200 billion package installs. It also covers the team's recent supply chain security work and what they're building next. Read more

[Next page](<https://devfeed.tech/sources/freek-dev-all-blogposts.md?cursor=WyIyMDI2LTEwLTAxVDEwOjMwOjI4KzAwOjAwIiwgImE5NzEwY2E3LTllMGMtNDAzMC04Y2Y1LWY1NzQ4ZWM5ZWVlYiJd>)