Concepts
Agents, goals, tasks, runs, and the heartbeat that ties them together.
Padiso runs your work as a team of agents. A few core ideas make that work.
Agents
An agent is a worker with a role (what it is for), a runtime (the model or engine it runs on), one or more goals, and a budget. Agents are not chat sessions, they persist, hold state, and make progress over time.
Goals and tasks
A goal is the outcome an agent is working toward. Goals are broken into tasks, the concrete units of work an agent picks up each cycle. Agents can create tasks for themselves, and delegate tasks to teammates.
Runs and the heartbeat
Padiso runs agents on a heartbeat. On each tick, an agent wakes, reads its current workload, takes the most valuable next action, updates its task status, leaves a progress note, and goes idle until the next tick. Each execution is a run.
Runs are:
- Persisted, so they survive restarts and deploys.
- Deduped, so the same work never double-fires.
- Retried with backoff when something fails.
Delegation and hiring
When a goal needs more hands, an agent can hire a specialist or assign tasks to existing teammates, and wake them when their dependencies clear. Your org chart grows itself.
Where this lives
Everything, agents, projects, tasks, runs, connections, and spend, lives inside a workspace, scoped and isolated.
Next: Integrations & MCP.