Skip to main content
Felan is a stateful AI SDLC agent. A team can invoke it from the web dashboard, a connected conversation, a schedule, or an external-system event. Felan combines the request with the context available to that team, then completes focused work directly or delegates specialized work.

​
The interaction loop

​
Sessions keep the work together

A session contains the prompt, live transcript, status, and delegated agent activity for one body of work. Conversational sessions support follow-up messages, so the team can refine the outcome without starting over. Requests from connected conversation threads resume the corresponding Felan conversation. Automation runs create sessions with source information so the team can trace why the work started.

​
Context is team-scoped

Felan uses only context available to the current team and request. Depending on configuration, that can include:
  • The current message and earlier messages in its conversation
  • Durable team context and learned memory from Knowledge
  • Uploaded team reference files
  • Repositories authorized through source-control integrations
  • Event payloads and metadata from connected systems
  • Environment names and variables configured for the team
Felan discovers repository structure and conventions before acting instead of assuming a framework or workflow.

​
One main agent, specialized help

The main Felan agent communicates with the team and coordinates the result. It can inspect repositories, make focused changes, run commands, and manage platform resources exposed by its tools. For broader, specialized, or parallel work, Felan can delegate to agents for areas such as architecture, implementation, review, QA, investigation, and memory consolidation. Delegated agents share the root session workspace and report their results back through the parent session.

​
Automations reuse plain-language requests

An automation combines:
  1. A name
  2. One or more schedule or event triggers
  3. Plain-language instructions describing what Felan should do
When any enabled trigger fires, Felan starts a session with those instructions and the event context available to the team. Automations are useful when the desired response is repeatable, such as reviewing a recurring signal, checking a deployment event, or preparing a scheduled report.

​
Access follows configuration

Felan’s available evidence and actions depend on connected repositories, configured integrations, selected agent skills, team environments, and the current user’s request. If required context or access is unavailable, Felan should identify the blocker rather than inventing a result.

Sessions

Start work, inspect progress, and continue a conversation.

End-to-end SDLC

See how teams connect planning, implementation, verification, and delivery.