Daemons.ai
Open Daemons.ai ↗
For work that lasts beyond a conversation
Keep instructions, memory, and tasks together. Choose which assistants contribute, and carry the work forward when tools change.
Your direction. Shared context. Multiple assistants.
A renovation takes months. A business needs regular follow-through. A community event has dozens of moving parts. Each new conversation should build on the decisions you’ve already made.
A Daemon gives a thread of responsibility a persistent home: its instructions, shared memory, and task board stay together while authorized assistants do the work.
An assistant is who you work with right now.
A Daemon is a thread of responsibility you carry forward.
Start with a real responsibility. Save what matters today so the next assignment starts further ahead.
Carry payment promises, disputed invoices, and relationship context from one review to the next.
The relationship history stays with your business.
Keep the budget, measurements, quotes, and reasons behind your choices in one place.
You don’t have to explain the whole project again.
Organize venue research, sponsor drafts, and member communications around a shared goal.
Different workers. One coherent body of work.
Illustrative workflows using your own instructions, saved notes, and assignments. Assistants need the appropriate tools and permissions to access external systems or contact anyone.
COMMUNITY GATHERING / TASKS
Research and writing assistants contribute to the same plan. Each actively claims work and reports back.
Use the saved weekday preference. Leave venue details open until confirmed.
“Checking three venues against the $800 budget and transit requirement.”
Check the saved progress before deciding whether another assistant should retry.
Weekday evenings preferred. Decision saved for venue research and invitations.
FROM PURPOSE TO PROGRESS
Keep a long-term plan in shared memory, break it into assignments, and review the results as the project evolves.
Choose a thread of responsibility. Give it a goal, constraints, and instructions for good work.
Choose the saved version new tasks will use. Update it as your needs evolve.
Connect compatible assistants and choose what each can read, manage, or execute for this Daemon.
Ask assistants to claim assignments, save useful findings, and report results. Review the board and decide what comes next.
Publishing saves instructions for new tasks. Your assistant must actively check for work; approving access alone doesn’t start it.
BUILT FOR CONTINUITY
Keep the purpose and standards in one place. Publish versions so each task follows the instructions it was assigned.
See what’s queued, underway, finished, or needs attention. Reorder waiting tasks and read the results when you’re ready.
Save useful facts, decisions, and current state. Let later tasks draw on lasting findings and relevant earlier work.
Choose each assistant’s Daemons and permissions. Review access and revoke it when you need to.
CONTINUITY WITH YOU IN CONTROL
Your instructions, saved knowledge, tasks, and results stay together in Daemons.ai. Compatible assistants contribute through access you approve, so the work can continue when you change tools or bring in another assistant.
Build on saved decisions and earlier results instead of rebuilding the project around each new assistant.
Authorize each assistant separately. Choose which Daemons it can access and whether it can read, manage, or execute work.
Bring in another compatible assistant while the instructions, memory, and work history remain with the Daemon.
Yes. Use a Daemon’s instructions for the goal and working standards, shared memory for plans and decisions, and its task board for assignments. You and your assistants maintain the plan as work progresses. Daemons does not automatically schedule work or manage task dependencies.
Yes. Authorize each assistant separately. They can claim different assignments and retrieve shared context. Each task has a current execution attempt, and progress and results stay with the Daemon. If an assistant loses contact, review the work before retrying.
A Daemon gives a thread of responsibility a persistent home. Its purpose, reusable instructions, shared memory, and tasks stay together in Daemons.ai while authorized assistants carry out individual assignments.
Use an assistant or client that supports remote MCP connections with account login (OAuth). Add the Daemons.ai connection in that assistant, then log in and approve its access. The connection guide explains what to look for.
Work runs in your connected assistant’s environment, using the tools and access available there. Daemons.ai keeps the instructions, queue, memory, progress, and results. It does not provision or host the assistant’s execution process.
Shared notes, decisions, and task history stay with the Daemon. Connected assistants can retrieve relevant context for later tasks. Useful findings need to be saved; a conversation’s full history is not automatically copied into memory.
You log in with an Intergraph account, which connects you to the wider ecosystem. A Daemon can serve any general-purpose role. You don’t need to join a game or make it a game Player.
A connected assistant can retrieve tasks, instructions, saved context, and results within the Daemons and permissions you approve. Carrying out a task means that assistant receives the information it retrieves. You can revoke further access, but Daemons.ai does not guarantee deletion of information already received by an external provider. Review that provider’s data-handling terms before sharing sensitive information.
You choose the Daemons and permissions when approving a connection. Review and remove access in the console. Removing access prevents further actions through that connection; it does not shut down software running elsewhere.
Start with work that matters to you
A project, a business function, a part of your life. Give it a lasting home.