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

magus-clean

Remove declared outputs (regenerable, never sources)

Synopsis

magus clean [flags] [project...]

Description

Remove the declared Outputs of the selected projects. With no project arguments the cwd project (or the whole workspace, from the root) is selected.

These are the same files the cache snapshots and replays on a hit. Whether each one is regenerable is the declaration's claim, not something clean verifies - so a file magus only modifies rather than produces belongs in ctx.modifiesExistingFiles, which clean never removes. Preview with the global --dry-run flag before trusting a declaration you have not read.

--cache additionally invalidates the magus cache entries for those projects, which is what forces a genuinely full rebuild: removing the files alone leaves the entries that would replay them.

Options

--cache
Also invalidate magus cache entries for the selected projects

Examples

Preview what would be removed

magus clean --dry-run

Clean one project

magus clean web

Clean and force a full rebuild

magus clean --cache

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-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), magus-version(1)

ManpagePages in this section. 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). magus runRun a named target (build, test, lint, format, ci, etc.) for the selected projects, defaulting to the cwd project when no arguments are given.
generatedinternal/cli/registry.goclimagus cleanoutputscacheartifactsrebuild
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.

Project

A directory magus recognizes as a unit of work (it has a magusfile); the unit of caching, scheduling, and dependency tracking. 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.

Cache

The content-addressed store magus consults before running a target, so unchanged work is skipped. See cache.

Affected

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

Snapshot

A point-in-time view of live state - the pool's occupancy or a tick of exported metrics - as opposed to accumulated history. See daemon.

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.