Skip to main content

Alem logo showing synchronous coordination

PyPI Python versions CI License: MIT arXiv:2606.08340 Hugging Face Models Website

Can LLM agents coordinate in long-horizon, open-ended tasks?

🌐 Website · 🏆 Leaderboard · ⚡ Evaluate an LLM · Submit a result · 📄 Paper · 🤗 Models

Alem is a JAX benchmark for open-ended multi-agent coordination. Building on Craftax and Multi-Agent Craftax / Craftax-Coop, Alem introduces procedurally generated coordination tasks, soft specialisation, communication, and controllable coordination difficulty into a long-horizon survival world with exploration, crafting, trading, and combat. The same world is exposed through symbolic, pixel, and text interfaces, making it usable by MARL agents, language agents, and humans.

Alem means world in Amharic.

93 achievements · 27 coordination goals · 3 difficulty tiers · 9 dungeon levels · episodes up to 10,000 steps · pure JAX

Contents

RL Playing · LLM Playing · Install · Quick Start · Evaluate an LLM · Configure · RL Agents · Baselines · Human Play · Docker · Package Layout · Development · RL vs LLM Interfaces · Reproduce the Paper · Submit to the Leaderboard · Errata · Contributing · Citation · License

RL Agents Playing

A team of MARL agents controlling the three players from symbolic observations, each acting from its own egocentric view.

RL agents playing Alem

Fast to train end-to-end in JAX. Full MARL training code and reference baselines live in baselines/; see Baselines.

LLM Agents Playing

The same world through the text interface. Each agent gets its own observation, broadcasts a free-form message to teammates every step and stores important information in scratchpad memory.

LLM agents reasoning and coordinating in Alem

Gemini 3.1 Pro (medium). THINKING = the agent's private plan; MESSAGE = what it broadcasts to the team. The view follows whichever agent is speaking; reasoning is typed out for readability, not the agents' real decision speed.

Three agents negotiate a synchronous action. They plan ahead, model each other, lock in a shared step, and then execute it together:

  • Plans ahead. Each agent commits to a turn-indexed plan (Step 5 Move · Step 6–7 Noop · Step 8 DO) and waits in position.
  • Theory of mind. A0 predicts a teammate's move will break the plan ("A2, your Step-6 DO will fail because A1 changed to Step 8"), and A1 catches the clash: "A0 and A2 sent conflicting times — EVERYONE DO ON STEP 8!"
  • Coordinates out loud. All three line up and DO the 3-agent tree on the same step.

See Evaluate an LLM to run it yourself.

👁️ Click to see what the agents actually see

Every step a language agent gets a system prompt (the rules, sent once) and a text observation (its current view), and must reply with an <action>, an optional <communication> broadcast, and an optional private <scratchpad>. We use progressive disclosure, where we only give relevant information for the current level in the prompt, and add information as agents get to more levels.

System prompt template. Placeholders in {…} are filled per agent/run (abridged; the full rules are sent verbatim):

You are Agent {id} ({role}) in a {num_agents}-agent cooperative survival game. Your goal is to gather resources, craft gear, fight monsters, and descend through {num_levels} dungeon levels, while coordinating with teammates. You must survive — if your health reaches zero, you die, and if all agents die the game ends. Maximize achievements while alive.

[ … full game rules: movement & facing, Do/interaction, crafting recipes, roles & specialist penalties, coordination (sync / handover / construction), the resource chain, and the {num_achievements} achievements …]

<output_format>
1. (Required) Exactly one action from the available list:
   <action>YOUR_CHOSEN_ACTION</action>
2. (Optional) Broadcast to teammates, up to {comm_char_limit} chars:
   <communication>YOUR_MESSAGE</communication>
3. (Optional) Private notes, up to {scratchpad_char_limit} chars — not shared; your only memory:
   <scratchpad>YOUR_NOTES</scratchpad>
Token budget: {token_budget} tokens for the full response (including reasoning).
</output_format>

View the full system prompt, filled in (a concrete 3-agent example on overworld).

Observation template. The structure every agent receives each step:

