Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

README quick start: the first agent reply through your own MCP client

Open
  • Is something wrong?
#320 0 comments 0 reactions 1 assignee View on GitHub

Maintainers usually reply within 1 day

@Zamojski5 is already working on this.

Since Oct 6, 2026.

Assessment

This issue has not been assessed yet.

Description

Found while measuring the time to first run for #305 (L-1) on 2026-10-06.

The launch plan's fourth time is the time to the first agent reply through a person's own MCP client, following the README. It cannot be measured yet, because the README quick start has no step for it.

Observed at efb1fb94, on ./flux demo data

  • The README mentions MCP only under Project status. The #305 PR adds a one-line pointer to Settings → Agent connections (MCP).
  • In the running app, the path is:
    1. Settings → Agent connections (MCP).
    2. Create a personal agent. The demo seeds none.
    3. A project manager grants it access to the project.
    4. Select the agent's projects.
    5. Add the server to the client and sign in. For Claude Code: claude mcp add --transport http flux http://127.0.0.1:8081/mcp, then claude mcp login flux. The login opens the OAuth consent in a browser. Codex has the same two commands.
    6. Ask the client something about the project.
  • The page says "Use your self-hosted Flux HTTPS address", but it shows the loopback http:// address of the quick start.
  • The server side is ready. /mcp returns 401 with resource_metadata, and both .well-known OAuth documents return 200.

Acceptance criteria

  • The README quick start, or one page it links, lists the steps from ./flux demo to the first agent reply in Claude Code and in Codex, on the loopback URL. Decide in the task whether ./flux demo should also seed Ada's personal agent with a grant to the demo project, which would remove steps 2–3.
    • Done in PR #328 (342c3752): the README section "Connect your own agent" lists the six steps for Claude Code and Codex on the loopback URL. Still open: the seeding decision.
  • A person with Claude Code or Codex and their own model account completes the steps on a clean clone. The time from git clone to the first agent reply is recorded in docs/development/time-to-first-run.md.
  • The Connect page copy fits the loopback quick start. It does not require HTTPS there.
    • Done in PR #328 (342c3752). The PR records that its UI check (test_ai_connections test_07) did not run in Docker; run it before closing.
  • Coordinate with #277 (one Connect AI entry) and #160 (Start/Resume onboarding), which may change this page.

Owner: Zamojski5. Evaluator: PelikanFix16.

Updated 2026-10-07: progress from PR #328 recorded against the criteria.

Dominant language
TypeScript
Stars
3
Forks
0
Avg merge
13h 27m
Merged PRs (30d)
224

Getting set up

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from ColdPhase/flux

All issues in ColdPhase/flux

Similar issues

More TypeScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.