bbg

A thin wrapper around babashka that runs tasks from a single global bb.edn (~/.config/bbg/bb.edn), so you can invoke personal automation tasks from any directory without polluting per-project configs. Includes shell completions and a small catalog of tasks I actually use.

Babashka task runners are normally scoped to a project's bb.edn. That's great for project-specific automation, but awkward for personal utilities you want available everywhere. bbg points bb at a fixed config under ~/.config/bbg/, so a single bb.edn follows you across every directory — no per-project pollution, no shell aliases, no cd dance.

• babashka

git clone https://github.com/jxonas/bbg ~/.config/bbg
ln -s ~/.config/bbg/bbg ~/.local/bin/bbg

Make sure ~/.local/bin is on your PATH.

bash — add to ~/.bashrc:

source ~/.config/bbg/completions/completions.bash

zsh — add to ~/.zshrc:

source ~/.config/bbg/completions/completions.zsh

bbg tasks            # list available tasks
bbg <task> [args]    # run a task

Tab completion will offer task names and per-task options.

Edit ~/.config/bbg/bb.edn and add entries under :tasks. See the babashka tasks documentation for the full schema.

• tm — Tmux session for the current project (host/main/claude/pi windows; auto-runs aishell)
• update:projects — Sync managed sandbox-Dockerfile fragments (clojure, knot) — in .aishell/Dockerfile or .sandbox/Dockerfile — from bbg into a hardcoded list of projects, gated per-fragment by anchor presence; also mirrors each fragment's skill (clojure → .claude/skills/clj-surgeon/, knot → .claude/skills/knot/) into projects carrying that fragment (one-way; never onboards)

This is a personal config. Fork freely and adapt it to your own needs. Issues and pull requests may not be acted on.

Inspired by PEZ/my-bbg.

MIT