▸ Analyst and software engineer, Geneva
I work on humanitarian data analysis and tooling for crisis response. Assessment reports, funding flows and situation PDFs turned into something a coordinator can act on while it still matters.
Otherwise I build:
▪ AI systems and RAG
▪ Automation and workflow engineering
▪ Data pipelines and dashboards
▪ Web applications and performance
→ Writing: https://t.co/B3AYEjPx0s
→ Work: https://t.co/Efq3RbKnri
I write up my own failures as well.
For code projects, I use 3 Claude Code sessions. A lead keeps the list of work and merges, a dev session writes the code on a branch, and a review session checks each change before it is merged. This catches mistakes that a single session misses, but only if each session knows its role and they do not edit the same files.
So every session starts by reading its role from the project’s CLAUDE.md and AGENTS.md. Dev and review each work in their own git worktree, and review never edits the code. In a test run, review sent the first version back with a finding, dev fixed it, and the change was merged in 152 seconds for $2.11. The Claude Code Workstation Kit creates these files from its templates when you create a project, and the guide has a chapter on running several sessions on one repository.
If you want Claude to plan, build and review, and not only write code, this is the set-up. The waitlist closes on Friday 27 November at 18:00 CET: https://t.co/G6ImSbX4SY
When Claude Code runs inside WSL, your projects on C: are reached through /mnt/c. Sometimes that link breaks while WSL keeps running. Every path on C: then returns an error, and a Claude session working there reports that its folder was deleted, although nothing was deleted. This is a known WSL bug that is still open. The usual fix is to shut WSL down, which closes every session and every dev server you had open.
The Claude Code Workstation Kit has a mount check for this. It checks the drive every 30 seconds and, when it has dropped, mounts it again without a restart. It then tells you in your tmux window which sessions need to reopen their folder, so the rest keep running. kit-doctor tells you if the check itself has stopped. Projects on the Linux disk never use this link, and the kit can move them there for you.
That is the second of the kit’s 3 fixes. The waitlist closes on Friday 27 November at 18:00 CET: https://t.co/G6ImSbWx3q
The kit is 8 tools, measured settings and templates, and a guide of about 40 pages. People on the waitlist get it first. I will send 1 email, when it is ready, and every 1.x release is free.
The waitlist closes on Friday 27 November at 18:00 CET.
Leave your email to join the waitlist:
https://t.co/rQsa69af2k
1 licence covers 5 computers that you use yourself, including paid work for clients. You can read and change the scripts for your own use, and the AGENTS.md, CLAUDE.md and projects.yaml files the kit creates are yours.
The memory and mount tools are also published under the MIT licence, and every 1.x release is free.
Check out the launch offer and join the waitlist:
https://t.co/IQkTBwPzhZ
Each project keeps its own session, so Claude keeps working in one while I look at another. project app opens a project, or switches to it if it is already open.
Closing the window does not stop the sessions. pstatus shows which ones are working and what they cost, and project-stop app closes one when I am done.
Check out the launch offer and join the waitlist:
https://t.co/acPVTWdoZv
This is a normal day with the kit. In the morning, project app opens the project’s folder, its windows and its Claude session. While I work, I switch between projects, and Claude keeps working in the others.
After a restart, claude-recover brings every session back with its conversation. In the evening, project-stop app closes that project’s session.
Check out the launch offer and join the waitlist:
https://t.co/HZ2ZeuVCr8
I do not install anything on my machine without knowing what it will change, and the kit works the same way. Every installer prints what it will change and asks before it changes anything, and --remove takes out exactly what it added.
proj-move changes nothing until you tell it to, and kit-doctor tells you which part has stopped. Admin rights are needed once, to install WSL, and never after that.
Check out the launch offer and join the waitlist:
https://t.co/sbBwdFhcj2
These are the 6 commands I type in a day. project new client-a --type app adds a project from 1 of 6 templates (development, website, app, research, design and data) and opens it. project app opens that project’s tmux session, and pstatus shows every session’s state, model, context and cost.
After a reboot, claude-recover brings back every session with its conversation. kit-doctor tells you which part has stopped, and project-stop app closes the project when I am done.
Check out the launch offer and join the waitlist:
https://t.co/D2kBMPPsaz
The kit is for Windows 11, or Windows 10 with WSL2, running Ubuntu built on 26.04 LTS. It needs 16 GB of RAM for 2 or 3 projects, and a Claude Pro or Max plan or an API key.
Admin rights are needed once, to install WSL; the kit itself never needs them. It works with the tools you already use: tmux, Herdr, cmux or the desktop app. It is not for macOS or Linux in this version.
Check out the launch offer and join the waitlist:
https://t.co/aMiB8UoVu2
The kit is 8 tools, measured settings and templates, and a guide of about 40 pages. The tools are the 3 fixes (memory watch, mount check and claude-recover) and 5 more: project, project new, pstatus, proj-move and kit-doctor.
It also includes a measured .wslconfig, and settings and CLAUDE.md templates. The guide covers what failed, what the logs showed and what fixed it. Every installer asks first, --remove takes it out again, and every 1.x release is free.
Check out the launch offer and join the waitlist:
https://t.co/VHWQtvsOvO
Every project I work on needs the same things each time: its folder, its terminal windows and its Claude session. So each one now has its own tmux session.
project app opens it, or switches to it if it is already open. Closing the window does not stop anything, and Claude keeps working in the other projects. project-stop app closes it when I am done, and adding a project is 1 entry in projects.yaml.
Check out the launch offer and join the waitlist:
https://t.co/MbBl7HlZjK
The .wslconfig decides how much of the machine’s memory WSL2 can take from Windows. The one in the kit was measured on my own machine, and the guide explains why each value is set as it is.
With the settings and CLAUDE.md templates, every session starts knowing its role, what it owns and what it must never do. Each project runs as few sessions as the work needs, and after a restart nothing has to be explained again.
Check out the launch offer and join the waitlist:
https://t.co/w6ef2fh2DA
A reboot or a crash closes every tmux session and every Claude conversation with it. Terminal tools that restore your tabs do not restore what was running in them.
claude-recover brings back every project and every session with 1 command, and each Claude session resumes its conversation where it stopped.
Check out the launch offer and join the waitlist:
https://t.co/Ug9URLDSEM