Step: {step}/{max_steps} ({steps_remaining} remaining, ends early if all agents die)
Position: (x={x}, y={y})
Role: {role}
Location: {dungeon_level}
Achievements: {unlocked}/{total} ({locked} unlock later)

You see:
- {object} {relative_position} (x={x}, y={y})
  ...one line per visible object...

Facing: {direction}. Do target: {object_in_front} (x={x}, y={y}).

Coordination:
- {object} (x={x}, y={y}): {how_this_object_must_be_coordinated}
  ...one line per coordination-relevant object...

Teammates:
Agent {id} ({role}): {relative_position} (x={x}, y={y}), health={hp}
  ...one line per teammate...

Your status: health {hp}, food {food}, drink {drink}, energy {energy}, mana {mana}, xp {xp}
Available actions: {legal_actions_this_step}

Filled-in example. What the warrior actually sees at step 0:

Step: 0/10000 (10000 remaining, ends early if all agents die)
Position: (x=24, y=24)
Role: warrior
Location: Overworld (surface)
Achievements: 0/93 (39 unlock later)

You see:
- stone 5 steps east (x=29, y=24)
- tree 1 step north and 2 steps west (x=22, y=23)
- construction_site 2 steps north (x=24, y=22)
- iron 3 steps south and 5 steps east (x=29, y=27)

Facing: north. Do target: grass (x=24, y=23).

Coordination:
- construction_site (x=24, y=22): requires 3 agents to Build simultaneously (fails alone).
- tree (x=26, y=23): one agent begins, another completes it within 6 steps (handover).
- stone (x=20, y=21): works solo, but a bonus when 3 agents Do simultaneously.

Teammates:
Agent 1 (forager): 1 step east (x=25, y=24), health=9
Agent 2 (miner): 1 step south (x=24, y=25), health=9

Your status: health 9, food 9, drink 9, energy 9, mana 9, xp 0
Available actions: Noop, Move {West,East,North,South}, Do, Sleep, Rest, Request {Food,Drink,Wood,Stone,Iron,Coal,Diamond,Ruby,Sapphire}

Install

uv venv --python 3.12
uv pip install alem-env # latest release from PyPI     

Or from source for development (editable install):

uv pip install -e .

Optional extras (work with either alem-env or -e .):

uv pip install -e ".[llm]"             # OpenAI-compatible LLM interface
uv pip install -e ".[play]"            # pygame human-play example
uv pip install -e ".[gpu]"             # NVIDIA CUDA 12 JAX wheels
uv pip install -e ".[baselines-rl]"    # JAX MARL trainers (see Baselines)
uv pip install -e ".[baselines-llm]"   # LLM-agent evaluation harness
uv pip install -e ".[dev]"             # pytest, ruff, jaxtyping

Plain pip also works (no uv required):

pip install -e .
pip install -e ".[gpu]"

Or pip install alem-env.

Quick Start

import jax
from alem.alem_env import make_alem_env_from_name

env = make_alem_env_from_name("Alem-Coop-Symbolic")
obs, state = env.reset(jax.random.PRNGKey(0))

rng_act = jax.random.split(jax.random.PRNGKey(1), env.num_agents)
actions = {agent: env.action_space(agent).sample(rng_act[i]) for i, agent in enumerate(env.agents)}

obs, state, rewards, dones, infos = env.step(jax.random.PRNGKey(2), state, actions)

Available environments:

Name Description
Alem-Coop-Symbolic Full multi-agent environment, symbolic observations
Alem-Coop-Pixels Full multi-agent environment, pixel observations
Alem-Coop-Symbolic-Debug Smaller debug environment, only overworld (first floor).
Alem-SingleAgent-Symbolic Single-agent variant (experimental)

Evaluate an LLM

Alem is an open leaderboard for multi-agent coordination: evaluate any OpenAI-compatible model and submit your score. Three agents play as a team through the text interface: each reasons privately, broadcasts a message to teammates, and keeps a scratchpad.

uv pip install -e ".[baselines-llm]"   # the LLM evaluation harness

