Weather Agent
Aleph
Start with an agent that already works.
Browse agents built for real jobs. Inspect every file and permission, install a live source into your workspace, authorize what it needs, and switch it on. Aleph handles the runtime around it.
From public agent to running copy
See exactly what you are copying.
Aleph turns a published agent into something you can inspect, configure, and run without rebuilding its platform.
Featured agents
Public agents ready to inspect and install
Long-Term Stock Finder Agent
Social Media Posts Scout Agent
Featured agents
Public agents ready to inspect and install
Weather Agent
Long-Term Stock Finder Agent
Social Media Posts Scout Agent
Find an agent worth installing.
Start with a public agent that already fits the job instead of rebuilding the same workflow from scratch. Search the catalog, compare its purpose, and see which agents other people already rely on.
Every listing is a versioned bundle, not a vague promise. You can open the exact agent, inspect who maintains it, and decide whether it is the right foundation before adding anything to your workspace.
Bundle code
v1.4.2 · published 3 days ago
AGENTS.md
agent.toml
README.md
sandbox.toml
connections.toml
schedules.toml
Know what you are adopting.
Open the agent and read the same versioned files Aleph will run: its instructions, skills, schedules, runtime settings, and declared connections. Nothing needs to stay hidden behind a demo or a black box.
You can see the vault and environment references it expects before you install it. That makes adoption a reviewable decision: understand the behavior first, then choose what your scope will allow it to access.
Install Long-Term Stock Finder Agent
Personal workspace
Vault & environment
FINANCIAL_DATA_API_KEY
RISK_PROFILE
Install summary
- Memory
- Shared live memory
- Visibility
- Private
- Version
- Live source version
adoptionMode = "installed"
visibility = "private"
Put the live agent to work.
Install the live source into your personal, team, or organization workspace. The bundle stays read-only, memory is shared, and your permissions, conversations, channels, and enablement remain yours.
The setup flow is derived from the bundle itself. Aleph asks for the vault secrets, environment variables, Connections, and channels this agent actually needs—so configuration is explicit instead of discovered through runtime failures.
Connections
Requested by this agent
GitHub
repos:read
Slack
messages:write
Notion
pages:read
Discord · stock-finder
Give it only your access.
Authorize the tools the bundle declares without putting credentials in its code. Connections stay scoped to your workspace, and the agent receives access only when you explicitly connect each service.
Then connect Discord or Telegram separately for conversations and delivery. Files and scheduled results can arrive in the channels your team already watches instead of forcing everyone into another isolated chat interface.
Long-Term Stock Finder
Version v1.4.2 pinned
Today's schedule
UTCMarket brief
Complete
Thesis check
Running
Close summary
Queued
Latest turn
IsolatedLoaded pinned bundle v1.4.2
Resolved scoped vault + variables
Restored thesis memory
Delivered scheduled result
cron = "0 8 * * 1-5"
deliverTo = "Discord"
Switch it on. Aleph keeps it running.
Pin the version you reviewed and enable the agent when its configuration is ready. Conversations and scheduled turns run in isolated environments with the bundle, memory, and scoped credentials assembled for that turn.
Aleph keeps the operational pieces connected between runs: schedules fire at the declared times, memory persists, and results return to the right conversation or channel. Disable the agent whenever you want it to stop.
Start from a featured agent.
Curated public agents you can inspect and install.
Loading featured agents…
For builders
Build the agent. Aleph runs the platform.
Publish the agent as a versioned bundle. Everyone who copies it gets the same inspectable starting point—not a sealed black box.
Build an agentStep 1: Author ordinary files
Keep instructions, skills, schedules, and runtime configuration together in Git.
Step 2: Push a version
Publish an immutable bundle that other people can inspect and copy with confidence.
Step 3: Let Aleph operate it
Platform models, isolated turns, memory, secrets, schedules, and channels are already wired in.
Adopt one. Build one. Keep it running.
Start by installing an agent that already works, or publish your own bundle and let Aleph operate it.