ipfs/kubo · error

removed, use 'ipfs dag' or 'ipfs files' instead

Error message

removed, use 'ipfs dag' or 'ipfs files' instead

What it means

RemovedObjectCmd is the placeholder command registered for subcommands of the removed `ipfs object` surface. Its status is cmds.Removed and its Run always returns this error: the functionality was deleted from kubo and users are pointed at `ipfs dag` or `ipfs files`. It exists only so old invocations fail with an instructive message.

Source

Thrown at core/commands/object/object.go:48

	Subcommands: map[string]*cmds.Command{
		"data":  RemovedObjectCmd,
		"diff":  ObjectDiffCmd,
		"get":   RemovedObjectCmd,
		"links": RemovedObjectCmd,
		"new":   RemovedObjectCmd,
		"patch": ObjectPatchCmd,
		"put":   RemovedObjectCmd,
		"stat":  RemovedObjectCmd,
	},
}

var RemovedObjectCmd = &cmds.Command{
	Status: cmds.Removed,
	Helptext: cmds.HelpText{
		Tagline: "Removed, use 'ipfs dag' or 'ipfs files' instead.",
	},
	Run: func(req *cmds.Request, res cmds.ResponseEmitter, env cmds.Environment) error {
		return errors.New("removed, use 'ipfs dag' or 'ipfs files' instead")
	},
}

View on GitHub (pinned to 329838acdf)

Solutions

1. Replace `ipfs object <sub>` with the equivalent `ipfs dag` or `ipfs files` command (e.g. `ipfs object get` -> `ipfs dag get`, `ipfs object links` -> `ipfs dag get` and inspect Links).
2. Update scripts/docs to stop referencing the removed object command tree.
3. For DAG-PB inspection use `ipfs dag get <cid>` or `ipfs dag stat <cid>`.

Example fix

// before
ipfs object links <cid>
// after
ipfs dag get <cid>   # parse the "Links" array of the dag-pb node

// detect removed commands before running them
if strings.HasPrefix(cmdPath, "ipfs object ") {
    return errors.New("'ipfs object' is removed; use 'ipfs dag' or 'ipfs files'")
}

When it happens

Trigger: Invoking any subcommand that resolves to RemovedObjectCmd, e.g. `ipfs object data`, `ipfs object links`, `ipfs object stat` (whichever were removed) on a current kubo build.

Common situations: Scripts and tutorials written years ago for `ipfs object` commands; automation not updated after the deprecation/removal (kubo issue #7936); users following outdated documentation.

Related errors

• supernode routing was never fully implemented and has been r
• unrecognized routing option: %s
• deprecated configuration detected. Manually migrate 'Provide
• deprecated configuration detected. Manually migrate 'Reprovi
• invalid configuration profile: %s

AI-assisted analysis of ipfs/kubo@329838acdf (2026-09-03). Data as JSON: /api/errors/16ed553457d8c8eb. Report an issue: GitHub.