Glad you figured it out.

That dos remind me of having many terminal tabs open and sometimes it's hard to tell which is which.

I separate them by windows and other tabs in proximity.

How can we make them more distinguishable? App name in tab?

@andreasdueren in /app/data or browser?

Always good to check the logs for progress

If I need to open a terminal for an app, the search finds it but then I have to change screens to app configuration to access power, fm, term, etc

I'd like to see those icons right in a column below the gear icon of the square tile for easier access.

One click fm!

Some workarounds:

You can check other php apps that may have it packaged to run it from the surrogate container.

You would otherwise have to find a statically compiled binary that includes it.

Or investigate installing a user local php with its own extensions and edit the apache config in LAMP.

That is expected. No?

Thanks my bad.

Official website: nullclaw.io

NullClaw

Null overhead. Null compromise. 100% Zig. 100% Agnostic.
678 KB binary. ~1 MB RAM. Boots in <2 ms. Runs on anything with a CPU.

The smallest fully autonomous AI assistant infrastructure — a static Zig binary that fits on any $5 board, boots in milliseconds, and requires nothing but libc.

Docs: English · 中文 · Contributing

678 KB binary · <2 ms startup · 5,300+ tests · 50+ providers · 19 channels · Pluggable everything

Features

• Impossibly Small: 678 KB static binary — no runtime, no VM, no framework overhead.
• Near-Zero Memory: ~1 MB peak RSS. Runs comfortably on the cheapest ARM SBCs and microcontrollers.
• Instant Startup: <2 ms on Apple Silicon, <8 ms on a 0.8 GHz edge core.
• True Portability: Single self-contained binary across ARM, x86, and RISC-V. Drop it anywhere, it just runs.
• Feature-Complete: 50+ providers, 19 channels, 35+ tools, 10 memory engines, multi-layer sandbox, tunnels, hardware peripherals, MCP, subagents, streaming, voice — the full stack.

Why nullclaw

• Lean by default: Zig compiles to a tiny static binary. No allocator overhead, no garbage collector, no runtime.
• Secure by design: pairing, strict sandboxing (landlock, firejail, bubblewrap, docker), explicit allowlists, workspace scoping, encrypted secrets.
• Fully swappable: core systems are vtable interfaces (providers, channels, tools, memory, tunnels, peripherals, observers, runtimes).
• No lock-in: OpenAI-compatible provider support + pluggable custom endpoints.

Benchmark Snapshot

Local machine benchmark (macOS arm64, Feb 2026), normalized for 0.8 GHz edge hardware.

	OpenClaw	NanoBot	PicoClaw	ZeroClaw	🦞 NullClaw
Language	TypeScript	Python	Go	Rust	Zig
RAM	\> 1 GB	\> 100 MB	< 10 MB	< 5 MB	~1 MB
Startup (0.8 GHz)	\> 500 s	\> 30 s	< 1 s	< 10 ms	< 8 ms
Binary Size	~28 MB (dist)	N/A (Scripts)	~8 MB	3.4 MB	678 KB
Tests	—	—	—	1,017	5,300+
Source Files	~400+	—	—	~120	~230
Cost	Mac Mini $599	Linux SBC ~$50	Linux Board $10	Any $10 hardware	Any $5 hardware

Measured with /usr/bin/time -l on ReleaseSmall builds. nullclaw is a static binary with zero runtime dependencies.

Reproduce locally:

zig build -Doptimize=ReleaseSmall
ls -lh zig-out/bin/nullclaw

/usr/bin/time -l zig-out/bin/nullclaw --help
/usr/bin/time -l zig-out/bin/nullclaw status

Documentation

Start here if you want the shortest path to install, configure, operate, or extend nullclaw.

Localized documentation lives under docs/en/ and docs/zh/. Use the links below to jump straight to the page you need.

Need	English	中文
Start here	docs/en/README.md	docs/zh/README.md
Install	docs/en/installation.md	docs/zh/installation.md
Configure	docs/en/configuration.md	docs/zh/configuration.md
Commands	docs/en/commands.md	docs/zh/commands.md
Development	docs/en/development.md	docs/zh/development.md
Operations	docs/en/usage.md	docs/zh/usage.md
Architecture	docs/en/architecture.md	docs/zh/architecture.md
Security	docs/en/security.md	docs/zh/security.md
Gateway API	docs/en/gateway-api.md	docs/zh/gateway-api.md

• Specialized guides: CONTRIBUTING.md, SECURITY.md, SIGNAL.md

Add to this LightPanda headless browser and you gain speed and drop overhead.

Would love to see this integrated in Change Detection App as well.

Steel

The open-source browser API for AI agents & apps.
The best way to build live web agents and browser automation tools.

Get Started · Documentation · Website · Cookbook

Steel Demo

Highlights

Steel.dev is an open-source browser API that makes it easy to build AI apps and agents that interact with the web. Instead of building automation infrastructure from scratch, you can focus on your AI application while Steel handles the complexity.

Under the hood, it manages sessions, pages, and browser processes, allowing you to perform complex browsing tasks programmatically without any of the headaches:

• Full Browser Control: Uses Puppeteer and CDP for complete control over Chrome instances -- allowing you to connect using Puppeteer, Playwright, or Selenium.
• Session Management: Maintains browser state, cookies, and local storage across requests
• Proxy Support: Built-in proxy chain management for IP rotation
• Extension Support: Load custom Chrome extensions for enhanced functionality
• Debugging Tools: Built-in request logging and a UI to view/debug sessions with
• Anti-Detection: Includes stealth plugins and fingerprint management
• Resource Management: Automatic cleanup and browser lifecycle management
• Browser Tools: Exposes APIs to quick convert pages to markdown, readability, screenshots, or PDFs.

For detailed API documentation and examples, check out our API reference or explore the Swagger UI directly at http://0.0.0.0:3000/documentation.

Steel is in public beta and evolving every day. Your suggestions, ideas, and reported bugs help us immensely. Do not hesitate to join in the conversation on Discord or raise a GitHub issue. We read everything, respond to most, and love you.

If you love open-source, AI, and dev tools, we're hiring across the stack!

There are many packaged apps that do this as a first run setup then not.

You can check for logs, unique config signatures, db entry, .first_run file or other hints first run and setup is done.

Do any placeholder vars prevent the crash?

Dedup FTW

Woohoo! 2023 -> 2026

@nebulon if nothing in the code calls it, is there an external script or cron?

@archos interesting it knows how to access the old doc to make a new copy.

Nice find!

It doesn't seem to make sense to separate the versions file from the source.

Since the architecture requires this for public pulls, it would make sense to have a homegrown vanilla implementation where this is taken care of.

In the case of the private registry, how could this be solved?

1. Exposing a designated source file via a local webserver at a specific path, such as .well-known/ - possibly automated by a script scanning all repos for such files, then linking them to the hosted exposed spot
2. A new addon for this purpose which accomplishes the above, which may be useful to use in other projects that need things for autodiscovery
3. Runner type workflows that work to set something like this up from the source side?
4. Cloudron provided hosting for such packages with self management capabilities?
5. Docker image hints/artifacts that can serve as a versions file???
6. Your turn..

So it could be made public with an agreed upon default app password such as 'cloudron'

@joseph