This is an early release preview. You may encounter bugs.
Agent-Native logo
Unclaimed

Tool coding

Agent-Native

Framework for agent-native apps where one Action definition powers the UI, agent, HTTP, MCP, A2A, and CLI

A 84/100 GitHub score ? This grade is derived from GitHub signals, not user votes. Open for the full breakdown.
Discussion

01 / Summary

About Agent-Native.

Agent-Native is an open-source TypeScript framework for building agents that pair autonomous work with a purpose-built UI. Each capability is defined once as an action: the agent receives it as a tool, and the UI calls it from code. The same action is also exposed over HTTP, MCP, A2A (agent-to-agent), and a CLI.

The premise is that knowledge work needs the same kind of environment coding agents already have. A UI shows what an agent can do and gives people familiar ways to inspect, edit, approve, and share its work. The agent does not click through the UI: it works through the same action layer, so both paths share validation, permissions, and implementation.

Agent work shows up in the UI and UI work is available to the agent, and the agent receives relevant UI state such as the current page, the selected record, or the active view. You bring your own LLM, SQL database, tools, and infrastructure.

The project ships a set of open-source agents to start from or study: Clips (meetings, screens, and voice notes), Design, Slides, Analytics, Calendar, Mail, Assets, Content, and Plans. A Claude Code skill, visual-edit, edits a running app on a canvas and has Claude apply the chosen edits to the source.

  • Shared actions: one action definition, with schema validation and permissions, serves the agent as a tool and the UI as a function call
  • Every surface: each action is also exposed over HTTP, MCP, A2A, and a CLI
  • Shared data and state: agent and UI read and write the same data, and the agent sees the current page, selection, and view
  • Agent chat: people delegate work, ask questions, and review results inside the app UI
  • Authentication and permissions: controls who can access and change shared work
  • Skills and memory: reusable expertise and persistent context for agents
  • Automations: agent work runs on schedules or events
  • Agent teams: delegates work to specialist agents in the same workspace or across connected agents
  • PostgreSQL backend: PostgreSQL in production and PGlite for local development, on any Nitro-compatible host
  • Example apps: Clips, Design, Slides, Analytics, Calendar, Mail, Assets, Content, and Plans as starting points

02 / Discussion CREDIBILITY-GATED

Discussion

Reading is open to everyone. Posting and voting need a verified identity or a GitHub grade of B or higher.

  • No discussions yet.

04 / Build

Build with Agent-Native.

Browse the catalog for frameworks, tools, and harnesses, each scored on real GitHub credibility.

Get Agent-Native →

Browse the catalog