Folders are agents: build expertise that lasts
A task ends. What it builds should endure.
Multi-agent work is more than dividing a task. It should also make the next task start from what the last one achieved.
Light by design. Folders are agents.
Every member has a place to build
Every Rind team member is bound to a working directory. Files, instructions, scripts, and outputs live there; Rind keeps session and task records so the work can be traced.
A member is a continuing working identity. A session is a conversation; a task is assigned work with an owner, a status, and a delivery. One member can span many sessions and tasks.
Temporary delegation asks who can handle this step. Rind's team also asks what this step can leave behind. Folders are agents means a lasting foundation for work—not a model automatically running in every directory.
Expertise is more than the model
An agent's capability also depends on the knowledge, methods, and tools it can use. Scripts, workflows, and research refined in one task can remain in the workspace for the next.
Imagine three specialist workspaces:
- Quant research: a genetic-algorithm framework for factor discovery, experiment configurations, and evaluation methods.
- Information gathering: daily cross-platform collection scripts, source lists, and deduplication rules.
- Financial analysis: company filings, consistent metric definitions, and sourced historical analyses.
These are directions to explore, not built-in experts or validated case studies. Building reusable assets requires curation, testing, and maintenance—not automatic model training.
Reuse more than a role name. Reuse a way of working you've refined.
Your team, with visible responsibility
A Lead aligns the goal, a Builder implements, and a Reviewer checks. Teams organize responsibilities and reporting lines without prescribing the directory tree on disk.
Team Agents Management makes the work inspectable: Organization shows members, Tasks shows assignments, Inbox brings attention items together, and Background shows ongoing work and services. Open a member's session when you need the detail.
Keep key decisions with people. Deliver files, checks, and unverified boundaries—not just “done.” Use one agent when one is enough. Coordination has a cost; a workspace isn't a sandbox. Separate worktrees separate changes; shared-directory writes need serialization.
Make the process visible. Make the result inspectable.
Light: keep the work, release the weight
A workspace should outlive an execution. Rind separates persisted context from temporary execution: restore context when work resumes, release idle execution objects. Keeping history shouldn't mean keeping every past session actively running.
Workers still have runtime state. Light doesn't promise zero memory use or entirely local inference. It means keeping what matters without accumulating needless weight.
Taste is productivity
Readable states, fluid keyboard interaction, restrained tool output, and input that survives background updates all protect your attention. Taste doesn't replace reliability; good design makes reliability easier to understand and inspect.
We're building Rind so one agent feels good to use, and a team still feels natural to work with. We'd like to build it with people who share that standard.
Folders are agents. The team is yours.