Urgent.News

What's breaking now, across thousands of outlets.

Tech

Echoes of the Terminal: a haunted shell that runs on your own machine

This is a submission for the Hacktoberfest Open-Source AI Challenge Week 4: Ghost in the Machine What I Built Echoes of the Terminal is a shell that answers back. You type git push --force . The command runs, and then something in the terminal speaks: Are you sure you want to rewrite history, mortal? The dead do not like being disturbed, and your teammates' commits will not rest quietly. That…

This is a submission for the Hacktoberfest Open-Source AI Challenge Week 4, titled "Ghost in the Machine". The project is called "Echoes of the Terminal", a shell that responds to your commands. When you type "git push --force .", the terminal replies with a warning: "Are you sure you want to rewrite history, mortal?" This is produced by an open-weight model running on your own machine, which monitors each command you input, along with its exit status, current directory, git branch, time, and previous command.

The system warns about dangerous commands like "rm -rf node_modules" while remarking about your "sterile existence" for harmless ones like "ls" or "pwd". Failures receive smug responses. There are two versions of this shell: a web shell with a CRT-like appearance, and "haunt", a command-line interface that takes control of your real shell. To use "haunt", you simply type "haunt git push --force" or integrate it with bash or zsh for commentary on every command you type.

The software takes a literal approach to its haunted theme, ensuring each warning accurately reflects the command's impact. For instance, a warning about "rm -rf" still provides true information. There's also a "séance mode" that allows the software to take over, shouting "PAYROLL BUREAUCRACY" when you comment in different programming languages.

The project is available at echoes-of-the-terminal.vercel.app. You can try commands like "git push --force", "rm -rf node_modules", and "cat .env" in the shell. Running "seance cobol" after that will demonstrate the system's capabilities. The shell is simulated, so nothing you type affects your machine. To activate a real model, open the sieance board and select one. The scripted ghost speaks until a model is recognized.

Written by urgent.news from Dev.to's reporting — not their text. Machine-written — may contain errors; check the original before relying on it.

Read the original at dev.to →

More in Tech

Your agent crashed after the write. Should you retry?

The hardest moment in an automation often sits between two acknowledgements: the target accepted the change, but the executor has not recorded completion.

  • Automation process fails to record completion after executor crash.
  • Local tests on October 27, 2026, showed 22 out of 22 tests passed.
  • Recovery process classifies as "reconciled" without altering target.

You own the code: what that sentence has to mean in writing

Why the sentence alone is not enough If an agency's site says you own the code, that line sits on a sales page, and a sales page is not your agreement. What counts is what the signed paper says.

  • Ownership of code begins with the author, not the paying agency.
  • Work made for hire requires a written agreement from both parties.
  • Ensure repository and domain are under your business's control.

GRANT ALL to anon is the wrong fix for Supabase 42501 after Oct 30

From Oct 30, 2026, Supabase will apply a change to existing projects: new tables in public won't be visible to the Data API until you grant access.

  • Supabase changed on Oct 30, 2026, to restrict public schema tables without explicit grant.
  • Granting all privileges to anon role is incorrect fix due to unnecessary privileges for visitors.
  • Enable RLS, grant specific verbs per table, and review older tables' grants for alignment.

More from Tuesday 27 October →