Thanks to visit codestin.com
Credit goes to github.com

Skip to content

Conversation

@zknicker
Copy link
Contributor

@zknicker zknicker commented Jan 19, 2026

This change enables the heartbeat to run in a different session than main. This is important for clawdbot users who do not use the main session (e.g. the majority of my bot-to-human conversation happens within a discord channel).

Changes

  • add new optional config heartbeat.session (default: main)
  • example: { session: "agent:main:discord:channel:123", ... }
  • when configured, the heartbeat will run in this session
  • updated docs

Alternatives

A plugin could approximate this by injecting channel context into the heartbeat prompt via before_agent_start. But this belongs at the framework level: users who primarily work outside the main session would otherwise get heartbeats that miss recent conversation context.

Testing

  • added unit tests
  • live tested with my clawdbot that lives in a private Discord channel

👾 Assisted by Codex

@zknicker zknicker changed the title Heartbeat: configurable session context feat: configurable heartbeat session Jan 19, 2026
@steipete steipete self-assigned this Jan 21, 2026
@steipete
Copy link
Contributor

Checked main at 758f30e.
Heartbeat still runs in the main session only; no heartbeat.session config in src/config/zod-schema.agent-runtime.ts or src/infra/heartbeat-runner.ts.
So this isn’t implemented on main yet; PR still adds new behavior.

@steipete steipete force-pushed the feat/heartbeat-session-target branch from 537b971 to 39073d5 Compare January 22, 2026 01:50
@steipete steipete merged commit da98528 into openclaw:main Jan 22, 2026
41 of 42 checks passed
@steipete
Copy link
Contributor

Landed via temp rebase onto main.

  • Gate: pnpm lint && pnpm build && pnpm test
  • Land commit: 39073d5
  • Merge commit: da98528

Thanks @zknicker!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants