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

How to add a typed Resource to the Endo app for your own data with Endo

Define one table and schema, then get an API, agent tools and live updates from it.

Who it is forA developer extending Endo for a team or personal tool who needs agents and people to edit the same records under the same rules.

The problemWiring a new data type through the API, agent tools and UI by hand means keeping several definitions in sync.

The outcomeA new Resource with a Drizzle table and Effect Schema that exposes a typed API, agent tools and live updates.

What you need first

  • A Mac with Apple Silicon for the signed download, or Node.js 24, Bun 1.4.2 and Just for running from source
  • An existing codex, claude, Antigravity or grok login, or a provider set up in Settings → Models
  • A workspace folder where workflow files can live

Steps

  1. Clone the repo with git clone https://github.com/longsurf-ai/endo.git and enter it with cd endo.
  2. Install dependencies with just install --frozen-lockfile.
  3. Read the Adding a Resource section in docs/architecture/resource.md.
  4. Define your table as a Drizzle table and an Effect Schema for the new resource.
  5. Start the app with just desktop and confirm the new data appears through the typed API and agent tools.

Prompt for your agent

In the longsurf-ai/endo repo, follow docs/architecture/resource.md to add a Resource for <my data type>, defined once as a Drizzle table and an Effect Schema. Expected output: the new resource exposed through the typed API and agent tools. Verify that an agent tool can read and write a record and that the change shows in the app.

Caveat. The README calls Endo 0.1.x and warns of breaking changes, so a custom Resource may need changes after future updates.

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