git404hub

what is little-peanut-agent fr?

smallpeanutbaby/little-peanut-agent — explained in plain English

Analysis updated 2026-05-18

13TypeScriptAudience · developerComplexity · 4/5Setup · moderate

tl;dr

Electron desktop AI workbench with modes for chat, planning, agent execution, and review, plus a permission-gated local tool layer and SQLite store.

vibe map

mindmap
  root((little-peanut-agent))
    Inputs
      User prompts
      Project folder
      MCP servers
      API keys
    Outputs
      Edited files
      Tool runs
      Saved memory
      Cost logs
    Use Cases
      Local coding agent
      Plan only research mode
      Pipeline planner executor reviewer
    Tech Stack
      Electron
      React
      TypeScript
      SQLite
      MCP

Code map

Detail Auto

An interactive map of this repo's files and how they connect — its source is parsed live in your browser. Click Visualize to build it.

filefunction / class

what do people make with this?

VIBE 1

Run a local AI workbench that edits files and runs commands inside a project

VIBE 2

Use plan mode to research a change and propose a structured implementation

VIBE 3

Chain planner, executor, and reviewer roles through pipeline mode

VIBE 4

Connect MCP servers over stdio, SSE, or HTTP to add new agent tools

what's the stack?

ElectronReactTypeScriptSQLiteNodeMCP

how it stacks up fr

smallpeanutbaby/little-peanut-agentandersondanieln/hexllamaantonlobanovskiy/agent-tmux-web
Stars131313
LanguageTypeScriptTypeScriptTypeScript
Setup difficultymoderateeasymoderate
Complexity4/52/53/5
Audiencedevelopervibe coderdeveloper

Figures from each repo's GitHub metadata at analysis time.

how do i run it?

Difficulty · moderate time til it works · 30min

Needs Node 22 or newer plus npm 10, and the real Electron app lives inside the src directory under a delegator root.

in plain english

Little Peanut is a desktop AI workbench built as an Electron application with a React interface and a local SQLite database. Its goal is not to be another chat client. The README frames it as a place where a model can actually do work inside a real project folder on your computer, rather than just answering questions in a browser tab. The repo is described as early development, with the basic skeleton in place and many features still being filled in. The app organises work into named modes. Chat is for light conversation, Agent runs tasks against a project, Plan is a read-only mode that does research and proposes a structured implementation plan without changing files, and Pipeline strings together a planner, executor, and reviewer in stages. There are also modes called Review, Writing, Code, Learning, Research, Brainstorm, Translate, and Summarize, each tuned for a different kind of request. The agent can call local tools such as file read and search, file edits, terminal commands, todo and task tracking, web search and fetch, lint reading, and a memory store. Tool calls go through a permission gate. Risky or destructive actions trigger an approval prompt, and permission rules can be saved per project or per session. The README is careful to say this is not a full sandbox, only a controllable boundary on a local machine. Little Peanut supports several model providers including OpenAI, Anthropic, Gemini, and OpenAI-compatible endpoints, with custom base URLs and API keys. It can also connect to MCP servers over stdio, SSE, or HTTP for extra tools. SQLite stores conversations, messages, tool runs, tasks, permission rules, a memory index, cost logs, model and provider config, and channel bot settings for QQ, Feishu, and DingTalk integrations. To run it you need Node.js 22 or newer and npm 10 or newer. The root folder is a small delegator, and the real Electron app lives in the src directory. Typical commands are npm install, npm run install:app, npm run dev to start, and npm run build or npm run dist to package.

prompts (copy fr)

prompt 1
Install Node 22, run npm install and npm run install:app, then start the desktop app
prompt 2
Walk through how permission gating decides which tool calls require an approval prompt
prompt 3
Add an Anthropic provider with my API key and switch the active model in settings
prompt 4
Wire a stdio MCP server into the agent and verify its tools show up in the picker
prompt 5
Show me the SQLite tables that track tool runs, tasks, and permission rules

Frequently asked questions

what is little-peanut-agent fr?

Electron desktop AI workbench with modes for chat, planning, agent execution, and review, plus a permission-gated local tool layer and SQLite store.

What language is little-peanut-agent written in?

Mainly TypeScript. The stack also includes Electron, React, TypeScript.

How hard is little-peanut-agent to set up?

Setup difficulty is rated moderate, with roughly 30min to a first successful run.

Who is little-peanut-agent for?

Mainly developer.

peek the repo → explain another one

This repo across BitVibe Labs

double-check against the repo, no cap.