norien
Open app

Changelog

Norien is built in phases. Each one below is complete and running.

  1. Phase 8current

    Frontend & marketing site

    • Public marketing site: landing, docs, pricing, blog, changelog, about, contact, legal.
    • Application shell with a persistent sidebar, topbar, and mobile drawer.
    • Dashboard with eight live widgets across market, ecosystem, and registry data.
    • Registry, marketplace, runtime, publish, API keys, profile, and settings pages.
    • Warm cream and brown design system replacing the previous dark theme.
    • GitHub sign-in via Supabase Auth (backend verifies the session JWT).
  2. Phase 7

    Product surface & developer experience

    • Market data commands in the CLI: markets, trending, token, wallet, contract, project.
    • Unified search spanning the registry and market data.
    • SDK namespaces for tokens, projects, contracts, wallets, chain, and market search.
    • First web application, streaming each dashboard panel independently.
  3. Phase 6

    External data integration

    • Six providers normalized behind one API: market, on-chain, repository, and TVL data.
    • Every response carries its provenance; a failing provider degrades rather than errors.
    • One outbound client owning timeout, retry with backoff, caching, and structured logging.
    • Stale-on-failure cache: a slightly old answer beats no answer.
  4. Phase 5

    Tool marketplace

    • Tools as first-class published records with input and output schemas.
    • One plugin protocol across node, python, and http runtimes.
    • Seventeen categories, versioning, search, and dependency resolution.
    • norien tool commands and client.tools in both SDKs.
  5. Phase 4

    Agent runtime

    • A supervisor that runs installed agents: run, stop, restart, logs, status.
    • Health probing separate from process status, so both can be reported honestly.
    • Crash recovery with a loop cap, so a failing agent cannot spin forever.
    • Permission validation and tool injection before a process starts.
  6. Phase 3

    CLI & SDKs

    • The norien CLI: login, search, info, install, publish, update, uninstall, list, doctor.
    • TypeScript and Python SDKs with matching ergonomics.
    • --json on every command, with stdout kept pure for piping.
  7. Phase 2

    Runtime inspection

    • agent.json gains runtime, entrypoint, and commands.
    • The registry parses, detects, and resolves an agent without executing it.
    • Install responses carry the manifest, dependencies, runtime, and environment.
  8. Phase 1

    Registry core

    • Agents, tools, and installations with validation and slug uniqueness.
    • Immutable version records alongside a mutable head.
    • Ranked full-text search, filtering, and pagination.
    • OpenAPI document generated from the same schemas that validate requests.