alexein-cli
Memory from Alexein in a LangGraph project, a CrewAI crew or an OpenAI
Agents SDK agent, as a short file you own: one command writes memory.py - your settings and one
configured AlexeinMemory, wired from the alexein
client's integration for your framework - and adds alexein[<framework>] to your project.
uvx alexein-cli init langgraph # a LangGraph project you have
uvx alexein-cli init crewai # a crew you have
uvx alexein-cli init openai-agents # an OpenAI Agents SDK project you have
uvx alexein-cli create langgraph my-agent # a new one, with memory wired in
uvx alexein-cli create crewai my-crew
uvx alexein-cli create openai-agents my-agent
uvx alexein-cli doctor # is it all set up?
The file is yours: edit the settings, rename things, move it. What it imports - recall, saving,
the tools, failing open - comes from alexein.langgraph, alexein.openai_agents or
alexein.crewai, and an upgrade of alexein reaches it. Importing it needs no key: the client
is made on the first call to memory, from ALEXEIN_API_KEY and ALEXEIN_API_URL.
init
Before it writes anything, init checks that it is in a Python project, that the project uses
the framework (it asks before going on in one that does not; --yes goes on without asking),
that what is installed is new enough (LangGraph 1.2, LangChain 1.0, the OpenAI Agents SDK 0.24,
CrewAI 1.15), and where the file goes: beside the graph langgraph.json names (asking when there
are several, or --graph NAME), beside the file that builds your Agent, or beside your crew.
Any of these can stop it, and then nothing has changed. An existing memory.py is replaced only
with --force.
Then it writes memory.py, adds alexein[langgraph]>=0.3 (or [openai-agents], [crewai])
where the project does not depend on it with that extra yet - with the project's own tool: uv,
poetry, pdm, or a line in requirements.txt - and sets up the key: --key tm_..., or asked for
at a terminal. Enter skips it, and an empty ALEXEIN_API_KEY= waits in .env. A key it is given
is checked, and a key that only reads is called out.
| Flag | What it does |
|---|---|
--fast |
FAST = True: searches skip the relevance check, free and quicker |
--key, --base-url |
the key and memory's address, written into .env |
--skip-key |
do not ask for a key |
--dir, --file, --graph |
where the file goes, and what it is called |
--force |
replace a file already there |
--no-install |
print the install command instead of running it |
--dry-run |
make every check, say what would happen, change nothing |
--yes |
ask nothing |
Every file holds the same four settings, at the top:
| Setting | Default | What it does |
|---|---|---|
FAST |
False |
True answers sooner and free, a little less precisely |
STRICT |
False |
True raises when memory is down, where by default a turn goes on without it |
MAX_CHARS |
4000 |
how much of what memory holds goes into a prompt |
TIMEOUT |
10.0 |
seconds each attempt at a call may take |
A wrong key raises whatever STRICT says: that is a mistake to fix, not an outage to ride out.
Memory being down is logged on the alexein logger.
LangGraph
init langgraph writes memory, with MemoryState and MemoryContext:
from app.memory import MemoryContext, MemoryState, memory
builder = StateGraph(MemoryState, context_schema=MemoryContext)
builder.add_node("recall", memory.recall) # what memory holds, into state["memory"]
builder.add_node("agent", agent) # yours: memory.prompt(state) in its prompt
builder.add_node("remember", memory.remember) # save the turn
builder.add_edge(START, "recall")
builder.add_edge("recall", "agent")
builder.add_edge("agent", "remember")
graph = builder.compile()
graph.invoke(
{"messages": [HumanMessage("Where do I live?")]},
config={"configurable": {"thread_id": "t-1"}},
context={"user_id": "dana"},
)
Or give the model tools to call when it decides to:
create_agent(model, tools=memory.tools(), context_schema=MemoryContext) offers memory_search
and memory_open; memory.tools(write=True) adds memory_add. The nodes and tools run under
invoke and ainvoke; memory.arecall and memory.aremember are the nodes' async
counterparts.
Whose memory is read comes from the run's context, never from the model. A LangGraph thread is
a memory session.
The OpenAI Agents SDK
init openai-agents writes memory, with MemoryContext, beside the file that builds your
Agent (asking when there are several, or --dir; with none, into the project's package):
from app.memory import MemoryContext, memory
agent = Agent(name="Assistant", tools=memory.tools())
result = await Runner.run(
agent,
"Where do I live?",
context=MemoryContext(user_id="dana", session_id="conv-7"),
run_config=RunConfig(call_model_input_filter=memory.recall),
)
await memory.remember(result) # for run_streamed, once its events are consumed
memory.recall searches once a turn and adds what it finds to the instructions of every model
call in the turn, so it is never written into a Session, the Conversations API or
to_input_list(). Any context with a user_id will do.
CrewAI
init crewai writes alexein_memory - CrewAI's own memory, kept in Alexein - and whose,
beside a classic crew (@CrewBase in src/<pkg>/crew.py) or a JSON one (crew.jsonc). Flows
are not supported yet.
from my_crew.memory import alexein_memory, whose
@CrewBase
class MyCrew:
memory = alexein_memory
@before_kickoff
def whose_memory(self, inputs):
return whose(inputs)
@crew
def crew(self) -> Crew:
return Crew(agents=self.agents, tasks=self.tasks, memory=self.memory)
MyCrew().crew().kickoff(inputs={"user_id": "dana", "topic": "..."})
A JSON crew points crew.jsonc at the same two names:
"memory": {"python": "memory.alexein_memory"},
"before_kickoff_callbacks": [{"python": "memory.whose"}]
CrewAI then recalls the user's memory before every task, saves what each task learned, and gives
every agent its memory tools. Every kickoff names its user in inputs["user_id"]; the key is
checked at kickoff, once per process. whose is a function in the file rather than
alexein_memory.whose because CrewAI keeps only module-level callbacks when it restores a
checkpoint. Without CrewAI's memory: Agent(..., tools=alexein_memory.tools("dana")), and
alexein_memory.save_result("dana", output) after the run.
create
create <framework> <name> makes a uv project with memory wired in, and memory.py as init
writes it:
create langgraph- a graph that recalls, searches and remembers, a terminal chat (uv run -m <package>.chat --user dana, where<package>is the name in lower case with-as_), andlanggraph.jsonforuv run langgraph dev.--modelnames the model byinit_chat_model's name (defaultanthropic:claude-sonnet-5-5), whose LangChain package it adds.create openai-agents- an agent and a terminal chat.--modelnames the model (MODELin.env); without it, the SDK's default.create crewai- a classic crew with one assistant agent anduv run run_crew --user dana "...".--modeltakes CrewAI'sprovider/modelname (defaultanthropic/claude-sonnet-5-5) and adds the CrewAI extra that provider needs.
It takes init's --fast and key flags.
doctor
Checks the memory file, that alexein is a dependency with the framework's extra, the installed
versions, that the integration module imports in the project's own .venv, ALEXEIN_API_KEY
and ALEXEIN_API_URL (in .env or the environment), the key (with memory.me(), which is free)
and that .env is not committed. Each failure says how to fix it.
License
MIT
Metadata
Release files for alexein-cli 0.3.0
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 |
|---|---|---|---|---|
| alexein_cli-0.3.0.tar.gz | 31.5 kB | With provenance | Details for alexein_cli-0.3.0.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| alexein_cli-0.3.0-py3-none-any.whl | Python 3 | none | any | Details for alexein_cli-0.3.0-py3-none-any.whl |
Total release size: 80.0 kB
Release files / alexein_cli-0.3.0.tar.gz
| Download URL | alexein_cli-0.3.0.tar.gz |
|---|---|
| Size | 31.5 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
728a15ad4c8df9f9e24aacd5d8dadf8a40b3af299b8374b23291543550e4caa7
|
|
BLAKE2b-256 checksum How to use checksums |
9bcc5ccd046d9ae2d1569843310b222caa3e25ada88735904c4b1f6ae5dfc143
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.16
|
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.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Nov 4, 2026.
Transparency logRelease files / alexein_cli-0.3.0-py3-none-any.whl
| Download URL | alexein_cli-0.3.0-py3-none-any.whl |
|---|---|
| Size | 48.5 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
7641eeed7bcf1d633dd03d764898c5302b64e867383e09d79881df15e8ae6f5d
|
|
BLAKE2b-256 checksum How to use checksums |
5a2689290189fec028f317a1f7feaa0b7804e3be1319eebcdb1897c563a863fc
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.16
|
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.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Nov 4, 2026.
Transparency logSecurity for alexein-cli 0.3.0
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.
Full provenance
Both files in this release have been uploaded with provenance metadata.
Attestation for alexein_cli-0.3.0.tar.gz
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Nov 4, 2026.
Transparency logA 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.