MoodLens FAQ

An AI workforce platform is a work system where humans and AI collaborate inside the same workspace. In MoodLens, that includes tasks, boards, sprints, calendar, docs, chat, meetings, and an AI layer built around Moody, AI Employees, Team Discussions, automations, and System Packs. The goal is not only to organize work, but to help teams move it forward.

AI Employees are role-based specialists that can help with research, planning, support, writing, operations, and repeatable workflows. They work alongside human teams inside the workspace and can participate in discussions, connected-tool flows, and automations when needed. The value is faster follow-through and less manual coordination, not pretending every human role should disappear.

MoodLens is designed to reduce coordination overhead, not claim that every meeting should disappear. Moody can help summarize meetings, capture follow-ups, turn decisions into tasks, and keep planning connected to execution. AI Employees and Team Discussions can add specialist input when the team needs help thinking through next steps.

AI teams in MoodLens are built from AI Employees with defined roles, instructions, knowledge, tools, and automations. You can bring one specialist into a thread or open a Team Discussion where multiple AI Employees respond to the same prompt together. That keeps collaboration, delegation, and status more visible than splitting work across isolated chats.

System Packs are reusable setup blueprints for how an AI team is configured. A pack can include the employee roster, prompts, knowledge setup, compatible automations, and shared playbook for a specific use case. Secrets, live credentials, chat history, and run logs stay outside the pack.

Partly, but it is broader than a standard project management app. MoodLens includes tasks, boards, backlogs, sprints, calendar, docs, chat, meetings, and multi-workspace collaboration, then layers AI on top through Moody, AI Employees, Team Discussions, and automations. It is meant to support both organization and execution.

Some work can run automatically in MoodLens, especially through scheduled, event-driven, and webhook-triggered automations. Teams can also use dry runs, manual runs, and logs to review how a workflow behaves before depending on it more heavily. The more accurate description is controllable automation, not blind autonomy.

GitHub is the main live engineering connection in MoodLens. The platform also supports migration-style imports from Trello, Jira, Asana, Notion, and ClickUp, plus webhooks, workspace secrets, and external action lanes for broader workflows. Not every tool should be described as a permanent bidirectional sync, because the connection model depends on the system and setup.

MoodLens is designed around workspace-level controls, scoped connections, and separated secrets. Workspace secrets let teams store credentials without pasting raw values into prompts, and AI Employees can be configured around specific roles, tools, and context. As with any business system, safe use still depends on good admin setup and access decisions.

In MoodLens, automations can be owned by AI Employees and triggered on a schedule, by events, or by incoming webhooks. That makes the platform useful for recurring reporting, follow-up flows, content operations, support routines, and other repeatable work. Logs, dry runs, and manual run controls help keep those automations operational instead of opaque.

Notion and ClickUp are often used to organize information and manage work. MoodLens also covers the workspace structure, but adds an AI operating layer with Moody, AI Employees, Team Discussions, automations, and System Packs. The difference is not only storing work neatly, but helping work move from planning into execution inside the same system.

Yes. You can configure AI Employees around different roles, instructions, knowledge, tools, and automations, then reuse that setup across workspaces or use cases. If the setup should be repeatable, you can package it as a System Pack blueprint.