@pellux/goodvibes-agent
v0.1.1
Published
Near-fork GoodVibes operator assistant with the GoodVibes TUI shell, renderer, input, fullscreen workspace, and daemon-connected Agent product brain.
Maintainers
Readme
GoodVibes Agent
GoodVibes Agent is the personal operator assistant built on the GoodVibes terminal UI foundation. This repository is intentionally in a near-fork baseline phase: the shell, renderer, input, fullscreen workspace, command, and release bones are copied from the terminal product first, then the coding-specific behavior is removed or reshaped deliberately.
The Agent product connects to an already-running GoodVibes daemon. It does not install, start, stop, restart, or own the daemon, HTTP listener, web surface, or service lifecycle.
Install
Install the public alpha package with Bun:
bun add -g @pellux/goodvibes-agent
goodvibes-agent --help
goodvibes-agent statusIf Bun reports untrusted lifecycle dependencies, trust only the package and dependencies required by this package:
bun pm trust -g @pellux/goodvibes-agent @pellux/goodvibes-sdk core-js tree-sitter-css tree-sitter-javascript tree-sitter-json tree-sitter-python tree-sitter-typescriptSource Usage
git clone https://github.com/mgd34msu/goodvibes-agent.git
cd goodvibes-agent
bun install
bun run devUseful checks:
bunx tsc --noEmit
bun run build
bun run package:install-check
bun run publish:checkInside the Agent TUI, use /agent, /home, or /operator to open the operator workspace. It is the Agent-first fullscreen surface for setup, status, knowledge, local memory/skills, work-plan/approval review, automation observability, and explicit build delegation to GoodVibes TUI.
Daemon Prerequisite
Start or restart the daemon from GoodVibes TUI or the daemon host before launching Agent. Agent status and companion/knowledge routes connect to that external daemon, normally on http://127.0.0.1:3421.
Agent intentionally blocks daemon lifecycle commands:
goodvibes-agent serve
goodvibes-agent service start
goodvibes-agent surfaces enable webThose commands should return explicit external-daemon guidance instead of mutating local service posture.
Product Boundary
GoodVibes Agent owns the operator assistant surface: serial assistant flow, proactive safe actions, local memory/skills/personas until stable shared registries exist, Agent knowledge routes, companion chat, approvals/automation observability, and explicit build delegation.
GoodVibes TUI owns coding execution: file edits, git/worktree workflows, coding panels, sandbox/QEMU UX, and WRFC execution. Agent may delegate explicit build/fix/review work to TUI through public daemon/session contracts; normal assistant chat must not use shared coding sessions.
Package Docs
Package-facing docs are intentionally narrow during the near-fork baseline:
Broader TUI-derived reference docs may exist in the source tree while the near-fork foundation is being completed, but the package-facing Agent documentation is limited to the docs listed above.