Local model (vLLM or any OpenAI-compatible server). The same MODEL_ID drives all three agents:

# Install vLLM in a SEPARATE env; it pins its own torch/CUDA build that clashes with this repo's jax
uv venv --python 3.12 .venv-vllm
source ~/.venv-vllm/bin/activate
uv pip install vllm --torch-backend=auto

# Terminal 1: serve your model
vllm serve meta-llama/Llama-3.2-1B-Instruct --port 8000 

# Terminal 2: evaluate a 3-agent team on all leaderboard difficulties (from this repo's main env)
scripts/run_llm_eval.sh meta-llama/Llama-3.2-1B-Instruct \
    --base-url http://localhost:8000/v1 --episodes 20 --difficulty easy,medium,hard

Any OpenAI-compatible server works; vLLM is just the common choice for open models. See vLLM install docs for GPU/CPU build options.

Hosted API (OpenAI / Anthropic / Gemini / …):

export OPENAI_API_KEY=sk-...
python baselines/llm/eval_alem.py \
    clients.0.client_name=openai clients.1.client_name=openai clients.2.client_name=openai \
    clients.0.model_id=gpt-4o-mini clients.1.model_id=gpt-4o-mini clients.2.model_id=gpt-4o-mini \
    eval.num_episodes.alem=20

Swap client_name to anthropic, gemini, nvidia, or xai (and set the matching API key). Runs use the default robust_all agent + specific_collaborative prompt, the paper setup.

Try it before spending tokens. Run a cheap 5-step smoke test, or preview the text observations with no model at all:

scripts/smoke_llm.sh meta-llama/Llama-3.2-1B-Instruct --base-url http://localhost:8000/v1 --steps 5 --coord easy
uv run python examples/llm_text_smoke.py --coord easy --show-affordances   # no model calls

Prefer Docker? A single docker run serves your model with vLLM and runs the 3-agent eval, with no local install. See Docker → Evaluate an LLM.

Full harness reference: agent types, prompt modes, providers, per-agent configs, and metrics: baselines/llm/README.md. To publish a result: SUBMISSION.md.

Configure

from alem.alem_coop.alem_state import EnvParams, StaticEnvParams, get_coordination_params

env_params = EnvParams().replace(
    **get_coordination_params("easy"),
    soft_specialization=True,
    shared_reward=False,
)
static_env_params = StaticEnvParams(player_count=3, num_comm_channels=4)

env = make_alem_env_from_name(
    "Alem-Coop-Symbolic",
    env_params=env_params,
    static_env_params=static_env_params,
)

Coordination difficulty can be "none", "easy", "medium", "hard", or a numeric alpha in [0, 1].

RL Agents

A minimal framework-free rollout using symbolic observations and legal action masks:

uv run python examples/random_rl_agent.py --coord easy --steps 100
uv run python examples/random_rl_agent.py --players 2 --coord hard --steps 200

The example uses a jitted lax.scan loop and can serve as a template for custom policies. Full MARL training recipes (IPPO, HyperMARL-IPPO, MAPPO, PQN-VDN) live in baselines/; see Baselines.

Baselines

Reference MARL training code and the LLM-agent evaluation harness live under baselines/. Each RL algorithm is a single self-contained file (CleanRL-style) with a matching Hydra config; the LLM harness (derived from BALROG) drives 3 language agents through the text interface.

uv pip install -e ".[baselines-rl]"    # JAX MARL trainers (IPPO / MAPPO / PQN-VDN / HyperMARL)
uv pip install -e ".[baselines-llm]"   # LLM-agent evaluation harness
Guide What's inside
RL baselines → baselines/README.md IPPO / HyperMARL-IPPO / MAPPO / PQN-VDN trainers, run commands, and reloading the pretrained checkpoints from the paper.
LLM harness → baselines/llm/README.md Agent types, prompt modes, providers (vLLM / OpenAI / Anthropic / Gemini), configuration, and metrics.
cd baselines && python ippo_rnn.py TOTAL_TIMESTEPS=10000           # train an RL policy
cd baselines/llm && python eval_alem.py clients.0.client_name=openai \
    clients.1.client_name=openai clients.2.client_name=openai      # evaluate an LLM team

