@alwen and jobs
What happens when you ask @alwen in Slack, Telegram or Discord to get something done.
Mention @alwen in Slack, or message it in Telegram or Discord, with a request — “have Grok Bot research this and build it with Claude Code if it makes sense” — and Alwen opens a job. A job can take minutes or days. Every step is written to jobs/<id>.md in your vault.
The steps
| Step | What happens |
|---|---|
| Requested | Alwen reads the request and searches the vault for everything related. |
| Clarifying | If something can't be undone or is unclear, Alwen asks one question in the thread. |
| Researching | Research goes to Grok Bot, or Alwen uses research already in the vault. |
| Judging | With the findings in, Alwen checks again whether the request still makes sense. |
| Building | The work goes to Claude Code, Cursor, Codex or GitHub Copilot. |
| Reporting | Alwen posts the result in the same thread and logs the decision in the journal. |
| Done or declined | A declined job always comes with the reason, and the rule Alwen relied on. |
How work reaches your agents
- Builders (Cursor, Claude Code, GitHub Copilot, Devin, Google Jules, v0 by Vercel): Alwen writes the task into your memory and starts the agent through its own API, with the key you pasted on the Agents page and a brief from your memory: the request, the research and your rules. The agent works in your project with its own GitHub access and answers with a pull request; Alwen posts it in your chat, with the preview when Vercel is connected. When you say “ship”, Alwen asks the agent to merge it. Alwen never opens your project itself.
- Grok Bot researches: its routine asks Alwen for the next task with
next_taskevery few minutes and hands in the findings withtask_done. They're saved to your memory and go into the builder's brief. - Your own tools (Business): a tool or agent of your company's takes research or building the same way, with
next_taskandtask_done. Your own tools. - In a team's channel or group, the work goes to the team's agents and its task, research and decisions go to the team's shared vault. Teams.
- Connect the builders on the Agents page of the dashboard. Name the project when you ask (“build a pricing page in github.com/you/project”) and Alwen remembers it. Vercel is optional: it puts the preview in your chat.
The defaults
- One good question beats a guess on anything that can't be undone.
- Anything touching money, deletion or contacting people is declined unless you say otherwise.
- Alwen never opens a browser, runs a terminal or writes code. Your agents do the work.