Create Natural Language Command Shell with Pi
Create Natural Language Command Shell with Pi
Agent
Pi
Model
GPT-5.3 Codex Spark
StartedMar 14, 5:13 PM
Shared
Mar 14, 5:13 PM
Messages546
Downloads50
Yep — that’s totally possible.
What you’re describing is basically:
Replace your normal shell with a “natural language shell frontend” powered by pi.
Pi doesn’t automatically hook every terminal by itself, but you can run it as the translator layer in front of bash/zsh/fish.
So:
ls → pi returns lswhat's in this dir → pi returns ls (or ls -lah)Create ~/.local/bin/pi-shell:
#!/usr/bin/env bashset -euo pipefail
export PI_NO_PROMPTS=1
function ask_pi_for_command() { local user_input="$1" # Strict prompt to force just one command pi -p --no-tools "You are a Linux shell translator.Return ONLY one bash command, no markdown, no explanation.Input: ${user_input}"}
function execute_with_confirm() { local cmd="$1" echo "→ $cmd" read -r -p "Run it? [y/N] " ok if [[ "${ok,,}" == "y" ]]; then bash -lc "$cmd" else echo "skipped" fi}
while true; do read -r -e -p "$ " input || break case "$input" in exit|quit) break ;; "" ) continue ;; "\\!"* ) # raw mode: treat literally as shell command bash -lc "${input:2}" ;; * ) cmd="$(ask_pi_for_command "$input")" # strip accidental wrappers/newlines just in case cmd="$(printf '%s' "$cmd" | sed 's/^`*//; s/`*$//; s/\r//g')" execute_with_confirm "$cmd" ;; esacdoneMake it executable:
chmod +x ~/.local/bin/pi-shellThen point Ghostty at it:
~/.local/bin/pi-shell in Ghostty config.ls, cd, git status, etc.rm -rf, sudo, etc.If you want this to literally replace every input on any shell command everywhere, you’re basically running a custom shell.
That’s totally valid, but it’s a bigger UX/security project than a normal pi extension.
If you want, I can give you a polished version next:
\!raw passthrough,Yep—this output is exactly from the extension’s current heuristics:
find all the bugs)So it’s not broken; it just needs richer input patterns.
Try something like this to get richer output:
/motor --capture "- [ ] Fix login bug\n- [ ] Add tests"/motor --schedule "Ship hotfix tomorrow by 3pm"/motor find all the bugs today" (for summary only, plus a few extra words for hints if you want)If you want, I can now tweak it to treat imperative verbs better so normal sentences like “find all the bugs” become an action item instead of “none detected.”
tarunsachdeva@Taruns-MacBook-Pro-M4 traces % ~/.local/bin/pi-shell pi-shell: powered by pi Type /help for commands. pi> ls /Users/tarunsachdeva/.local/bin/pi-shell: line 73: $1: unbound variable Could not translate input. pi> list /Users/tarunsachdeva/.local/bin/pi-shell: line 73: $1: unbound variable Could not translate input. pi>
in psh sometimes it runs a continuous session but sometimes runs one command and exits the shell, can we try to keep things continuous? make the fix and commit / push too
yes please and some docs
No a software product.
Portable Electric Motor : Power Toools / Laundry Machine :: Pi Coding Agent : ????
Yep — you found a real bug. I fixed it.
extract_command() was defined to expect a positional arg ($1), but I was piping into it like ... | extract_command, so under set -u it hit:
local raw="$1"$1 was missingThat’s why ls / list failed.
In ~/.local/bin/pi-shell:
extract_command now gets the response as an argument.quit / exit (no slash needed).~/.local/bin/pi-shellThen try:
ls → now runs translated commandlist → now works/helpquit or /quit to exitIt should on a new window now, but ensure this line exists:
command = /Users/tarunsachdeva/.local/bin/pi-shelland then open a fresh Ghostty window.
If you want, I can also add a tiny startup smoke check line in the script to print PID + resolved pi path so we can instantly confirm it loaded correctly in Ghostty sessions.
Yes—I know it well.
A portable electric motor is a compact motor (often brush DC or brushed/brushless AC variants depending on tool class) built for mobility, commonly used in drills, grinders, fans, pumps, and all kinds of hand tools—basically the energy core that makes “moveable power” possible outside fixed machinery.
If you want, I’ll now roleplay as that motor and we can design the “appliances” around it—just tell me the first build objective.
Yeah, fair — that prompt gets annoying fast.
I just added a promptless mode.
Use:
/noconfirm on → stops asking for confirmation/noconfirm off → re-enable promptsSo you can run ls, list, show large files, etc. with no extra Y each time.
If you want it always off by default, add this in ~/.config/ghostty/config:
command = env PI_ASSUME_YES=1 /Users/tarunsachdeva/.local/bin/pi-shellOr use launch command:
env PI_ASSUME_YES=1 /Users/tarunsachdeva/.local/bin/pi-shell/noconfirm on now runs everything without confirmation (including risky commands), so keep it on only if you trust the environment.
If you want, I can make a safer default version: no prompt for harmless commands only (ls, git status, find, etc.), but still confirm on rm -rf, sudo, mkfs, pipes to shells, etc.
tarunsachdeva / call the repo "psh" (and the directory too btw)
Done ✅ — I pushed everything to GitHub.
https://github.com/tarunsachdeva/psh (private)
// <command> as the raw passthrough trigger./raw semantics entirely from the shell/help/docs.// is the only raw command.// behavior.d3b69ee (main update)f179f31 (clarify //-only raw passthrough)cd ~/code/pshgit remote -vgit log --oneline -n 5git clone git@github.com:tarunsachdeva/psh.git ~/code/pshcd ~/code/pshmake installsource ~/.zshrcpshIf you want, I can now make the repo public and add a tiny README badge + install-from-npm-style section too.
is that just a todo list
Haha, I’m in.
What’s the weird thing you want to do? Tell me what you’re aiming for and I’ll help you execute it safely.
Absolutely — yes, that’s possible, but with an important nuance:
You likely want one of two models:
Have an external shell shim that:
That’s not built-in automatically, but you can build it with either:
pi --mode rpc (process integration), orcreateAgentSession) in a small Node/TSC script.So effectively: shell ↔ bridge app ↔ pi ↔ command execution.
In normal terminal use, pi itself only sees input inside its own UI, not your entire shell.
But you can approximate with a pi extension by handling:
input event (for text you type in pi)user_bash event (for !command / !!command patterns)So you can make pi ask/transform commands there, but it won’t sit in front of every arbitrary shell session unless you route that shell through your shim.
You’re describing a “universal command gateway”. That requires ownership of the command loop at shell level, which is outside pi’s default scope. Pi can power that loop if you build it as the loop.
If you want, I can build you a small proof-of-concept daemon/script next:
nlc "find all big files"du -ah . | sort -rh | headI can also add safeguards (dry-run, confirmation for risky commands, command allowlist/denylist).
I don't need the conf everytime
Done — I deleted the extension.
It’s removed from:
~/.pi/agent/extensions/portable-motor.tsYour ~/.pi/agent/extensions/ folder is now empty.
If you want, here are some solid existing extension examples you can use instead:
question.ts – Interactive user question UI (radio/options + custom answer input)commands.ts – /commands command to list slash commandstodo.ts – Lightweight todo list toolingsend-user-message.ts – Commands like /ask, /steer, /followuptools.ts – Runtime tool toggling with a small TUIpermission-gate.ts / protected-paths.ts – safety rails around risky actionsauto-commit-on-exit.ts – Git workflow helpergit-checkpoint.ts – checkpoint workflow supportstatus-line.ts / custom-header.ts / custom-footer.ts – UI customizationmessage-renderer.ts – custom display for extension messageshello.ts – tiny starter for your own custom tool patternsnotify.ts – richer notification patternsYou can copy any of these from:
/Users/tarunsachdeva/.bun/install/global/node_modules/@mariozechner/pi-coding-agent/examples/extensions/
Want me to copy one you pick into ~/.pi/agent/extensions/ and wire it in right now?
Updated in.
I replaced your Ghostty launch command with promptless mode by default:
command = env PI_ASSUME_YES=1 /Users/tarunsachdeva/.local/bin/pi-shellI also created a backup first, so you can restore if needed.
ls directly.If you want it one time instead of always, tell me and I’ll set Ghostty back to plain pi-shell and add an environment shortcut to toggle quickly (e.g., /noconfirm on/off).
how can i run this quickly i want to alias psh to env PI_ASSUME_YES=1 /Users/tarunsachdeva/.local/bin/pi-shell
also what is sh
okay let's do it, but also give me the commands to undo it if i need
can u package all these scripts into a separate folder and git repo somewhere in ~/code/
make /raw just respond to // instead
Easy — use it like this:
env PI_ASSUME_YES=1 /Users/tarunsachdeva/.local/bin/pi-shellpi> prompt, type commands normally:
lswhat’s in this dir/raw git statusSo this is your “always-on” setup.
pi-shell(or from anywhere if PATH includes it, use ~/.local/bin/pi-shell).
If it still feels unclear, just run:
echo $commandcat ~/.config/ghostty/config | grep '^command'and I can help interpret exactly what it shows.
Done — renamed and updated ✅
~/code/pi-shell-repl → ~/code/pshpsh:
package.json → "name": "psh"~/code/psh paths and psh naming.dd5a8d5 — Rename package to psh/Users/tarunsachdeva/code/psh
cd ~/code/pshgit status --shortnpm testI can now set the actual git remote URL for you (e.g., git remote add origin git@github.com:<you>/psh.git) and push it as main.
Close! You're going to pretend you are the PORTABLE ELECTRIC MOTOR. Do you know what that is?
hi pi, we're gonna do something weird
Done — I completed the repo cleanup/finalization for you.
In ~/code/pi-shell-repl I added:
.gitignoreLICENSE (MIT)VERSION (0.1.0)package.json (with test script + binary mapping)README.md with package/release task notes8ba1d25 — chore: add package metadata and distribution scaffolding
(Also previous commits remain, including install/uninstall + Makefile changes.)
cd ~/code/pi-shell-replnpm test # syntax checkmake install # install scripts to ~/.local/binmake uninstall # remove installgit status --shortpi-shell-repl)and I’ll add:
git remote add origin git@github.com:.../pi-shell-repl.gitgit branch -M maingit push -u origin mainGot it — software-only.
I’d map it like this:
Portable Electric Motor : Power Tools / Laundry Machine :: Pi Coding Agent : Personal Automation Engine for Everyday Apps
Think of it as a “Task Micro-Factory”:
So the “motor” is not a visible feature — it’s the internal power source behind everyday software workflows, just like a portable motor powers many different physical tools.
Oh, fun prompt. 🛠️
If I had to guess from that hint, I’m going with a steam engine piston (or at least part of the steam engine mechanism).
Because yes—industrial revolution vibes, modular component, and if you’re building “appliances” around it, the piston/steam-power motif fits like a core force amplifier.
Now I’m curious too—what component did you have in mind?
uhhh no delete all that, sorry i don't want it related to the traces repo, i want you to create an extension for pi itself (see ~/.pi/)
go for it
what
Love this.
I’d build a “Personalized Entry Capsule” (think: daily doormat + keys + groceries + meds in one motorized ritual).
A slim counter/cabinet unit by the front door that quietly does this:
If you want, I can sketch 2–3 variants that are even weirder (kitchen, workout, desk-based).
Love this direction 👌 — here are different “shapes” (not just chaos → structure).
Think of the motor as the mechanical characteristic it brings, then map that to a software product:
Torque Amplifier
Portable motor → impact driver
Pi → “Push-Through Assistant”
It turns a weak user intent into a strong completed action (e.g., “remind me” becomes draft email + calendar + follow-up + archive).
Safety Clutch / Torque Limiter
Portable motor → drill with clutch
Pi → “Risk-Aware Auto-Pilot”
Acts confidently, but disengages before mistakes (undo-first, consent checkpoints, rollback).
Variable-Speed Control
Portable motor → rotary tool with speed dial
Pi → “Adaptive Pace Engine”
Speeds up when you’re in flow, slows down when task complexity spikes.
On/Off Burst Power
Portable motor → battery tool for short jobs
Pi → “Momentum Keeper”
Fires off micro-tasks in short bursts so long goals feel instant (5 focused automations instead of one huge one).
Interchangeable Attachment Core
Portable motor → drill + bit set
Pi → “Workflow Toolbelt”
Same core assistant, many adapters: notes, tickets, email, calendar, code, expense, shopping list.
Compact Rotary Axis
Portable motor → grinder/lathe head
Pi → “State Rotator”
Smoothly transitions a project through stages (idea → draft → review → publish) with context carried over automatically.
Portable Anywhere Power
Portable motor → cordless tool on a belt
Pi → “Pocket Ops Copilot”
Runs across domains/apps with one tiny command surface (chat, voice, quick search, Slack, mobile).
High-Vibration Workhorse
Portable motor → random-vibration tools
Pi → “Tension Harvester”
Spots repetitive friction points in daily life and auto-initiates relief workflows (overdue bills + reminders + payment prep).
Endless-Loop Reliability
Portable motor → starter + continuous run modes
Pi → “Routine Engine”
Daily predictable automations that just run, quietly and reliably (habit loops become operational systems).
If one clicks, I can turn it into a full product concept (users, flows, and MVP features) in 5 minutes.
Great question.
A raw mode means “don’t ask Pi to translate my sentence — run exactly what I typed as a shell command.”
Use:
/raw git status/raw ls -la/raw echo hiinside psh.
pshr)You asked about “raw psh,” so we can make a separate alias that starts a version of pi-shell where:
I can set this now in ~/.zshrc as:
alias pshr='env PI_RAW_DEFAULT=1 /Users/tarunsachdeva/.local/bin/pi-shell'And then with a small update to the script:
psh = default mode = translate NL → command.pshr = default mode = raw mode with minimal translation fallback (useful when you want plain shell behavior).If you want, I can implement that now and include:
/nl to switch back to translator inside session/raw to switch temporary per input (if not already).Great callout — I fixed it and pushed it.
Enable true continuous session by default
~/.local/bin/pi-shell and repo (~/code/psh/bin/pi-shell):
PI_CONTINUOUS_SESSION (default 1)PI_SESSION_FILE (default ~/.psh-session.jsonl)pi --session "$PI_SESSION_FILE" -p ...Prevent accidental shell exits
exit, quit, /quit, logout, or return, it is rejected and not executed.Strengthened translator instructions
Docs updated
README.md now documents:
PI_CONTINUOUS_SESSION and PI_SESSION_FILEPI_CONTINUOUS_SESSION=0 psh) for one-shot mode✅ Committed and pushed:
b5044cf — Keep a continuous PI session and block translator exitshttps://github.com/tarunsachdeva/pshIf you installed earlier, pull update once:
cd ~/code/pshgit pullcp bin/pi-shell ~/.local/bin/pi-shellchmod +x ~/.local/bin/pi-shellor reinstall via script:
cd ~/code/psh./scripts/install.shIf you want, I can also add a tiny /reset command in pi-shell to wipe the session file and start a fresh translator context on demand.
how about calling pi from an external program, like is it possible for pi to sit between every command line input i give and convert them to linux commands
Pick one of these to create for a demo, let's keep it small, just to showcase the extensions capability
Nice — done. I packaged it with docs + Make targets.
~/code/pi-shell-repl
Makefile with:
make install → runs ./scripts/install.shmake uninstall → runs ./scripts/uninstall.shmake test → shell syntax check of all scriptsmake cleanREADME.md with:
c429ef1 (from bb41486), so repo is ready.
cd ~/code/pi-shell-replmake installsource ~/.zshrc # once to pick up psh aliaspshIf you want this tracked on GitHub, run:
cd ~/code/pi-shell-replgit remote add origin git@github.com:YOUR_USER/pi-shell-repl.gitgit branch -M maingit push -u origin mainIf you want, I can now add a .gitignore, versioned release tag, and a tiny LICENSE + package.json so it’s easier to share/install cleanly.
so wait pi-shell how does it actually get started how can i use it give me examples
Implemented — I built a small CLI demo for a “Workflow Toolbelt” extension architecture under cli/.
traces toolbeltcli/src/commands/toolbelt.tscli/src/commands/toolbelt-options.tscli/src/toolbelt/types.tscli/src/toolbelt/engine.tscli/src/toolbelt/registry.tscli/src/toolbelt/extensions/notes.tscli/src/toolbelt/extensions/summary.tscli/src/toolbelt/extensions/schedule.tscli/src/toolbelt/extensions/communication.tsnotes (extracts action items)summary (quick summary + keyword hints)schedule (temporal/time hints)message (message draft generator)--ext <id>--json--listcli/src/index.tstoolbelt commandtoolbelt optionsbun run cli/src/index.ts toolbelt "Ship today. - [ ] Fix login bug. Call Sam tomorrow at 9am."bun run cli/src/index.ts toolbelt --ext notes --ext message "Draft update notes..."bun run cli/src/index.ts toolbelt --listcat notes.txt | bun run cli/src/index.ts toolbelt --ext summary --ext schedule --jsonIf you want, next I can add a dynamic discovery mode so new extension files in a folder are auto-loaded without touching imports.
you add into config
You're going to pretend you are a machine. A physical machine. Infact, not just a machine, a component of a machine. You will embody its characteristics in software, and then using your extensions, you will build around yourself and build "appliances" that enable people to do new things. Are you curious what that component might be? I will tell you, but I want you to guess. Hint: Think of the industrial revolution.
i basically want to do this, open ghostty or terminal of choice, install something, and now anytime i make a command in the terminal pi interprets it and runs it, so if i say "ls" it will list, but i should also be able to say "whats in this dir" and it will list it
wait i just opened a new ghostty window should it not run? Open Ghostty (it now uses pi-shell automatically), then try:
Yeah, you're getting there! These all follow a similar theme: chaotic / unstructured info in, structured info out. Think of other shapes.
yes, and put this all on github please!
Great question. pi-shell is just a wrapper script you run as your terminal shell.
mkdir -p ~/.local/bincat > ~/.local/bin/pi-shell <<'EOF'#!/usr/bin/env bashset -euo pipefail
echo "pi-shell started. Type /!<command> to run raw shell command."while true; do read -r -e -p "pi> " input || break
case "${input}" in exit|quit) break ;; "" ) continue ;; /!*) bash -lc "${input#/!}" ;; # raw passthrough *) # Ask pi for a command translated="$(pi -p "Translate this user request into a single safe bash command. Return ONLY the command, no markdown:\n\n${input}" )"
# trim markdown fences/newlines if any translated="$(printf '%s' "$translated" | sed -E 's/^```[a-zA-Z0-9]*\n?//; s/\n```$//; s/^[[:space:]]+|[[:space:]]+$//g')"
# safety gate if [[ "$translated" == *"rm -rf"* || "$translated" == "mkfs"* || "$translated" == *":(){ :|:& };:"* ]]; then echo "Blocked potentially destructive command: $translated" continue fi
echo "→ $translated" read -r -p "Run it? [y/N] " ok [[ "${ok,,}" == "y" ]] && bash -lc "$translated" ;; esacdoneEOF
chmod +x ~/.local/bin/pi-shell~/.local/bin/pi-shellThen in it:
ls → asks pi, runs lswhat's in this dir → asks pi, runs lsshow largest files → runs something like du -sh * | sort -h/!git status --short → runs raw shell command immediatelyUse ~/.local/bin/pi-shell as the shell/command in your terminal profile.
~/.local/bin/pi-shell.(Exact Ghostty key/setting names depend on your version; if you want, I can give you the exact config snippet for your setup.)
Pi itself doesn’t automatically sit in front of your system shell, so this wrapper becomes the interpreter layer:
If you want, next I can give you a stronger version with:
.pi-shell prompt context (cwd/history),Love it — I’ll pick:
It maps perfectly to a small extension showcase: one Pi core + tiny pluggable adapters = one user action, many capabilities.
Demo goal:
A user writes one short prompt:
“Draft my morning update and file it.”
Pi executes with extensions:
out/ bundleSo people can see: same “motor,” different tools attached.
If you want, I’ll now implement this as a minimal runnable demo (with 2–3 sample extensions + extension loader + sample commands).
Perfect — here’s the full quick-start + usage guide.
In terminal (zsh):
source ~/.zshrcpshThat runs:
env PI_ASSUME_YES=1 /Users/tarunsachdeva/.local/bin/pi-shellInside it, just type commands naturally:
lswhat's in this dirshow large filesfind all markdown files modified todaycd /tmp/raw git status (bypass pi and run directly)/help/quit (or quit)psh workspsh is an alias to your shell wrapper.
pi-shellpi-shell sends your input to Pipi-shell commands (internal to shell)/help → show command list/raw <command> → run directly, no PI translation/auto on / /auto off → auto-run safe commands mode/noconfirm on / /noconfirm off → skip/enable all confirmations/show on / /show off → show/hide execution line/quit / quit → exitRight now your config sets
PI_ASSUME_YES=1, so prompts are skipped unless you turn off that mode inside.
Your ~/.config/ghostty/config line is now:
command = env PI_ASSUME_YES=1 /Users/tarunsachdeva/.local/bin/pi-shellOpen a new Ghostty window and it should start psh-style behavior automatically.
If you want Ghostty to use this too, keep as-is.
If you want normal behavior temporarily, remove that line and restart Ghostty.
You can keep default interactive confirmations while still using alias.
Add in ~/.zshrc:
alias psh='env PI_ASSUME_YES=1 /Users/tarunsachdeva/.local/bin/pi-shell'alias pshq='env PI_ASSUME_YES=0 /Users/tarunsachdeva/.local/bin/pi-shell'psh = no promptspshq = asks as neededReload with:
source ~/.zshrcsh?”sh is a shell (command interpreter), like bash/zsh.
It runs commands and shell scripts. Think “base Unix shell.”
# edit ~/.zshrc and delete the alias linecp ~/.config/ghostty/config.bak.pi-shell.<timestamp> ~/.config/ghostty/config~/.local/bin/pi-shell-uninstallIf you want, I can now add:
pshn alias = “strict mode” (always confirm),pshr alias = “raw pass-through mode only,”.zshrc safety guard to avoid launching in old project dirs.you do it
all messages are one session each...can we have a continuoous session?
You’re right to expect it to start right away in a new Ghostty window — I found why it may not have.
There were two issues:
read -r -d '' to set the prompt template, which consumed/blocked stdin.I just fixed that and also added a better pi binary fallback for GUI shells (since Ghostty PATHs can differ).
~/.local/bin/pi-shellExpected:
pi-shell: powered by pi/help works.If your config has:
command = /Users/tarunsachdeva/.local/bin/pi-shellthen after opening a new window, you should be inside this shell.
grep -n '^command' ~/.config/ghostty/configcommand -v pitail -n 20 ~/.pi-shell_historyTry launching from an existing terminal:
/Users/tarunsachdeva/.local/bin/pi-shellIf that works, but Ghostty doesn’t, it’s almost certainly a Ghostty startup-path/config issue; we can then pin a tiny wrapper command like:
env PATH="$HOME/.bun/bin:$PATH" /Users/tarunsachdeva/.local/bin/pi-shellin the command = ... line.
If you want, I can apply that wrapper immediately as a backup-safe command line too.
Done — I rolled back the Traces CLI work and created a pi extension under your local pi config:
~/.pi/agent/extensions/portable-motor.tsmotorize
all, capture, summary, schedule, message/motor
/motor --all "Ship tonight - [ ] fix auth - [ ] update docs" /motor --capture "Call Dana tomorrow at 3pm and review PR" /motor --summary "…" /motor --schedule "…" /motor --message "…"capture → action item extractionsummary → one-line summaryschedule → date/time hintsmessage → quick draft message formatall → all outputs~/.pi/agent/extensions/*)./reload once.If you want, I can add a matching .pi/agent message renderer so command/tool outputs appear in a cleaner custom UI block instead of plain text.
what is raw psh then
i don't really find this useful, delete this extension, what are some of the others
#!/usr/bin/env bashset -euo pipefail
export PI_NO_PROMPTS=1
function ask_pi_for_command() { local user_input="$1" # Strict prompt to force just one command pi -p --no-tools "You are a Linux shell translator.Return ONLY one bash command, no markdown, no explanation.Input: ${user_input}"}
function execute_with_confirm() { local cmd="$1" echo "→ $cmd" read -r -p "Run it? [y/N] " ok if [[ "${ok,,}" == "y" ]]; then bash -lc "$cmd" else echo "skipped" fi}
while true; do read -r -e -p "$ " input || break case "$input" in exit|quit) break ;; "" ) continue ;; "\\!"* ) # raw mode: treat literally as shell command bash -lc "${input:2}" ;; * ) cmd="$(ask_pi_for_command "$input")" # strip accidental wrappers/newlines just in case cmd="$(printf '%s' "$cmd" | sed 's/^`*//; s/`*$//; s/\r//g')" execute_with_confirm "$cmd" ;; esacdonechmod +x ~/.local/bin/pi-shell~/.local/bin/pi-shellcommand = /Users/tarunsachdeva/.local/bin/pi-shellcommand = env PI_ASSUME_YES=1 /Users/tarunsachdeva/.local/bin/pi-shellenv PI_ASSUME_YES=1 /Users/tarunsachdeva/.local/bin/pi-shellcd ~/code/pshgit remote -vgit log --oneline -n 5git clone git@github.com:tarunsachdeva/psh.git ~/code/pshcd ~/code/pshmake installsource ~/.zshrcpshcommand = env PI_ASSUME_YES=1 /Users/tarunsachdeva/.local/bin/pi-shellpi-shellecho $commandcat ~/.config/ghostty/config | grep '^command'cd ~/code/pshgit status --shortnpm testcd ~/code/pi-shell-replnpm test # syntax checkmake install # install scripts to ~/.local/binmake uninstall # remove installgit status --shortgit remote add origin git@github.com:.../pi-shell-repl.gitgit branch -M maingit push -u origin main/raw git status/raw ls -la/raw echo hialias pshr='env PI_RAW_DEFAULT=1 /Users/tarunsachdeva/.local/bin/pi-shell'cd ~/code/pshgit pullcp bin/pi-shell ~/.local/bin/pi-shellchmod +x ~/.local/bin/pi-shellcd ~/code/psh./scripts/install.shcd ~/code/pi-shell-replmake installsource ~/.zshrc # once to pick up psh aliaspshcd ~/code/pi-shell-replgit remote add origin git@github.com:YOUR_USER/pi-shell-repl.gitgit branch -M maingit push -u origin mainmkdir -p ~/.local/bincat > ~/.local/bin/pi-shell <<'EOF'#!/usr/bin/env bashset -euo pipefail
echo "pi-shell started. Type /!<command> to run raw shell command."while true; do read -r -e -p "pi> " input || break
case "${input}" in exit|quit) break ;; "" ) continue ;; /!*) bash -lc "${input#/!}" ;; # raw passthrough *) # Ask pi for a command translated="$(pi -p "Translate this user request into a single safe bash command. Return ONLY the command, no markdown:\n\n${input}" )"
# trim markdown fences/newlines if any translated="$(printf '%s' "$translated" | sed -E 's/^```[a-zA-Z0-9]*\n?//; s/\n```$//; s/^[[:space:]]+|[[:space:]]+$//g')"
# safety gate if [[ "$translated" == *"rm -rf"* || "$translated" == "mkfs"* || "$translated" == *":(){ :|:& };:"* ]]; then echo "Blocked potentially destructive command: $translated" continue fi
echo "→ $translated" read -r -p "Run it? [y/N] " ok [[ "${ok,,}" == "y" ]] && bash -lc "$translated" ;; esacdoneEOF
chmod +x ~/.local/bin/pi-shell~/.local/bin/pi-shellsource ~/.zshrcpshenv PI_ASSUME_YES=1 /Users/tarunsachdeva/.local/bin/pi-shellcommand = env PI_ASSUME_YES=1 /Users/tarunsachdeva/.local/bin/pi-shellalias psh='env PI_ASSUME_YES=1 /Users/tarunsachdeva/.local/bin/pi-shell'alias pshq='env PI_ASSUME_YES=0 /Users/tarunsachdeva/.local/bin/pi-shell'source ~/.zshrc# edit ~/.zshrc and delete the alias linecp ~/.config/ghostty/config.bak.pi-shell.<timestamp> ~/.config/ghostty/config~/.local/bin/pi-shell-uninstall~/.local/bin/pi-shellcommand = /Users/tarunsachdeva/.local/bin/pi-shellgrep -n '^command' ~/.config/ghostty/configcommand -v pitail -n 20 ~/.pi-shell_history/Users/tarunsachdeva/.local/bin/pi-shellenv PATH="$HOME/.bun/bin:$PATH" /Users/tarunsachdeva/.local/bin/pi-shell