Feature Ideas

Add native SFTP support to Luumen, allowing users to securely browse, upload, download, edit, and manage files directly on connected servers. Users will be able to open a file explorer alongside their terminal session for faster operational workflows without needing separate tools like FileZilla or Cyberduck. This creates a more complete infrastructure workspace by combining terminal access and secure file management in a single experience.

Allow users and partners to build custom applications, integrations, widgets, workflows, and operational extensions directly on top of the Luumen platform. The marketplace would provide a central place to discover, install, and share new applications, AI Skills, integrations, dashboards, and operational tooling built by both Luumen and the community. This lays the foundation for a broader Luumen ecosystem and extensible agentic operations platform.

Add a visual Ansible management experience within Luumen, allowing teams to create, organize, run, and monitor Ansible playbooks and inventories directly from the platform. This would make it easier for teams to operationalize infrastructure automation without constantly switching between terminals, repositories, and CI/CD systems, while opening the door for tighter integration between LuumenAI Skills, compliance workflows, and existing Ansible-based operations.

Add support for Microsoft Remote Desktop Protocol (RDP) sessions directly within Luumen, enabling users to securely connect to and interact with Windows-based systems alongside SSH and WinRM connections. This allows IT engineers to manage both Linux and Windows environments from a single AI-native operational workspace, while preserving Luumen context, auditability, and future AI-assisted workflows across sessions.

Self-service compliance scans and AI-defined compliance rules directly from terminal workflows. Why it's valuable: Useful for enterprise operations and governance.

Create persistent AI agents that monitor systems and autonomously execute tasks under defined rules. Why it's valuable Core long-term strategic vision for agentic IT operations. Additional notes Should likely remain heavily gated behind approvals/policies initially.

Allow users to connect their own MCP servers and external integrations. Why it's valuable Makes Luumen extensible and attractive to advanced engineering organizations. Additional notes Very aligned with platform/ecosystem vision in long-term roadmap.

Detect procedural workflows in uploaded SOPs and draft reusable LuumenAI Skills automatically. Why it's valuable Huge unlock for scaling operational automation and reducing setup friction. Additional notes Depends on SOP ingestion foundation.

Connect company SOPs, Notion docs, wikis, and KBs to LuumenAI for operational context. Why it's valuable Transforms LuumenAI from generic assistant into company-aware operational copilot. Additional notes Large strategic feature; likely enterprise-focused initially.

Analyze real Skill executions and recommend SOP/Skill improvements when users consistently deviate from workflows. Why it's valuable Creates a feedback loop that continuously improves operational knowledge. Additional notes Strong long-term moat and highly differentiated AI workflow capability.

Web UI for managing users, workspaces, credentials, billing, reports, audit logs, and vulnerabilities. Why it's valuable Required for team adoption and organizational scaling beyond individual engineers. Additional notes Important bridge from solo engineer -> team -> enterprise.

Allow organizations to provide operational context, standards, instructions, and guardrails to LuumenAI. Why it's valuable: Massively improves AI usefulness and reduces hallucinations by grounding responses in company-specific operations. Additional notes Start with simple org/workspace text fields before full ingestion pipeline. This would likely be a "custom instructions" free form field for admins to define guardrails for all luumenAI interactions, common in other AI solutions. This could be used to define workspace specific context or guardrails for activities that should not be done with the AI (e.g. never upgrade a package on an individual server without confirming a SNOW ticket was created first). automatic ingestion of company SOPs/knowledge base would be a strong follow up to this feature

Allow users to customize themes, colors, terminal appearance, and workspace visuals. Why it's valuable High-impact quality-of-life feature for terminal users who expect personalization.

Allow users to use local SSH keys without uploading them to Luumen. Why it's valuable: Give users the option to use local keys withoutImportant for adoption among security-conscious engineers. Removes friction and increases trust. Additional notes: Need clear UX around non-syncing behavior, team-sharing limitations, and recovery states.

Central audit log showing terminal sessions, commands executed, AI summaries, Skill executions, approvals, and impacted systems. Why it's valuable: Enterprise trust feature brought down to teams plan.critical differentiator for AI operations. Helps teams understand what happened and who performed actions. Additional notes: AI-generated session summaries are especially valuable for managers and compliance.