Skip to content
Homany

Agents · Agent builder

Composing your own scoped agents

As the platform matures, the goal is to let teams compose their own agents - defined roles, a scoped set of tools, and governance baked in. Here's how we're thinking about it.

This page describes product direction, not a shipped feature. Custom agent composition is on the roadmap (Phase 2→3); today, agents operate through Homany's existing scoped surface.

Book a working session

Concept

What an agent builder makes possible

The idea: instead of one general agent, define purpose-built agents for specific operations, each with exactly the scope it needs.

  • 01

    A defined role

    An agent scoped to one job - intake triage, reporting prep - rather than a do-everything assistant.

  • 02

    A scoped tool set

    The specific actions and objects that role needs, and nothing more.

  • 03

    Governance by construction

    Approvals and limits defined when the agent is composed, not bolted on later.

Direction

Scoped roles, tools & governance

  • Roles

    Composable agent roles aligned to real operations, owned by the teams that run them.

  • Tools

    A curated set of permitted actions per agent, drawn from the same surface as the API.

  • Governance

    Scope, approval gates, and audit defined as part of the agent, not around it.

Where this stands today

The control primitives - scope, approvals, audit - exist now and power today's agents. Composing custom agents on top of them is the direction; we'd rather show the plan than overstate the present.

Want to shape where agents go?

Book a session to tell us about the agents your operations need - it informs the roadmap.

Book a working sessionSee pricing details