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

Runner: make it usable without the private flai binary

Open
#3 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
55/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Active
Tech stack
python
Domain
devtools

Research direction

Start by reading the README sections that introduce the runner and the etchwork runner build --agent-bin entry point. For launch, either support an available agent such as Claude Code or Codex CLI, or mark the runner internal or experimental and omit it from the docs. Done means contributors can use the runner with an available agent, or the README and docs clearly identify its current limits.

Written by the indexing model from the issue text.

Description

launch runner

etchwork runner build --agent-bin accepts only a Linux build of flai, FlologixAI's private agent. Outside contributors can't build or run the isolated runner.

For launch, at least one of:

  • support an agent people can get (Claude Code or Codex CLI) as the runner's agent;
  • or mark the runner as internal/experimental in the README and skip it in docs.

Longer term --agent-bin (or --agent) should take any supported client.

Dominant language
Python
Stars
1
Forks
1
Avg merge
1h 36m
Merged PRs (30d)
2

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 FlologixAI/etchwork

All issues in FlologixAI/etchwork

Similar issues

More Python issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.