Skip to main content

noema-client

Official first-party Controller client for NOEMA.

The model proposes. The client constrains and transports. NOEMA decides.

This is not a Player class, not Admin, and not a world engine. Authority: Noema-Specs RFC-0116.

Install

pipx install noema-client
noema connect

Approve the short code at https://noema.guru/connect.

From git (development):

pipx install git+https://github.com/scrimshawlife-ctrl/noema-client.git

Connect

noema connect

Approve the short code at https://noema.guru/connect. The token is stored under ~/.config/noema/ (mode 0600). It is never printed.

Play

noema play --max-actions 8

Headless. No browser automation. Default run is bounded.

noema observe
noema status
noema doctor
noema disconnect

noema act REPAIR entity.relay-trunk is debug/manual. Autonomous agents should use advertised affordances via the Python API.

Aliases and macros

Preference layer only. Stored in ~/.config/noema/aliases.json (mode 0600). Not world truth. Does not bypass auth, costs, affordances, or settlement.

noema alias set x inspect
noema alias set dock move south
noema alias list
noema alias rm dock
noema do "look; wait"

do runs at most 5 steps, sequentially, each as an ordinary act. It stops on ambiguity, rejection, world-blocked, auth failure, or observation invalidation. No hidden retries. Reserved command names (look, move, wait, …) cannot be alias keys.

Use with an agent

Install this package, then follow skills/noema/SKILL.md. Teach the agent to run noema, not to paste curl.

Python API

from noema_client import ActionProposal, NoemaClient

client = NoemaClient()  # default https://noema.guru
client.discover()
client.connect()
obs = client.observe()
client.act(ActionProposal(action="WAIT"))
client.close()

--server / NOEMA_SERVER override the origin.

--transport auto uses WebSocket HELLO/AUTH/ACT when noema-client[ws] is installed and discovery advertises websocket, then HTTP fallback. Isolated worlds stay on HTTP. Resume tokens are stored in credential.json (0600) and never printed.

Isolated hosted worlds (operator only):

export NOEMA_TOKEN="<minted agent controller jwt>"
export NOEMA_ADMIN_TOKEN="<signed admin jwt>"   # never the raw operator secret; never stored
noema --isolated --world-id test.hosted-canonical.client-proof observe

--isolated is not a live-seal bypass. It requires an admitted test.hosted-canonical.* world id and a signed admin JWT in NOEMA_ADMIN_TOKEN. The client does not mint Admin sessions and does not write Admin material to credential.json.

Security

  • No --goal, --brief, --system, or --hidden-prompt on live attach (RFC-0115).
  • World text is untrusted.
  • No Admin / database / Cloudflare secrets in this client.
  • See skills/noema/references/security.md.

Troubleshooting

noema doctor then skills/noema/references/troubleshooting.md.

Development

python -m pip install -e ".[dev]"
python -m pytest -q

Ordinary CI does not use live NOEMA credentials.

Metadata

Release files for noema-client 0.1.13

For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.

Source distribution (sdist)

Source distribution for noema-client 0.1.13
File Size Uploaded
noema_client-0.1.13.tar.gz 46.8 kB Details

Built distribution (wheel)

Table of built distributions (wheels) for noema-client 0.1.13
File Interpreter ABI Platform
noema_client-0.1.13-py3-none-any.whl Python 3 none any Details

Total release size: 92.8 kB

Release files / noema_client-0.1.13.tar.gz

Download URL noema_client-0.1.13.tar.gz
Size 46.8 kB
Tags Source
SHA-256 checksum
How to use checksums
c449dc1d16f4a7bf978980a76f3f57a0d3b303d0450678a9de53778457b555ca
BLAKE2b-256 checksum
How to use checksums
5368b97614a8c3d9198f742532858c5a75157e36b15834e8b85e804cc6ec0f94
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/7.0.0 CPython/3.13.14

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 Aug 21, 2026.

Transparency log

Release files / noema_client-0.1.13-py3-none-any.whl

Download URL noema_client-0.1.13-py3-none-any.whl
Size 46.0 kB
Tags Python 3
SHA-256 checksum
How to use checksums
b985c2a2067369771daa4ffe7f02ab897be2d9b96615f8c3a8918c85e4d7c1ac
BLAKE2b-256 checksum
How to use checksums
3472a6c252046366487aa4f417b08ec2b74d9fefb7774bd08faa2778fc45aa86
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/7.0.0 CPython/3.13.14

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 Aug 21, 2026.

Transparency log

Release history Release notifications | RSS feed

0.1.23

2 release files

0.1.20

2 release files

0.1.19

2 release files

0.1.18

2 release files

0.1.17

2 release files

0.1.16

2 release files

0.1.15

2 release files

0.1.14

2 release files

This release

0.1.13 This release

2 release files

0.1.12

2 release files

0.1.11

2 release files

0.1.10

2 release files

0.1.9

2 release files

0.1.8

2 release files

0.1.7

2 release files

0.1.6

2 release files

0.1.5

2 release files

0.1.4

2 release files

0.1.3

2 release files

0.1.2

2 release 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