Independent software studio

Websites.
Apps.
AI tools.

Nosytlabs builds websites, web apps, and developer tools. The public projects below are our own. We also take on client work.

Explore our projects Work with us

Open source, built here

Five projects.
All on GitHub.

Explore the demos, read the docs, or open the code. Every project below has a public repository.

Nosytlabs on GitHub

Actual Agent Office dashboard from the README, showing a pixel-art workspace with synthetic agent activity.

README image · synthetic demo

Local dashboard

Agent Office

A local dashboard for coding agents. View sessions, reported usage, and requests for input in a pixel-art office.

GitHub Open demoJavaScript

Published skillstate-proxy documentation showing explicit state, setup links, and a state-patch example.

Published documentation

Local proxy

skillstate-proxy

A local HTTP proxy that builds model context from a task, structured state, and the latest observation.

GitHub Read docsTypeScript

Published employee.md documentation introducing the agent contract format and runtime boundaries.

Published documentation

Schema + tooling

employee.md

A YAML contract format for AI agents, with a JSON Schema, CLI validator, and Python runtime.

GitHub Read docsPython

Published Who’s Up North? site showing the live-clock statistical portrait and modeled Canadian activity.

Published site

Data visualization

Who's Up North?

Canadian local clocks and modelled daily activity, based on Statistics Canada time-use data.

GitHub Visit siteJavaScript

Published AURORA site introducing the independent Canadian UAP archive index.

Published site

Document index

AURORA

An independent index of Canadian federal UAP records, with case files, source links, and a map.

GitHub Visit siteHTML

A closer look

What the agent tools do.

Three separate projects for agent activity, context, and contracts. Each has its own setup guide and public source.

Context / local HTTP proxy

skillstate-proxy

Build the next turn from state.

Send the task, retained JSON state, and latest observation to your configured model provider. The proxy extracts a state_patch from the response for the next turn.

Setup guide Source code

Runs locally with your own upstream provider. Savings and compatibility depend on the workload.

One turn, illustratedNot a live request

Task
JSON state
Observation

Example model response

{
  "state_patch": {
    "step": 2,
    "notes": "Checked the input format"
  },
  "action": "Continue with validation"
}

What happens to the state?

The proxy merges the patch into retained state. Objects merge recursively, arrays are replaced, and null removes a key. Details omitted from state may be lost; keep a separate record if you need the full transcript.

See local agent activity