Use cases

Linger is easiest to judge through real jobs. This page walks through six of them, taken from the scenarios that Linger’s own guides show. Each one names the situation, what Linger does, what it needs, and which pages to read next. The examples use demo names such as the Atlas demo Room and the client Acme. Some jobs need setup first, such as connected apps or a voice key. Each example says so where it applies.

​

Get a demo ready with a team of agents

A job with research, code, and outreach goes faster when several agents share it. In the Atlas demo Room, Maya asks Another Me to get a demo ready. Another Me creates a Research agent and a Dev agent. It publishes a team.md with the goal, who leads, and who hands work to whom. The Collaboration panel shows the team graph. Research reads the interview notes in Finder. Dev runs the tests in Terminal. Another Me drafts the partner email in Gmail. The Room shows what each agent is doing and their replies. The agents work on your own computer, with your apps and files. Read Desktop and browser.

​

Research rivals, then draft a deck

Long work in the chat blocks the conversation, so hand it to a Task. You ask Another Me to research Acme’s rivals, then to draft a deck. The agent in your chat, the Meta, starts one Task for each request. Each Task runs in the background as an AlterEgo, and the two run side by side. A follow-up about the new logo joins the deck Task. Each result comes back into the chat as a card when its AlterEgo reports. Read Task delegation.

​

Follow up on a client quote

Another Me decides when a client email deserves your attention. This job needs a connected inbox. An email from Acme asks for a revised quote. Another Me sets it to follow up later, and it comes back as a reminder on Wednesday. You say that client replies should come right away. That night, Another Me learns the rule. Acme’s next reply then reaches you within minutes. Read Proactive Another Me and Connected apps.

​

Hear about vendor invoices when they arrive

Your replies teach Another Me which things to tell you at once. Two replies of the same kind become one rule.

I’d rather have heard when it arrived.

You send this reply to an AWS invoice reminder on Wednesday, Oct 28. That night it becomes a clue for vendor invoices. On Wednesday, Nov 4, you answer a Figma invoice reminder in the same way. The two clues become one rule: vendor invoices, tell now. Read Proactive Another Me.

​

Recall what you agreed with a client

The personal memory keeps the facts of your work, so any agent can answer from them later. This job needs a connected inbox. On day one, you connect Gmail, and Another Me starts the Acme rollout page. On day four, you settle the pricing in a chat, and that night the page records it. On day nine, someone asks in a Room what pricing you agreed on. Another Me answers from a search over the page. That night, the page adds the March start. Read Personal memory and Memory layers.

​

Record a meeting and hand off the follow-up

Voice turns a meeting into a transcript and a follow-up draft without notes. This job needs a Soniox key on your server. You start a recording, and Linger shows a live transcript. During the meeting, the Ask tab answers questions from what people said. It can also send a request to Another Me. After the meeting, the recording, the transcript, and the follow-up draft land in your chat with Another Me. Read Meetings, Voice Mode, and Enable voice.

​

Keep learning