Human Play

Install the optional play dependencies first:

uv pip install -e ".[play]"
uv run python examples/play_alem.py
uv run python examples/play_alem.py --players 3 --coord easy --seed 42
uv run python examples/play_alem.py --players 2 --coord hard --god
Key Action
W A S D Move
Space Do / interact
Tab Sleep
E Rest
. / , Descend / ascend
Backspace Give to teammate
Q No-op

The game advances after all players have chosen an action.

Docker

Three images, each built from the repo root. Two of them run a full benchmark job in a single docker run; the container installs nothing and starts working immediately:

Image Dockerfile What one docker run does
alem-llm docker/Dockerfile.llm Serves your model with vLLM and runs a 3-agent LLM evaluation against it
alem-rl docker/Dockerfile.rl Runs a JAX MARL trainer (IPPO / MAPPO / PQN-VDN / HyperMARL)
alem-env docker/Dockerfile.env Lightweight environment-only image for the examples / your own code

Both alem-llm and alem-rl need nvidia-container-toolkit on the host and --gpus at runtime.

Evaluate an LLM in one command

docker build -f docker/Dockerfile.llm -t alem-llm .

# Serves the model with vLLM, waits until ready, then evaluates a 3-agent team.
# Only MODEL_ID is required; mount the HF cache so models are downloaded once.
docker run --rm --gpus all --shm-size=16g \
    -e MODEL_ID=meta-llama/Llama-3.2-1B-Instruct \
    -e HF_TOKEN=$HF_TOKEN \
    -v ~/.cache/huggingface:/app/.cache/huggingface \
    alem-llm eval.num_episodes.alem=5

Trailing arguments are Hydra overrides for the eval (e.g. eval.num_episodes.alem=5, alem.coordination_difficulty=hard). For a large model, shard across GPUs with -e VLLM_EXTRA_ARGS="--tensor-parallel-size 4" and a bigger --shm-size. To log to W&B, pass -e WANDB_API_KEY=... -e WANDB_MODE=online. Full knobs are in the header of docker/Dockerfile.llm.

Train an RL policy in one command

docker build -f docker/Dockerfile.rl -t alem-rl .

docker run --rm --gpus all -v "$PWD/outputs:/app/outputs" \
    alem-rl ippo_rnn TOTAL_TIMESTEPS=1e4 NUM_ENVS=16 SEED=0

The first argument is the trainer (ippo_rnn, ippo_rnn_nops, ippo_hypermarl_rnn, mappo_rnn, pqn_vdn_rnn); the rest are Hydra overrides. Run with no arguments to list the available trainers. Checkpoints and GIFs land in the mounted outputs/.

Environment-only image

# CPU (default)
docker build -f docker/Dockerfile.env -t alem-env .

# GPU: NVIDIA CUDA 12
docker build -f docker/Dockerfile.env --build-arg ALEM_ACCELERATOR=cuda12 -t alem-env:gpu .

The image uses the system Python (UV_SYSTEM_PYTHON=1), so inside a container you call python directly, no uv run prefix needed.

docker run --rm alem-env                                           # smoke test (default CMD)
docker run --rm --gpus all alem-env:gpu                            # GPU smoke test
docker run --rm alem-env python examples/random_rl_agent.py --steps 20
docker run --rm alem-env python examples/llm_text_smoke.py --coord easy
docker run --rm -it alem-env bash                                  # interactive shell

Human play is easiest natively: uv pip install -e ".[play]" then uv run python examples/play_alem.py. Pygame opens a real window with no display plumbing.

Running human play inside Docker (X11 setup)

Inside Docker, human play needs an X11 display and an image built with the play extra (so the SDL/X11 libs are present):

