Vellum

Vellum's current offering is a personal assistant that can retain preferences and perform tasks across connected tools. It suits users who want continuity between conversations and repeated work. Start with a read-only task before enabling actions. Memory can retain an incorrect assumption as well as a useful fact, so inspect important context and set clear permission boundaries for messages, bookings and other outside changes.

A practical workflow

1. Choose hosted access or review self-hosting requirements.
2. Configure permitted sources and action boundaries.
3. Ask for a small read-only result.
4. Verify remembered facts and outputs before enabling automation.

Illustrative input

This example describes a task, not a tested output. Adjust the source material and settings to your own situation.

Prepare a private daily brief from these authorized sources, separating confirmed commitments from tentative ideas and taking no external action.

Result check: Check source freshness, remembered preferences and that no unapproved change or communication occurred.

Access and alternatives

The assistant has an MIT-licensed self-hosted codebase and paid managed plans. Free software does not include free infrastructure or model inference; hosted tiers also differ in compute, storage and usage. Confirm provider credentials, deployment maintenance and the currently supported client build before installing or subscribing.

Choose another workflow when its emphasis fits better: Letta for another stateful-agent approach; Lindy for a different connected-assistant workflow.