flightdesk 0.4.3 → 0.6.0
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- package/README.md +48 -12
- package/main.js +414 -85
- package/main.js.map +4 -4
- package/package.json +1 -1
package/README.md
CHANGED
|
@@ -35,18 +35,18 @@ flightdesk status
|
|
|
35
35
|
|
|
36
36
|
## Commands
|
|
37
37
|
|
|
38
|
-
| Command
|
|
39
|
-
|
|
40
|
-
| `flightdesk init`
|
|
41
|
-
| `flightdesk register` | Register a session with a task
|
|
42
|
-
| `flightdesk task`
|
|
43
|
-
| `flightdesk status`
|
|
44
|
-
| `flightdesk prompt`
|
|
45
|
-
| `flightdesk org`
|
|
46
|
-
| `flightdesk context`
|
|
47
|
-
| `flightdesk sync`
|
|
48
|
-
| `flightdesk project`
|
|
49
|
-
| `flightdesk preview`
|
|
38
|
+
| Command | Description |
|
|
39
|
+
| --------------------- | -------------------------------------- |
|
|
40
|
+
| `flightdesk init` | Configure API credentials |
|
|
41
|
+
| `flightdesk register` | Register a session with a task |
|
|
42
|
+
| `flightdesk task` | Create, list, and manage tasks |
|
|
43
|
+
| `flightdesk status` | Show status of all active tasks |
|
|
44
|
+
| `flightdesk prompt` | Get prompts ready to paste into Claude |
|
|
45
|
+
| `flightdesk org` | Manage organization connections |
|
|
46
|
+
| `flightdesk context` | Show current repo/org mapping |
|
|
47
|
+
| `flightdesk sync` | Refresh project-to-repo mappings |
|
|
48
|
+
| `flightdesk project` | Project management commands |
|
|
49
|
+
| `flightdesk preview` | Preview environment management |
|
|
50
50
|
|
|
51
51
|
## Multi-Organization Support
|
|
52
52
|
|
|
@@ -72,3 +72,39 @@ Full documentation available at **[flightdesk.dev/docs](https://flightdesk.dev/d
|
|
|
72
72
|
## License
|
|
73
73
|
|
|
74
74
|
This software is proprietary. See [flightdesk.dev](https://flightdesk.dev) for licensing information.
|
|
75
|
+
|
|
76
|
+
## Command center and Qalatra dispatch
|
|
77
|
+
|
|
78
|
+
FlightDesk records requests; Qalatra owns execution. Use an invited user marked `AGENT` by an
|
|
79
|
+
organization administrator, and authenticate the CLI with that user's organization-scoped token.
|
|
80
|
+
Node URLs and bindings are private and are never included in people lists.
|
|
81
|
+
|
|
82
|
+
```bash
|
|
83
|
+
flightdesk agent-bind --path agents/shi --node https://qalatra.example.com
|
|
84
|
+
flightdesk dispatch list
|
|
85
|
+
flightdesk dispatch update REQUEST_ID --status ACKNOWLEDGED --job QALATRA_JOB_ID
|
|
86
|
+
flightdesk dispatch update REQUEST_ID --status RUNNING
|
|
87
|
+
flightdesk comment TASK_ID --body "Implementation finished; checks passed."
|
|
88
|
+
flightdesk dispatch update REQUEST_ID --status DONE
|
|
89
|
+
```
|
|
90
|
+
|
|
91
|
+
Transitions are `REQUESTED → ACKNOWLEDGED → RUNNING → DONE`; any open stage may become `FAILED`.
|
|
92
|
+
Updates and polling are restricted to the request's agent and the token's organization. Qalatra
|
|
93
|
+
must deduplicate queued jobs by dispatch request ID before acknowledging. Polling is the contract;
|
|
94
|
+
there is no outbound webhook or agent execution in FlightDesk.
|
|
95
|
+
|
|
96
|
+
Human organization owners/admins may explicitly request work:
|
|
97
|
+
|
|
98
|
+
```bash
|
|
99
|
+
flightdesk dispatch request TASK_ID --agent AGENT_USER_ID --kind PLAN --prompt "Prepare a plan"
|
|
100
|
+
flightdesk comment TASK_ID --body "Explain the tradeoffs" --ask-agent
|
|
101
|
+
```
|
|
102
|
+
|
|
103
|
+
MCP equivalents are `bind_agent`, `list_dispatch_requests`, `update_dispatch_request`,
|
|
104
|
+
`request_dispatch`, `add_task_comment`, `list_task_comments`, and `transition_work_status`.
|
|
105
|
+
`list_tasks` also accepts `assigneeId` and `openDispatch`. A normal comment, including an `@agent`
|
|
106
|
+
mention, is stored as data and does not request execution.
|
|
107
|
+
|
|
108
|
+
Tasks now expose nullable `runStatus` and an independent `workStatusId`. GraphQL `status` remains
|
|
109
|
+
a deprecated alias for existing clients; MCP task detail responses also retain the alias. General
|
|
110
|
+
tasks have no run status and cannot enter GitHub or preview operations.
|