Plugin · Claude Code · Productivity

Vieko Bonfire

Vieko Bonfire is a Claude Code plugin for the Build phase that preserves project memory and coding context across agent sessions.

by vieko · github.com/vieko/bonfire

Keep decisions, patterns, and project context alive across Claude Code sessions so the agent does not restart from zero every chat.

9
GitHub stars
0
Installs
0
Community votes
One vote per signed-in builder - it helps surface the tools the community actually relies on.
Install

Add it to Claude Code

Install the plugin in Claude Code. One command, paste-ready.

Install the plugin
/plugin install vieko-bonfire@vieko/bonfire
Add to ClaudeUse the Agent APISkillselion is itself an MCP server - your agent can fetch this config directly.
Agent API

Built to be called by your agent

Skillselion is itself an MCP server. Your agent can pull this entry and a paste-ready install config straight from the API - no copy-paste.

Retrieve this entry with skillselion.get_details("plugin:vieko/bonfire") and the paste-ready config with skillselion.get_install_config("plugin:vieko/bonfire").

About

What it does

Vieko Bonfire is a Claude Code plugin built around a simple pain: your AI coding partner forgets everything when a conversation ends. Bonfire remembers—carrying context, patterns, and workflow state so indie builders can treat Claude Code more like a long-term teammate than a disposable tab. Catalog keywords emphasize memory, sessions, directory maintenance, and coding workflow, which maps to agent-tooling on the Build phase rather than a launch or analytics tool. It suits multi-week side projects where stack choices, naming rules, and partial refactors should survive overnight without dumping another mega-prompt. Complexity is moderate because you must adopt whatever memory conventions the plugin expects, but the payoff is fewer duplicated mistakes and less token burn on recap. It is not a deploy or SEO plugin; it is continuity infrastructure for agent-assisted development across Idea through Operate, with its primary browse home under agent-tooling.

Highlights

  • Persists coding context and patterns across conversations when Claude Code would otherwise forget
  • Directory-oriented memory model for maintaining project knowledge over multiple sessions
  • Workflow-focused plugin tagged productivity for solo builder continuity
  • Single-plugin bundle from vieko/bonfire repository
  • Reduces re-explaining architecture and conventions at the start of every session

Why builders use it

Every new Claude Code thread forces you to re-teach stack, patterns, and open tasks because the agent has no durable session memory.

After you register Bonfire, your agent can lean on maintained context and patterns so later sessions continue where the last one stopped.

At a glance

  • Type - Plugin in Productivity.
  • Adoption - 0 installs, 9 stars, 0 votes.

FAQ

Who is vieko-bonfire for?

It is for Claude Code users who work across many sessions on the same product and need persistent memory instead of blank-slate chats.

When should I use vieko-bonfire?

Use it once you notice rework from forgotten decisions—architecture picks, conventions, or in-progress tasks that the model keeps dropping.

How do I add vieko-bonfire to my agent?

Add the vieko/bonfire plugin from the Claude Code plugins directory and configure its memory or directory workflow per the repository README.

Discussion

Comments

Share how you use vieko-bonfire, gotchas, or tips for other indie builders.

No comments yet - be the first to share how you use it.

This week for builders

Five minutes, every Monday — the tools, releases and tactics for shipping solo.

unsubscribe anytime.