filament-kanban
Add kanban boards to your Filament pages
Runssource: GitHubhomepagePHPMITcommit 76bd44d71dc0
PHP, MIT licensed. The project labels itself: filament plugin, filamentphp, kanban, kanban board and laravel.
filament-kanban runs. An Argusic agent installed it in 3 minutes and hit 2 errors and fixed every one without help on a clean machine with no GPU, and the whole session was recorded.
Dependencies install cleanly, the full 17-test Pest suite passes (17 passed, 27 assertions), the filament-kanban:install command publishes assets and exits 0, the make:kanban command generates a KanbanBoard subclass, and npm run build produces the minified filament-kanban.css asset.
What the agent ended up with on a clean machine, in its own words. How this is measured
Measured by Argusic on a fresh machine every time. Every number links to its evidence. Argusic Score 100 of 100 (the mean of this project's run scores).
At a glance
Subject data from GitHub, linked at the top of this page, refreshed . Test data by Argusic (CC BY 4.0); every number links to a run page with the full log, the recording, and their sha256 hashes.
What was measured
From the run that decided this verdict. Every line is a recorded value, not an estimate.

What went wrong, in the agent's own words
The agent's own words, worst first, never rewritten into advice.
- Container had no PHP and no root to apt install it (Ubuntu 24.04, runner user)2 minutes
- composer install was blocked by Composer 2.11's new security-advisory policy rejecting older Laravel 10/11 releases required by orchestra/testbench (repo has no composer.lock)1 minute
- Install time
- 3 minutes
- Cold machine to finish
- 5 minutes
- Errors hit and fixed
- 2 hit, 2 fixed with no human help
- How the result was proved
- composer test exited 0 with 'Tests: 17 passed (27 assertions), Duration: 1.13s'; vendor/bin/testbench about reports Laravel 11.57.0 on PHP 8.2.32; vendor/bin/testbench filament-kanban:install printed 'filament-kanban has been installed!'; vendor/bin/testbench make:kanban DemoBoard printed 'Kanban page [app/Filament/Pages/DemoBoard.php] created successfully.'
- Model tokens used
- 263,348
- Exact commit tested
- 76bd44d71dc0
- Container image
- sha256:cdd920bce783
What was not measured
The other half, so you can see exactly how far this evidence goes. A gap is printed as a gap and never filled in.
- Peak GPU memory
- this ran on a CPU machine, so there was no GPU to sample
- Behaviour over a long run
- each attempt uses the smallest documented settings and a fixed time budget, so this measures whether it runs, not how it holds up under load
Watch the session
The whole run, from a clean machine, at the speed it actually happened. Nothing is cut and nothing is sped up.
A recording of attempt 1, run , the attempt that decided the verdict above. The terminal recording it was made from is the evidence, stored with a sha256 fingerprint; the video is a rendering of it. Nothing loads from the video host until you press play.
The end of the recording
The last lines of the terminal session that decided this verdict, exactly as they were recorded.
-rw-rw-r-- 1 runner runner 748 Oct 20 13:33 vendor/autoload.php -rwxrwxr-x 1 runner runner 3321 Oct 20 13:33 vendor/bin/pest === overlay 40G 1.3G 39G 4% / exec /bin/sh -lc 'date -u +%H:%M:%S' in /work/repo succeeded in 0ms: 13:35:27 All done. This is a PHP/Laravel Filament package (`mokhosh/filament-kanban`), not a desktop app. Sc… tokens used 263,348 All done. This is a PHP/Laravel Filament package (`mokhosh/filament-kanban`), not a desktop app. Sc…
Replay the whole session, every command from a clean machine to this point.
How it was tested
One agent, one container, no human help. It installs the project the way its own documentation says to, runs it, and fixes what breaks. Everything below is recorded as it happened: the terminal session, the log and the exact commit. The full method.
Strengths and limits
Measured facts, not opinions. How this is written.
What went well
- Reached a running state on a clean machine, with the session recorded.
- Installed in 3 minutes.
- Recovered from all 2 errors without a human stepping in, which says the failures are documented well enough to solve.
- Ran without a GPU, so it does not need one to start.
- Licensed MIT, as reported by its host.
What did not, or is not known
- Measured once so far. A single attempt shows it can run, not that it runs reliably.
What it is a reasonable choice for
- Trying it on a laptop or a small server: it reached a running state without a GPU.
- A quick evaluation: it was running 3 minutes after the clone.
Also tested, in the same area
Every one of these was installed and run by Argusic on a clean machine. Nothing appears here that was not tested.
Run history
Topics (from GitHub)
Embed the badge
Markdown for the project README. It links back here; terms on the terms page.
[](https://argusic.com/subject/filament-kanban)Questions
- Does filament-kanban run?
- Yes. filament-kanban runs. Argusic installed and launched it on a clean machine in 3 minutes, hitting 2 errors on the way, and recorded the session.
- How did Argusic test filament-kanban?
- On a fresh, disposable machine, with every command recorded and the repository pinned at commit 76bd44d71dc0. One attempt is recorded, and the full method is on the methodology page.
- What did it cost to test filament-kanban?
- The run that produced this verdict cost $0.07: real compute and model cost, not a list price per million tokens. It is recorded on that run's page.
- How long does filament-kanban take to install?
- 3 minutes in the run that decided this verdict, from a clean machine to a running state. That is one measured attempt, not an average.
- Does filament-kanban need a GPU?
- Not to start. Argusic reached a running state on a machine with no GPU.
- What goes wrong when installing filament-kanban?
- 2 things broke in the recorded run, and 2 were fixed without human help. Each one, and the time it cost, is listed on this page.
- Where is the evidence for filament-kanban?
- The recorded run is on this page, each linking to its full log and terminal recording, stored with a sha256 fingerprint so it cannot be quietly altered.