Directories
¶
| Path | Synopsis |
|---|---|
|
Package config is the gateway's self-hosted configuration, split the way memcode already splits everything (and the way Hermes does): secrets — the bot tokens — live in the global .env (written by `memcode gateway setup`, never hand-set), and NON-secret settings live here in gateway.yaml.
|
Package config is the gateway's self-hosted configuration, split the way memcode already splits everything (and the way Hermes does): secrets — the bot tokens — live in the global .env (written by `memcode gateway setup`, never hand-set), and NON-secret settings live here in gateway.yaml. |
|
Package importer migrates an existing OpenClaw configuration into memcode's gateway config.
|
Package importer migrates an existing OpenClaw configuration into memcode's gateway config. |
|
Package server is the memcode gateway runtime — the first external surface of memcode's event/agent spine.
|
Package server is the memcode gateway runtime — the first external surface of memcode's event/agent spine. |
|
Package state is the gateway's durable bookkeeping — the state that MUST survive a restart for the gateway to behave correctly: a durable INBOX of accepted-but-not-yet-processed messages (so a message is never lost between being acked to the provider and being run), and each polling channel's ack cursor (so a restart resumes where it left off).
|
Package state is the gateway's durable bookkeeping — the state that MUST survive a restart for the gateway to behave correctly: a durable INBOX of accepted-but-not-yet-processed messages (so a message is never lost between being acked to the provider and being run), and each polling channel's ack cursor (so a restart resumes where it left off). |
Click to show internal directories.
Click to hide internal directories.