Task Servers

Settings screen where you add Jira and GitHub issue trackers, store a pass path for the token, and test the connection.

packages/task-servers

Task Servers holds the connection details for the issue trackers that other RobOS apps use. It does not show issues itself.

Use it

  1. Click the plus button and choose a type: Gitea (Local OSS Forge), Jira / Atlassian, GitHub Issues, GitLab Issues, Linear or Azure DevOps.
  2. Fill in the form.
    • Jira: Jira Base URL, Username / Email, API Token, and Project Keys. The token field takes a pass entry, chosen with Select pass entry, so the token is read from your password store and not saved in settings.json.
    • GitHub: GitHub API URL (blank for github.com, or a GitHub Enterprise API URL), Use Git client account (use the gh CLI login; otherwise a Personal Access Token from pass), a list of repositories as Org / Owner and Repository pairs, and labels to include.
    • Gitea, GitLab, Linear, Azure DevOps: a generic form with an API / instance URL and username or email.
  3. Click Test Connection (Jira and GitHub forms only). Jira is checked with curl against the Jira API, GitHub with gh api user or curl against <api url>/user. Other types have no test.
  4. Changes are saved to the task_servers array in ~/.config/robos/settings.json. Delete a server with the X next to it in the list.

The server entries are also mirrored into the knowledge graph as task server nodes when packages/robos-graph is available.

Who reads the list

App Server types it uses
Task Planner GitHub (via gh) and Jira
Task Implementer GitHub and Jira
Task Board GitHub only
Report Builder The first repository of the server, through gh
Stage Demo GitHub only

Those apps use the server whose id equals active_task_server in settings.json, or the first server in the list if that key is not set. This app has no control for active_task_server, so order the list or set the key by hand. The other types can be saved but the apps above do not use them.

Run it

Launch RobOS Task Servers from the app launcher, or run npm start in packages/task-servers.

More in Architecture & Planning

Automation Studio

Editor for event rules and cron-style scheduled jobs, plus a viewer for the daily event log.

Issue Manager

Opens one GitHub issue, shows it with its workflow state, moves it between states by changing labels, and sets up a branch workspace for it.

Knowledge Graph Explorer

Browse, search, edit and validate the knowledge graph of your software, compare main with a branch, and import or refine graph data from source repositories.

People Directory

Searchable list of people with contact and org fields, stored as JSON files on your machine.

People Manager

Prototype roster screen for teams of people and AI agents, grouped by Team Topologies type. It shows built-in sample data.

RobOS Create Project & App Wizard

Scaffold a new project from an archetype, or import an existing folder, and register it in the RobOS project files.

RobOS Documentation

Lists the components in the knowledge graph, shows which have a documentation page, and lets you generate, edit and export those pages.

RobOS Group Manager

Create and edit developer groups (members, repositories, software, onboarding steps, secrets, CI) and set up a sample company identity.

Schema Studio & Registry

Browse the bundled Schema.org vocabulary, generate JSON-LD, TypeSpec, SHACL and code stubs for a new entity, and validate JSON-LD against RobOS shapes.

System Topology Studio

Prototype C4-style canvas that shows a built-in sample system (Acme Petshop). Backstage import and C4 export return canned results.

Task Board

Read-only board and list view of the issues in the active GitHub task server, grouped by status.

Workflow Studio

Define issue types, states and transitions for a GitHub task server, move an issue between states, and run a script or AI prompt when it enters a state.