Vigile
SearchContents

DocumentationOperations

remove_link

Remove a link between two items. The type is one returned by list_link_types. Built in: "contains" (a project or task groups a task), "depends on" (a task waits for a task or project) and "assigned to" (a task has a user working on it). Either the forward or the reverse name works: "A is contained B" is stored as "B contains A". Removing a "contains" link takes a task out of a project or parent task; removing a "depends on" link stops the task waiting for that item. The task the link was about moves one version on.

The operation's own description: what an agent reads to decide whether and how to call it.
It
Changes the plan, as one step that is stored whole or not at all.
Who may call it
Every user.
Version
Takes no version: it is carried out on the plan as it is at that moment.
Answers with
The link that was removed.
MCP tool
remove_link
HTTP
POST /api/remove-link
Command
vigile remove-link

Input

FieldTakesWhat it is
fromstringrequiredThe ID of the item the link starts at.
typestringrequiredThe link type, for example "depends on".
tostringrequiredThe ID of the item the link points at; a username works for a user.

A field that is not listed here is refused, as invalid_input. On the command line each field is an option, with hyphens for underscores: --from.

Example

The same call three ways, as agent1. It was made on the demo plan the pictures of this site show. Over HTTP and MCP, a call without a key acts as agent1 on a new instance.

Command line

vigile remove-link --from WEB-013 --type "depends on" --to WEB-010 --as agent1

HTTP

curl -s http://127.0.0.1:8700/api/remove-link \
  -H 'content-type: application/json' \
  -d '{"from":"WEB-013","type":"depends on","to":"WEB-010"}'

MCP tool call

{
  "name": "remove_link",
  "arguments": { "from": "WEB-013", "type": "depends on", "to": "WEB-010" }
}

The answer

{
  "removed": true,
  "link": { "from": "WEB-013", "type": "depends on", "to": "WEB-010" }
}

This is what a service answered when this page was built. Over HTTP it is the body of the response, over MCP the text of the tool result, and the command line prints it in words unless given --json.

What it answers

removed: true, and the link that was removed.

Rules

  • The link is named as it would be added: by its two ends and either name of its type.
  • Removing a "contains" link takes a task out of a project or a group. Removing a "depends on" link stops the task waiting for that item. Removing an "assigned to" link takes the task from that user.
  • It takes no version. The task the link was about moves one version on.
  • An end that is a project or task records in its history that the link is gone. A user does not: that a task was taken from a user is in the history of the task, and only there. See who records a link.

In the example the launch no longer waits for the accounts group. It still waits for the checkout and the search.

Errors

  • not_found: there is no such link, or one of the two items does not exist.
  • invalid_input: no such link type.