magus v0.4.2 is out. See what's new
¶ View generated markdown
1 min read

magus-version

Print the client and daemon versions

Synopsis

magus version [flags]

Description

Print the magus version string, git commit hash, and build date.

Two versions, because there can be two binaries: this one, and the daemon that has been serving the workspace since it was started. A daemon outlives the CLI that started it, so upgrading magus leaves the older code running until it is restarted - which is the case this command exists to show. The daemon line reads "not running" when nothing answers, and --client skips the probe entirely for a script that wants the build stamp with no daemon I/O.

In json and yaml the daemon key is present only when the probe ran: absent means it never ran (--client, or -o name, which prints the bare version and renders no daemon), and an empty value means it ran and nothing answered.

Options

--client
Print only this binary's version; skip the daemon probe entirely

Examples

Client and daemon

magus version

Just this binary, no daemon I/O

magus version --client

The bare version, for a CI pin comparison

magus version -o name

See Also

magus(1), magus-ls(1), magus-describe(1), magus-run(1), magus-x(1), magus-where(1), magus-affected(1), magus-graph(1), magus-query(1), magus-explain(1), magus-path(1), magus-refs(1), magus-watch(1), magus-events(1), magus-status(1), magus-clean(1), magus-vcs(1), magus-doctor(1), magus-config(1), magus-session(1), magus-memory(1), magus-notes(1), magus-diff(1), magus-server(1), magus-mcp(1), magus-buzz(1), magus-completion(1), magus-man(1), magus-init(1), magus-agent(1), magus-self(1)

ManpagePages in this section. magus statusShow effective config plus the live concurrency pool state of any running parent magus process, with optional --watch polling and --compact output. magus affectedRun a target for every project affected by a VCS diff, with forensic modes for explain, graph, CI shard plan, and regression bisect. magus graphEmit the project dependency DAG, export the knowledge graph for external graph tools, and report the graph's shape (god nodes, orphans, doc coverage).
generatedinternal/cli/registry.goclimagus versionversionbuild infocommitdaemon
Last updated (4f8cc295)
Earlier changes on this page (7)

Full history ↗ · Blame source ↗

Glossary

Workspace

The magus root directory that owns a set of projects and shared config; the unit magus operates over. See workspace.

Op

A single tool-native command a target composes (long form: operation); the middle of the work hierarchy (Spell to Op to Target). See operations.

Buzz

The language magusfiles are written in (the .buzz engine). See engines.

Affected

The set of projects touched by a change; magus affected <target> runs a target only over them. See affected.

Daemon

The background magus host that owns shared state such as services and the warm knowledge graph. See daemon.

CI

An ordinary magusfile-defined target you compose yourself with magus\needs - magus does not hardcode its stages. Magus.RunCI treats it specially only in that it strips the rw charm, it is the anchor magus affected ci keys off, and a selected scope with no project declaring it is a load error rather than a silent no-op. See targets.

MAGUS.md

The committed routing index at a workspace root, regenerated from the knowledge graph: it lists every node and points at the exact query for a given question, so it is the entry point an agent reads first. See knowledge.

Session

One magus process's recorded facts - the targets it finished, their outcomes, and the lease it acted as - kept in a repo-scoped store every worktree shares. magus session lists them; the store prunes itself by last-fact age.

Conventions

This page uses none of the site's convention markers. The full set is on the conventions page.