DEDUPED Hot AI repos, turned into use cases Get 5 a day

How to build and check Nautilo from source before a code change with Nautilo

Clone the monorepo, start a dev stack, and run the standard checks before you submit a change.

Who it is forA developer or coding agent who wants to change Nautilo or contribute a fix and needs a working local build and the repo's standard checks.

The problemContributing to a monorepo with several apps and packages is hard to start without a clear setup and a clear set of checks to pass.

The outcomeA running dev stack for your own instance and a pass or fail report from the four standard checks.

What you need first

  • Docker Desktop installed
  • A model API key from a provider you choose
  • A Mac for the local guide, or a Linux server or VPS for team deployment
  • Bun 1.3.11 and Node 24.x for source development
  • Rust, only if you prepare Desktop and need its native helper
  • Note that Nautilo is in alpha

Steps

  1. Run git clone https://github.com/agentsea/nautilo.git
  2. Run cd nautilo
  3. Run bun install --frozen-lockfile
  4. Run bun run dev-stack --instance my-nautilo-dev
  5. Follow the source development guide at https://nautilo.ai/docs/build/development/local-development to claim the instance and configure a model.
  6. Run bun run lint, bun run typecheck, bun run test:unit, and bun run lint:unused before submitting a code change.

Prompt for your agent

In a checkout of the agentsea/nautilo repo at <path>, confirm Bun 1.3.11 and Node 24.x are installed, then run bun run lint, bun run typecheck, bun run test:unit, and bun run lint:unused. Report pass or fail for each and the first error. Read AGENTS.md and README.ai before editing any file.

Caveat. The README asks for Docker for local PostgreSQL and Logto infrastructure, and some integration checks need extra setup described in the testing guide.

Share: X LinkedIn Hacker News Email Copy link

Disclaimer

Deduped lists open-source repositories that belong to other people. We do not own, maintain, audit, or vouch for any of them, and a repo appearing here is not an endorsement or a safety check. The use cases, steps, and prompts are written by AI and may be incomplete, outdated, or just wrong. Where a use case is marked "Seen in the wild", we link to public posts where someone described something similar, but we have not verified those posts and the use case itself is still our AI's own write-up. Use all of this at your own risk. Only run code, commands, or agents on systems and accounts you are authorized to use, and read the code and every command before you run it, especially anything that touches credentials, files, or the network. Nothing here is professional, security, legal, or financial advice. All trademarks and project names belong to their respective owners, and their use here does not imply affiliation. Content is provided as is, without warranties of any kind. Found a mistake, a safety problem, or something you want removed? Email [email protected] and we will look at it promptly. Full disclaimer page