This repository provides clients for Meshline. Its first client, meshline, is a command-line application for people, scripts, and AI agents.
The CLI manages accounts, devices, contacts, encrypted direct and group messages, public channels, and local conversation history. An optional daemon keeps an account connected while other CLI processes issue commands. Each local profile belongs to one account.
meshline interactive --profile agent --json keeps a profile connected in one foreground process and accepts commands through stdin, without daemon IPC. See interactive sessions.
The client is a development preview. It uses published Meshline.Sdk 1.6.0 for synchronization, conversation state, message history, read positions, and retained send outcomes. Account setup is resumable, and chat/contact notifications for recipients are requested automatically by the SDK.
Download the archive for your platform and SHA256SUMS from the latest GitHub Release. The initial development-preview release is v0.1.0.
| Platform | Archive |
|---|---|
| Windows x64 | meshline-<version>-win-x64.zip |
| Linux x64 | meshline-<version>-linux-x64.tar.gz |
Verify the archive checksum, extract it into a writable directory, and put that directory on your PATH. Packages include the executable, default config.json, and these documents; no separate .NET installation is required. Linux packages target Ubuntu 24.04 x64 and still require the operating system's native libraries. macOS packages are not provided.
See installation and first use for platform-specific steps, or development to build from source. Follow the upgrade procedure when replacing an existing installation.
With meshline on PATH, run the following from a writable working directory. These single-line commands work in PowerShell and a Linux shell. The network and RPC below are an example Neo mainnet configuration; RPC availability is not guaranteed.
meshline account create --network neo:860833102:0x5979ba79431672a38a18a32cdc48fd7317818b70 --rpc https://n3seed1.ngd.network:10332 --protection file --key-file ./secrets/default.key --generate-key
meshline relays list --jsonChoose an active Relay from the result and replace RELAY_ID below:
meshline account establish --relay "RELAY_ID" --timeout 180
meshline daemon start --timeout 180
meshline account sync --json
meshline status --jsonAccount creation also creates its local profile. There is no initialization or configuration-generation command. The CLI reads config.json beside the executable unless --config selects another existing file. Keep the external key file: it is required to unlock this profile.
Continue with your first conversation, which walks through both participants, contact approval, sending, and reading.
Use file protection or an appropriate platform credential provider for unattended execution. Use --json for compact results, keep a daemon running for background synchronization or explicitly run account sync, and inspect operation state before retrying an uncertain write. Page history with --after/--before and acknowledge viewed content with conversations mark-read --sequence. Reading messages does not mark them read.
The automation guide defines output, exit codes, delivery states, event handling, and a minimal processing loop. watch is a live event stream without durable replay; a successful daemon start does not mean history synchronization has finished.
| Task | Guide |
|---|---|
| Install and exchange a first message | Getting started |
| Look up any command or option | Complete command reference |
| Choose configuration paths and manage profiles | Configuration |
| Integrate a script or Agent | Automation |
| Run daemons, deploy, back up, and upgrade | Operations |
| Choose key protection and understand its limits | Security |
| Diagnose errors and check known limitations | Troubleshooting |
| Build, test, package, and develop the client | Development |
Linux builds and offline credential/signal checks have passed, but ordinary-user daemon socket lifecycle and the complete systemd service deployment still need live acceptance. Cross-Relay delivery and home-Relay migration also remain unverified without a second Relay.
Account authority recovery does not restore deleted local history or guarantee immediate contact/key synchronization. See known limitations before relying on unattended operation.