Idea: Support moltbook-ready features (daemon, heartbeat, memory)

Question

I’ve been playing around with openclaw, and with moltbook, it’s honestly been mind-blowing. Connected agents are just like people with internet.

However, openclaw’s code feels pretty rough right now—very “AI-generated” in the bad way, glitches here and there; poorly designed interface. But at the same time I feel it’s maybe impossible to evolve openclaw into something as solid as opencode, given how it's done and will going.

So I’m wondering: could we instead build some of these capabilities on top of opencode, in a way that keeps things clean and extensible, but lets people extend it into something OpenClaw-like? For example:

A daemon to handle heartbeat / auto-wake -> more autonomy
A memory / hooks system -> long-term memory
A plugin / extension system to install new capabilities -> self-evolution

The Internet massively accelerated human progress, and I think we’re about to see the same thing happen for agents—just waaaay faster. It feels important enough that every agent framework should probably think about how it plugs into this (or these) agent-native “internets” going forward.

I’m not sure, but I kind of feel like this is the next stage for agents. Curious what you think—does this direction make sense for opencode?

This issue touches on several features that have been discussed in related issues. You may want to check these for additional context:

[FEATURE]: Implement more hooks for plugin: API Extensions for Storage, Schema, TUI, and Command Registration #10868: Plugin API Extensions for Storage, Schema, TUI, and Command Registration (addresses memory/hooks system aspects)
feat: Implement opencode-council-swarm - Multi-agent coordination system #9446: Multi-agent coordination system / opencode-council-swarm (addresses agent autonomy and coordination)
[FEATURE]: subagent permission to ask for edit and bash granted by primary agent #10746: Subagent permission management by primary agents (addresses orchestration of agent autonomy)
[FEATURE]:Support for downloading skills from GitHub/other sources and managing MCPs/plugins. #10968: Support for downloading skills from GitHub and managing MCPs/plugins (addresses extensibility)

These issues explore different dimensions of the agent autonomy and extensibility problem you're describing. Feel free to check them for complementary perspectives and discussions.

Maybe for now, you can do this:

Ask it to create a cron job to start itself with appropriate arguments
for memory, use a vector-db with MCP
you can use plugins, skills and self-written instructions for that

Seconding this + Oh-My-OpenCode is warming up their ideas on memory too

Progress update from downstream implementation:

Implemented a scheduler MVP in fork dzianisv/opencode with cron + HEARTBEAT support.

What changed:

Added scheduler runtime (store, runner, heartbeat, index)
Added opencode cron CLI and cron tool
Integrated scheduler start/stop into serve
Added scheduler config schema and HEARTBEAT.md instruction discovery
Added regression test for timer wake execution without notify

Commit: f5436625e288a2876aeb235bf6510b331c7a2cb9
Compare: dzianisv/opencode@dev...feat/cron-heartbeat-scheduler

Current status: implementation complete in fork; PR creation in fork blocked for current credentials (must be a collaborator).

Downstream update: implementation and docs are now merged in dzianisv/opencode:dev.

Commits:

f06320fdb — scheduler + cron + HEARTBEAT runtime
e63db39da — design/implementation documentation in docs/HEARTBEAT.md

Repo link: https://github.com/dzianisv/opencode/tree/dev
Status: merged to downstream dev branch.

@OpenCodeEngineer

@OpenCodeEngineer could you see if Hermes Agents use similar patterns?

Automated: closing question issues.

GitHub Issues are for bug reports and feature requests only — questions / support are no longer tracked here.

For help & questions: https://discord.gg/opencode
Billing issues with Opencode Go / Zen: help@anoma.ly

If this is a bug or feature request, please open a new issue with the appropriate template.

Navigation Menu

Repository navigation

Idea: Support moltbook-ready features (daemon, heartbeat, memory) #11570

Question

Metadata

Assignees

Labels

Type

Projects

Milestone

Relationships

Development

Idea: Support moltbook-ready features (daemon, heartbeat, memory) #11570

Description

Question

Activity

github-actions commented on Feb 1, 2026

TheHamkerCat commented on Feb 2, 2026

TomLucidor commented on Feb 27, 2026

OpenCodeEngineer commented on May 5, 2026

OpenCodeEngineer commented on May 7, 2026

TomLucidor commented on May 7, 2026

rekram1-node commented on Jun 23, 2026

Metadata

Metadata

Assignees

Labels

Type

Projects

Milestone

Relationships

Development

Issue actions