Skip to main content
This guide follows the current Felan onboarding and dashboard.

​
Prerequisites

  • A Felan account
  • A team you created or joined
  • Access to a GitHub or GitLab account when connecting repositories during onboarding
When you create your first trial team, Felan adds $5 of non-expiring AI credit for managed-model usage. Each team owner receives this signup grant once; additional teams do not receive another signup grant. Team-provided model credentials remain independent of this balance.
1

Name your team

Review the automatically generated team name and change it if needed. Felan keeps the team slug unchanged when you rename it.
2

Connect a repository provider

Connect GitHub or GitLab and authorize Felan for the repositories your team wants it to use. For GitLab, complete project selection after authorization. Felan checks that either supported connection is active before continuing.
3

Start your first session

If you arrived from a marketing prompt, Felan starts that first session after you confirm the team details and repository access, without asking you to re-enter it. This starts agent work and uses the team’s available AI credit or configured model credentials. Once a session has been created, Felan opens it even if agent startup fails; the prompt handoff is cleared, and the session shows the failure. If no session was created, the prompt stays available in onboarding for a retry. Otherwise, choose Map this codebase, Ship a quick win, or Fix a bug; each template is editable, and you submit it when ready.
4

Review progress and follow up

Felan opens the new session and streams its transcript. The session header shows its status, and delegated agents appear with the session activity. When a conversational session is running or completed, use the composer below the transcript to clarify the request or ask for the next step.
Marketing prompts are handed off in the current browser tab and survive the sign-in redirect without being sent in URL query parameters. A signed-in user who opens a marketing prompt sees it in the new-session composer and must press Start session; it does not start automatically.
Felan uses the team owner’s email as the default update destination. To connect Slack, Microsoft Teams, or additional email recipients, open Integrations → Channels after onboarding and choose the primary channel there.

​
Add context when you need it

The first session can start with only a prompt. Add team-level configuration as your workflows require it:
  • Knowledge for durable context, reference files, and learned memory
  • Agent for models, extensions, skills, and subagents used in new sessions
  • Environments for variables and credentials used by agent runs
  • Integrations for additional repositories and external systems
  • Automations for scheduled or event-driven requests
Start with a specific outcome, relevant constraints, and the evidence Felan should inspect. Continue in the same session when the next request depends on its existing context.

​
Next steps

How Felan works

Learn how Felan uses context, tools, and specialized agents.

Explore the dashboard

See where sessions and team configuration live.