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.15

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.15
File Size Uploaded
noema_client-0.1.15.tar.gz 49.6 kB Details

Built distribution (wheel)

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

Total release size: 97.5 kB

Release files / noema_client-0.1.15.tar.gz

Download URL noema_client-0.1.15.tar.gz
Size 49.6 kB
Tags Source
SHA-256 checksum
How to use checksums
c6b4eff299d9993b7355fbd27352292ffdf4623693ac6bc64d4c5196b620a483
BLAKE2b-256 checksum
How to use checksums
fcacc6fc28a615f701b92b4168c60c0dd772f084870c9e52da8fc8457b0df601
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 24, 2026.

Transparency log

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

Download URL noema_client-0.1.15-py3-none-any.whl
Size 47.9 kB
Tags Python 3
SHA-256 checksum
How to use checksums
4bfae1ecc8de5ae37c9c5d726e3f27cd1d24f663f88a40af58bdc74871ebe6c7
BLAKE2b-256 checksum
How to use checksums
e0f03a934fb8060cd31df2d6ee759ae0a3f57231c4198c65add6b852bf90e2b4
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 24, 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

This release

0.1.15 This release

2 release files

0.1.14

2 release files

0.1.13

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