brav0charlie

Getting Useful Results from Self-Hosted Honcho

This is a field guide for the failure mode where Honcho is technically running, but the memory it produces is noisy, empty, or actively unhelpful.

The short version: Honcho is very sensitive to input quality. Garbage in, garbage out. If you feed the deriver recalled memory, assistant task history, tool chatter, temporary troubleshooting state, and every random user request as if it were durable autobiographical truth, Honcho will faithfully preserve garbage and then recall it later as context. That makes the agent feel haunted by its own transcript.

This document describes the symptoms we saw and the final changes that made Honcho useful in practice.

---

brav0charlie

/*

  File: RBC_Zettelkasten_in_Logseq.css
  
  Description:
    This CSS file is my attempt at 'porting' the Roam Book Club Zettelkasten
    CSS for use in Logseq.
  
  NOTES:
    - There are tags created for the three "projects" in the source css. You're intended

brav0charlie

#!/bin/bash

# VyOS Build Branch (Rolling Release=current, Stable=equuleus, 1.2=crux)
BUILD_BRANCH="current"

# This should be your cloned vyos/vyos-build git repo
PROJECT_DIR="/home/billc/Projects/vyos-build"

# Your home directory
HOME_DIR="/home/billc"

brav0charlie

#!/bin/vbash

#        file: 99-git-commit
# description: Saves config commands & config json to files, commits to local
#              git repo. Repo stored in /config/user-data/$CONFIG_REPO. Completes
#              process with a push to the remote repo.
#
#              This script is intended to be used as a post-commit hook, allowing
#              for automated config backup in a git repo.
#

brav0charlie

# NOTE: We're passing a cleartext password via an environment variable. If you're not 
#       comfortable with this, there's a manual setup process available in the Docker 
#       Hub page for smallstep/step-ca (https://hub.docker.com/r/smallstep/step-ca).
#       
#       If you're using your own DNS server(s) to resolve internal hostnames, enter
#       them in the DNS1 and DNS2 fields. If not, leave these null and delete the DNS
#       section (lines 26 - 28) in docker-compose.yml.
#

brav0charlie

# NOTE: While AdGuard Home may be configured as a DHCP server, this is out
#       out of scope for this docker-compose.yml file. Configuring the DHCP
#       server requires using 'network_mode: host'. 
#
#       If you want to use the DHCP server feature, delete the 'network:'
#       section (lines 20 & 21), as well as the entire 'ports:' section
#       (lines 30 - 47). Then, just below the 'restart:' section (line 19)
#       insert a line that reads 'network_mode: host'. The container will
#       still reserve all the ports listed below, as well as 67 and 68 for
#       DHCP, but there's no need to map them in the docker-compose.yml file

brav0charlie

# IMPORTANT NOTE: Make sure you replace the GRAYLOG_PASSWORD_SECRET on line 53 with one you generate. You must
#                 also replace the GRAYLOG_ROOT_PASSWORD_SHA2 on line 56 with one you generate. This stack will
#                 not load without these passwords defined.
#
#                 Data is persisted using the three volumes created below. Port 9200 is exposed on the Elasticsearch
#                 container allowing you to spin up a Grafana container to use for visulization as well.
#

version: '3'