maximem-synap-camel-ai
Synap memory integration for CAMEL-AI — plug
Synap in as a native AgentMemory so your ChatAgent gains persistent long-term
memory, plus explicit tools and short-term context.
pip install maximem-synap-camel-ai camel-ai
Surfaces
| Surface | CAMEL extension point | Purpose |
|---|---|---|
SynapAgentMemory |
AgentMemory → ChatAgent(memory=...) |
Recall + persistence layered over CAMEL's own conversation history |
create_synap_tools |
FunctionTool |
Explicit search_memory / store_memory the model can call |
synap_st_system_message |
ChatAgent(system_message=...) |
Fold Synap short-term context into the system prompt |
SynapAgentMemory also reports the turn on Synap's live stream — see
Live stream reporting.
Native memory
SynapAgentMemory subclasses CAMEL's ChatHistoryMemory and augments it rather
than replacing it — CAMEL's get_context() is the sole source of the model's input,
so the memory must return the real conversation (system + user + assistant). On top
of that live history it:
- recalls Synap's long-term memories and prepends them as a system context block (using the latest user turn as the query);
- records every user and assistant turn as a Synap conversation message, under
conversation_id(defaultcamel-{agent_id}; pass your own to continue a conversation across agents or processes). The server compacts that conversation and promotes it to long-term memory, and the SDK's local history search can find old turns after compaction; - replaces CAMEL's earlier turns with Synap's compaction once the server has compacted the conversation: the model sees CAMEL's system message, the compaction block, the turns after it, and the current turn. CAMEL's own summarizer stays installed as the fallback (it does not fire on the shorter history), and a conversation with no compaction yet is left as CAMEL holds it.
from camel.agents import ChatAgent
from camel.models import ModelFactory
from maximem_synap import MaximemSynapSDK
from synap_camel_ai import SynapAgentMemory
sdk = MaximemSynapSDK(api_key="sk-...")
memory = SynapAgentMemory(
sdk, user_id="alice", customer_id="acme", conversation_id="conv_abc",
)
agent = ChatAgent(
system_message="You are a concise, friendly support agent.",
model=ModelFactory.create(model_platform="openai", model_type="gpt-4o"),
memory=memory, # constructor only — not agent.memory = ...
)
print(agent.step("Remind me what plan I'm on and my open ticket.").msgs[0].content)
Attach the memory via the constructor (ChatAgent(memory=...)), not
agent.memory = ... afterward.
Explicit tools
from synap_camel_ai import create_synap_tools
agent = ChatAgent(
system_message="You are a helpful assistant.",
tools=create_synap_tools(sdk, user_id="alice", customer_id="acme"),
)
Short-term context
synap_st_system_message folds the conversation's compaction block (not its
recent turns, which ChatAgent already sends) into the system message once, at
construction. With SynapAgentMemory the live compaction replaces that snapshot
on every step.
from synap_camel_ai import SynapAgentMemory, synap_st_system_message
agent = ChatAgent(
system_message=synap_st_system_message(
sdk, conversation_id="conv_abc",
system_message="You are a support agent.",
),
memory=SynapAgentMemory(sdk, user_id="alice"),
)
Live stream reporting
CAMEL has no callback protocol, so SynapAgentMemory.write_records is the only
place an integration can see what an agent is doing — and it sees all of it,
because ChatAgent.update_memory is how CAMEL records every part of a turn.
The first write opens the stream (sdk.instance.listen()); you do not call it.
The memory reports five events on it so Synap's anticipation agent can watch the
turn unfold:
| What CAMEL writes | What goes on the stream |
|---|---|
a USER record |
the user turn |
an ASSISTANT record carrying meta_dict["tool_calls"] |
one tool_call per entry, with the parsed arguments and the provider's tool_call_id |
a FUNCTION record |
the tool_result, under that same id |
an ASSISTANT record with reasoning_content |
the reasoning step, then the assistant turn |
Stream first, REST otherwise, never both. The user and assistant turns go
out as stream events and the server persists them from the event. If the stream
cannot open they are written with sdk.conversation.record_message. Tool calls,
tool results and reasoning are stream-only. Set SYNAP_AUTO_LISTEN=false (or
call set_auto_listen(sdk, False) from synap_integrations_common) to keep
turns on REST.
CAMEL's own summary ([CONTEXT_SUMMARY] ..., and the user message it rewrites)
is never written as a turn: the real turns are already on Synap.
Previously, turns were ingested as a transcript document (
memories.create). That left no conversation on the server, so compaction and history search had nothing to work on. It is replaced, not kept alongside: the server promotes recorded messages to long-term memory, so both would extract the same text twice.
sdk = MaximemSynapSDK(api_key="sk-...")
memory = SynapAgentMemory(
sdk, user_id="alice", customer_id="acme",
conversation_id="conv_abc", # defaults to camel-{agent_id}
)
Reporting never raises into ChatAgent.step and never changes what the agent
answers.
Error policy
- Reads (
search_memory, memory recall) degrade — a Synap blip returns no recall and the turn continues. - The turn write inside the agent loop is best-effort by default
(
on_error="fallback") so a transient outage never discards a model response; seton_error="raise"to raiseSynapIntegrationErrorwhen a turn was not written. - The explicit
store_memorytool raisesSynapIntegrationErroron failure.
Requires Python 3.11+ and camel-ai>=0.2.90.
Metadata
Release files for maximem-synap-camel-ai 0.1.3
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | Actions |
|---|---|---|---|---|
| maximem_synap_camel_ai-0.1.3.tar.gz | 24.9 kB | Without provenance | Details for maximem_synap_camel_ai-0.1.3.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| maximem_synap_camel_ai-0.1.3-py3-none-any.whl | Python 3 | none | any | Details for maximem_synap_camel_ai-0.1.3-py3-none-any.whl |
Total release size: 41.8 kB
Release files / maximem_synap_camel_ai-0.1.3.tar.gz
| Download URL | maximem_synap_camel_ai-0.1.3.tar.gz |
|---|---|
| Size | 24.9 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
0000daad8d58976692438348d6308c3a536a893989bb9b982635ecf69644f938
|
|
BLAKE2b-256 checksum How to use checksums |
e5046e75eb3c4721565db37aeb2acbcdf05b67c4c86688661471af99e62431f1
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/7.0.0 CPython/3.14.2
|
Release files / maximem_synap_camel_ai-0.1.3-py3-none-any.whl
| Download URL | maximem_synap_camel_ai-0.1.3-py3-none-any.whl |
|---|---|
| Size | 17.0 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
4a6d5135c748b9123ec562f2672c28eec30c55bc4e1c606093ab1ba04858c32b
|
|
BLAKE2b-256 checksum How to use checksums |
80d320e77365e00a76eef079e11b5c82c023cce8a9a70868431a5cee97fbf462
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/7.0.0 CPython/3.14.2
|
Security for maximem-synap-camel-ai 0.1.3
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.