Tasks and trackers

Tasks live on the canvas as cards, while the source of truth stays in the tracker: GitHub, Gitea, knower or your own system with a description.

The "Task" node

"Components → ✅ Task" places a card with a todo, doing or done status, an assignee, a description, a due date, labels and a checklist. Tasks connect by edges to any nodes: screens, tables, code.

Tasks from a tracker

"Data → ✅ Tasks from tracker…": choose the tracker kind, the agent and the project. GitHub is read by an agent with gh installed and gh * allowed in agent.json, Gitea through tea, knower over HTTP. Tasks land in a group "Tasks: project". Reading again updates the group in place, your doing statuses and arrangement stay.

In the task inspector: "↑ to tracker" sends the difference, a new task is created and receives its number and link from the response, an edit updates, done closes, and back reopens. "↓ refresh" re-reads, "↗ open" leads to the tracker. The link is kept by a key such as github:owner/repo#12.

The "Tracker" node

How tasks are read and written is described by the "🔗 Tracker" node: kind, project, agent, address, release and, when needed, your own JSON description instead of the built-in one. The description sets request templates list, create, edit, close and reopen with ${project}, ${number}, ${title}, ${body}, ${assignee}, ${state}, ${base}, ${release} and conditional fragments, plus response parsing: the path to the list, paths to record fields, the values of the closed state, where to take the number of a created task.

Command-line descriptions are run by the agent's exec, HTTP descriptions by the agent's http:

"http": {
  "allow": ["https://tracker.example.com/"],
  "headers": {"https://tracker.example.com/": {"Authorization": "Bearer …"}},
  "timeoutSeconds": 30
}

Addresses come only from the allow list, headers with tokens and cookies are added by the agent and never reach the cloud or the nodes.

Built-in descriptions

github through gh, gitea through tea, knower over HTTP to its "Tracker" section. Your own tracker is described the same way.

← Project: jobs, meta-language, build chain Database schema, migrations and the grid with writes →