Daemon8 alpha discussion

[jhavenz]

👋 Welcome!

We’re using Discussions as a place to connect with other members of our community. We hope that you:

• Ask questions you’re wondering about.
• Share ideas.
• Engage with other community members.
• Welcome others and are open-minded. Remember that this is a community we
  build together 💪.

---

Overview

With daemon8 being local-first (0 network activity goes out) and the varying results from different LLMs, discussions are going to be key.

The goal here is to ensure the foundational features are working across the 3 major AI harnesses (Google, Codex, and Claude).

Project Setup

daemon8_connect and daemon8_init -- this is the vital setup stage in which daemon8 instructs your model to find the right log sources for the framework/language/etc. of the directory you're working in. I've seen cases where Claude flat out ignores this, though more often then not it gets it spot on. Codex has proven to be the strongest.

Be sure to check out the [pwd]/.daemon8/config.toml file once the LLM runs through this process. You can quickly adjust as needed.

Daemon8 is smart enough to know when you're not in a project folder and/or when you're in a monorepo/workspace. Behavior in these cases is as you'd expect -- either dont' set any config file up (non-project) or recurse into monorepo projects and grab their log sources

Quick commands: d8 sync, d8 init

---

Conversation Recovery

The idea here is that you pickup right where you left off, the provider is irrelevant.

By default, daemon8 only checks the last 24hrs. You can tell it to look further back or give it specific dates/days.

I've explicitly chosen not to use CLI hooks because of how brittle they are - especially once you're stacking them. If you have an opinion on this, do lmk.

daemon8 has a crate that abstracts over different AI providers. If it saves you some time, do lmk.

Quick commands: d8 convo, d8 chat history

---

Query Lensing

Lenses ensure all subsequent reads from the feed are filtered based on some series of criteria. Think of it as a database view, but for an agent reading debug and log output.

Quick commands: d8 lens network calls, d8 lens console errors, d8 lens sql

---

Debug Sessions

Debug sessions begin as persisted metadata. From there, actions taken and topics discussed can then be recorded together, providing a system of structured heuristics around agentic debugging in a more general sense.

Creating debug sessions also acts as a marker that tells daemon8 when to have the noisier log sources start emitting their data. Outside of debug sessions, the noise kept to bare minimum.

For example:

• checkpoint > execute code > read logs
• fix a bug > checkpoint > fix next bug
• checkpoint > fix many bugs > classify

Quick commands: d8 debug, d8 debug start/d8 debug finish, d8 checkpoint

---

All participation is welcome.

"The only dumb question is one you don't ask"

Thx for reading.