2

Source document

[2026-03-14 23:55] foxhop.: https://www.npmjs.com/package/@unturf/unfirehose-schema?activeTab=code [2026-03-15 00:02] foxhop.: would you like me to try to get unsandbox working in orcestra like i did for unfirehose? we may hide it behind a tab or something just for testing and proof of concept. [2026-03-15 00:02] foxhop.: if so, link me to your repo [2026-03-15 00:03] traves_theberge: that would be great do you have a sdk? [2026-03-15 00:04] traves_theberge: https://github.com/Traves-Theberge/Orchestra [2026-03-15 00:04] foxhop.: sort of I'll try to make one since you are type script. https://unsandbox.com/cli/typescript [2026-03-15 00:04] foxhop.: not tested [2026-03-15 00:04] foxhop.: except via functional tests but never integrated into a project. [2026-03-15 00:05] foxhop.: https://git.unturf.com/engineering/unturf/un-inception/-/blob/main/clients/typescript/sync/src/un.ts [2026-03-15 00:05] foxhop.: i might need to create an async version [2026-03-15 00:05] traves_theberge: or go because thats the backend [2026-03-15 00:06] traves_theberge: TS, GO, Python and C# would be great [2026-03-15 00:08] foxhop.: yeah we have a go one. [2026-03-15 00:08] foxhop.: https://git.unturf.com/engineering/unturf/un-inception/-/tree/main/clients/go [2026-03-15 00:08] foxhop.: https://git.unturf.com/engineering/unturf/un-inception/-/blob/main/clients/go/async/src/un_async.go 3k lines of go [2026-03-15 00:09] foxhop.: all the unsandbox rest API endpoints [2026-03-15 00:09] traves_theberge: sexy [2026-03-15 00:11] traves_theberge: do you have an implementaion guide ? [2026-03-15 00:11] foxhop.: you should stlil have unsandbox keys for fetch we may use those for this idea [2026-03-15 00:12] foxhop.: https://unsandbox.com/docs/go#quick-start [2026-03-15 00:12] foxhop.: ajax worked on this page a lot [2026-03-15 00:24] foxhop.: I'm going to try to add unsandbox two ways, one way is using vendoring should be seemless, other is to use `go get` using an environement var to trust my remote repo pinned to a version [2026-03-15 00:25] foxhop.: this is for my own understanding & learning you could pick either [2026-03-15 04:03] traves_theberge: this shit is getting good boys and gals (files: image.png) [2026-03-15 20:17] traves_theberge: (files: image.png) [2026-03-15 20:28] traves_theberge: So here the flow 1. You create a task with a title and description, and assign a project and "agent." 2. When you create a backlog item on the Task board, it creates an issue on GitHub for the associated project. <---> Likewise, if you create an issue in GitHub, it shows up in the Backlog. 3. When you move the task into TODO, it creates the plan based on the issue, then moves it to In Progress. 4. It executes the plan, then updates the issue on GitHub and moves the Task into review for the Human to review, and sends a notifcation to the user via a sound. 5. When you move from review to done, the GitHub issues closes. 6. You can then create a PR and merge it.