Internal ops API for the AIDA / OpenClaw Slack agent system.
Explore & call the API →
This service wraps a fixed set of /usr/local/bin ops scripts
behind an authenticated HTTP API, served at
admin-aida.claw.localsplash.ai.
Slack channels and threads are expected to already exist — they're created elsewhere. These endpoints exist to let Aida Claw actually use them: binding a Slack channel to the right business agent, refreshing a business's identity/profile, and attaching per-lead instructions to a specific thread.
/v1/profile/init and /v1/agent/init) can be updated at
will — changes take effect immediately, on the agent's next message.
/v1/lead/init)
are only picked up by a new session. An already-running Slack thread keeps
using whatever context it started with, so its session has to be torn down before it
will see the update — that's what /v1/thread-session/release is for: it
deletes the thread's stored session so the next message starts fresh and reads the
current thread-context file.
/v1/lead/init writes a per-thread context file
(thread-context/<channel>/slack-thread-<thread_ts>.json).
openclaw-thread-context is the separate OpenClaw plugin that actually
consumes those files: a before_prompt_build hook that looks up the current
Slack thread by its session key and appends that thread's
additionalContext to the system prompt for that turn only. It composes with
whatever context engine is running rather than replacing it, and does nothing if a thread
has no matching record. It's an internal, not-yet-published sibling project.