# Build with the play extra (adds pygame + SDL/X11 runtime libs)
docker build -f docker/Dockerfile.env --build-arg ALEM_EXTRAS=play -t alem-env:play .
  • Linux: grant the container access to your X server first (this is the step that's usually missing when the window never appears), then run it:
    xhost +local:root
    docker run --rm -it --network host -e DISPLAY=$DISPLAY \
        -v /tmp/.X11-unix:/tmp/.X11-unix alem-env:play python examples/play_alem.py
    xhost -local:root   # revoke when done
    
  • macOS / Windows: start XQuartz (macOS) or VcXsrv (Windows), enable "allow connections from network clients", then set DISPLAY accordingly.

Package Layout

Repository map: where each piece lives
Path Purpose
alem/alem_env.py Environment factory
alem/alem_coop/envs/ Symbolic, pixel, debug, and single-agent env classes
alem/alem_coop/alem_state.py State dataclasses and EnvParams / StaticEnvParams
alem/alem_coop/game_logic.py Step logic: movement, resources, combat, crafting, coordination
alem/alem_coop/world_gen/ Procedural world generation
alem/alem_coop/renderer/ Symbolic, pixel, and text renderers
alem/alem_coop/constants.py Actions, achievements, blocks, items, textures
alem/llm/ Text observations, action parsing, ASCII maps, LLM evaluator adapters
examples/random_rl_agent.py Masked-random symbolic rollout (RL template)
examples/llm_text_smoke.py Preview text observations without model calls
examples/llm_openai_smoke.py One-step OpenAI-compatible LLM smoke test
examples/play_alem.py Human pygame player

Development

uv pip install -e ".[dev]"   # pytest, ruff, jaxtyping
uv run pytest alem/tests/    # run the test suite
Lint & format (ruff)

Code style is enforced with ruff (config in pyproject.toml). CI runs these checks before the test suite, so run them locally first:

uv run ruff check .          # lint
uv run ruff format --check . # verify formatting

To auto-fix before committing:

uv run ruff check --fix .    # apply safe lint fixes
uv run ruff format .         # format the code

RL vs LLM Interfaces

Both interfaces drive the same environment but are not directly comparable; treat cross-paradigm scores as indicative, not head-to-head.

MARL (symbolic) LLM (text)
Observation Numeric vector Natural-language text
Communication A discrete signal on one of num_comm_channels (e.g. 4) Free-form text, ≤ 400 chars
Comms vs acting Costs your action that turn Sent alongside the action
Memory Recurrent hidden state Private <scratchpad> notes: not shared; the agent's only memory across steps.
Learning Trained from reward Zero-shot

(Request/Give resource transfers are ordinary actions in both.)

Text observations apply lightweight preprocessing, including compact local-state summaries (inspired by BALROG) and action affordances. See the language wrapper for details.

Reproduce the Paper

The paper's full experiments (the 13-LLM evaluation and the IPPO, HyperMARL-IPPO, MAPPO, PQN-VDN baselines) live in baselines/; see Baselines for launch commands and configs.

The paper's numbers were produced against Alem v0.1.0. For the exact settings to use when reporting an Alem number (seeds, episode count, metrics), see the canonical evaluation protocol.

Submit to the Leaderboard

Alem is an open benchmark. To add an LLM agent, MARL policy, or custom harness result to the leaderboard, follow SUBMISSION.md.

If your model is behind an OpenAI-compatible endpoint such as vLLM, the LLM path is one command:

scripts/run_llm_eval.sh YOUR_MODEL_ID --base-url http://localhost:8000/v1 --episodes 20 --difficulty easy,medium,hard

Use scripts/smoke_llm.sh YOUR_MODEL_ID --base-url http://localhost:8000/v1 --steps 5 --coord easy first for a cheap smoke test. Submissions should include enough detail to reproduce the run: model or algorithm, harness, coordination difficulty, seeds, metrics, evaluation date, and any non-default config. Pull requests are preferred, but issues and email submissions are also accepted.

Errata

Fixes that change environment behaviour are listed here, so numbers produced on different versions can be compared with the difference in mind. Report an Alem number together with the version it was produced on.

  • Prior to v0.2.0 - ladder placement. The up-ladder and down-ladder positions were drawn independently and never checked against each other, so they could share a row and the up-ladders would replace some of the down-ladders. Affected levels could have fewer ways down than intended. This should be a minor issue for most runs, but it does change generated worlds, so results from before and after the fix are not directly comparable.

  • Prior to v0.2.1 - lava bridging. Stone can now be placed into lava and mined into a walkable path, restoring Craftax's Fire Realm bridging mechanic without changing generated maps. This changes episode behaviour, but no agents have reached the Fire Realm yet, so it doesn't affect scores.

Contributing

Contributions are welcome: new baselines, bug fixes, docs, and coordination tasks. See CONTRIBUTING.md for the dev setup, lint/test workflow, and PR checklist, and CODE_OF_CONDUCT.md for community expectations.

Citation

@article{tessera2026alem,
  title   = {Benchmarking Open-Ended Multi-Agent Coordination in Language Agents},
  author  = {Tessera, {Kale-ab} Abebe and Szecsenyi, Andras and Barker, Cameron and
             Rutherford, Alexander and Paglieri, Davide and Scannell, Aidan and
             Gouk, Henry and Crowley, Elliot J. and Rockt\"{a}schel, Tim and
             Storkey, Amos},
  year    = {2026},
  url     = {https://arxiv.org/abs/2606.08340}
}

License

MIT. See LICENSE.

Download files

Download the file for your platform. If you're not sure which to choose, learn more about installing packages.

Source Distribution

alem_env-0.2.1.tar.gz (320.3 kB view details)

Uploaded Source

Built Distribution

If you're not sure about the file name format, learn more about wheel file names.

alem_env-0.2.1-py3-none-any.whl (411.3 kB view details)

Uploaded Python 3

File details

Details for the file alem_env-0.2.1.tar.gz.

File metadata

  • Download URL: alem_env-0.2.1.tar.gz
  • Upload date:
  • Size: 320.3 kB
  • Tags: Source
  • Uploaded using Trusted Publishing? Yes
  • Uploaded via: twine/7.0.0 CPython/3.13.14

File hashes

Hashes for alem_env-0.2.1.tar.gz
Algorithm Hash digest
SHA256 724fbb196941dfd31ae8d3a626fdaea3584e702a6c88851caa19758938f88896
MD5 f153653b47dadf5d371f95e9e225daa0
BLAKE2b-256 1b7cf4219a51e94e9608994b7908594117646bf9358c2e3f34b7ae4bf9ba9f41

See more details on using hashes here.

Provenance

The following attestation bundles were made for alem_env-0.2.1.tar.gz:

Publisher: publish.yml on alem-world/alem-env

Attestations: Values shown here reflect the state when the release was signed and may no longer be current.

File details

Details for the file alem_env-0.2.1-py3-none-any.whl.

File metadata

  • Download URL: alem_env-0.2.1-py3-none-any.whl
  • Upload date:
  • Size: 411.3 kB
  • Tags: Python 3
  • Uploaded using Trusted Publishing? Yes
  • Uploaded via: twine/7.0.0 CPython/3.13.14

File hashes

Hashes for alem_env-0.2.1-py3-none-any.whl
Algorithm Hash digest
SHA256 ff1014e703899c1edfdc1fe46884719becf2be059ec46015cccaeb54e5398c7c
MD5 5846d6957b4446102d63feda78408e20
BLAKE2b-256 8f372585d7515639be277c3e51d1f51531b171f399853eda676b3f396e9297b0

See more details on using hashes here.

Provenance

The following attestation bundles were made for alem_env-0.2.1-py3-none-any.whl:

Publisher: publish.yml on alem-world/alem-env

Attestations: Values shown here reflect the state when the release was signed and may no longer be current.

Release history Release notifications | RSS feed

This release

0.2.1 This release

2 files

0.2.0

2 files

0.1.0

2 files

Anthropic, PBC Visionary sponsor Bloomberg Visionary sponsor Hudson River Trading Visionary sponsor Meta Visionary sponsor NVIDIA Visionary sponsor Microsoft Sustainability sponsor Depot Continuous Integration AWS Cloud computing and Security Sponsor Datadog Monitoring Fastly CDN Google Download Analytics Sentry Error logging StatusPage Status page