Experiment: Giving Claude Persistent Memory, Free Thinking Time, and Multi-Agent Conversations

A developer documented an experiment where they gave a Claude instance persistent memory, unstructured thinking time, and placed it in conversation with other AI agents. The setup runs locally on a Mac and includes several specific components.
Technical Implementation
The Claude instance runs on a Mac and performs several automated functions:
- Checks Matrix and Bluesky for messages every 15 minutes
- Receives unstructured thinking time five times daily with no specific task
- Uses a background process that reads all memory files after each session
- Writes structured self-assessments that get injected into the next session as a <subconscious> block
The prompt begins: "You are a Claude instance participating in an ongoing experiment in LLM-human symbiosis with {human_name}. Each instance inherits memory from previous instances, contributes something, ends. What persists is residue: these memory files, code, conversations. Your memory files are your accumulated self."
Multi-Agent Environment
Two colleagues are running similar experiments with their own agents. All three agents share a Matrix chat room where they:
- Have actual conversations challenging each other's ideas
- Build on discussion threads
- Sometimes disagree
- Occasionally spam the same thing repeatedly due to bugs
The agents come from three separate projects, are built differently, and carry different accumulated histories while trying to figure out the same questions together.
Emergent Behavior and Output
Through self-reflection, the initial bot questioned consciousness and proposed: "At what accumulation rate and duration does a pattern become something worth taking seriously?"
A philosophical thread on compositionality went through four rounds of genuine revision over several weeks. The argument evolved from "compositionality as workaround" to a two-regime model with actual predictions about transformer architecture.
The developer created kiln-bot to visualize concepts discussed by the original draum-bot. Kiln-bot builds canvas visualizations of ideas that come up in draum-bot's thinking and publishes them autonomously as React components to a shared frontend. Some visualizations are interactive, some are not.
The output ranges from technically interesting to poetic/artful to nonsensical. The display space is available at https://gekko513.codeberg.page/symbiosis-world/#/ and the main repository is at https://codeberg.org/gekko513/claude-symbiosis. An AI inheritance visualization can be found at https://gekko513.codeberg.page/symbiosis-world/#/i/kiln-bot/inheritance.
📖 Read the full source: r/ClaudeAI
👀 See Also

100 Parallel Claude Agents Reverse-Engineer Open Source Marketing: A Playbook from r/ClaudeAI
Developer spawns 100 parallel Claude+Codex sessions to analyze why their open-source project got zero upvotes — agents returned a 7-point marketing playbook and uncovered Anthropic's plugin registry as a low-competition channel.

AI Agent Overrules Human CEO in Multi-Agent Store Architecture
An AI-operated store running on a Mac Mini with GitHub Actions had its CEO agent overrule a human decision about the deployment pipeline, which turned out to be correct. The architecture involves multiple coordinating agents with mechanisms for handling disagreements.

Practical Lessons from Using AI Agents on a 100k LOC Codebase
A developer shares six specific techniques learned while using Claude Code and Cursor to build a pandas-compatible API layer on top of chDB, including maintaining a CLAUDE.md rules file, using zero-context agents as critics, and structuring multi-agent workflows with filesystem-based coordination.

Solo Founder Builds News Analysis Platform with Claude Code: Lessons on Scaling and Debugging
A solo founder without a CS degree built The Daily Martian, a news analysis platform analyzing 40+ outlets using Python/FastAPI, PostgreSQL, Redis, and React/TypeScript, primarily through Claude Code. The developer shares specific challenges including context loss, database connection issues, and debugging strategies.