Movatterモバイル変換


[0]ホーム

URL:


Skip to content

Navigation Menu

Sign in
Appearance settings

Search code, repositories, users, issues, pull requests...

Provide feedback

We read every piece of feedback, and take your input very seriously.

Saved searches

Use saved searches to filter your results more quickly

Sign up
Appearance settings

Aider module support agentAPI#356

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to ourterms of service andprivacy statement. We’ll occasionally send you account related emails.

Already on GitHub?Sign in to your account

Open
Harsh9485 wants to merge36 commits intocoder:main
base:main
Choose a base branch
Loading
fromHarsh9485:aider-tasks-agentapi-support

Conversation

Harsh9485
Copy link
Contributor

@Harsh9485Harsh9485 commentedAug 21, 2025
edited
Loading

Closes#239

/claim#239

Description

video :-https://www.loom.com/share/d1d1d54d48bc45c4a48271ca9a387a88?sid=933e250d-78f8-4a7f-9745-0e908c0ee4d9

Type of Change

  • New module
  • Bug fix
  • Feature/enhancement
  • Documentation
  • Other

Module Information

Path:registry/coder/modules/aider
New version:v1.0.0
Breaking change: [ ] Yes [x] No

Testing & Validation

  • Tests pass (bun test)
  • Code formatted (bun run fmt)
  • Changes tested locally

Related Issues

@Harsh9485
Copy link
ContributorAuthor

@matifali@DevelopmentCats, most of the module works fine, but now I’m implementing MCP configuration and task prompts with active chatting.

Screenshot 2025-08-21 202353

The --message flag disables chat mode, runs only the prompt, and then exits the program. I’m trying to find a way to keep chat mode running inside the module.

@matifali
Copy link
Member

@Harsh9485, I think we should run in chat mode using AgentAPI by default, but provide the option to use message mode and disable AgentAPI (i.e., Coder Tasks) integration if a user wants to run in that mode.

@Harsh9485
Copy link
ContributorAuthor

@Harsh9485, I think we should run in chat mode using AgentAPI by default, but provide the option to use message mode and disable AgentAPI (i.e., Coder Tasks) integration if a user wants to run in that mode.

So should I give the user three options:
1 Empty prompt (works fine),
2 Task prompt,
3 Run the Aider module with a task prompt (runs only once and disables AgentAPI)

matifali reacted with thumbs up emoji

@matifali
Copy link
Member

So should I give the user three options:
1 Empty prompt (works fine),
2 Task prompt,
3 Run the Aider module with a task prompt (runs only once and disables AgentAPI)

Yes@Harsh9485

@Harsh9485
Copy link
ContributorAuthor

@matifali, unfortunately we can’t run interactive mode with the --message flag. What should I do now?

@Harsh9485
Copy link
ContributorAuthor

@matifali@DevelopmentCats. PR ready to review.

@Harsh9485
Copy link
ContributorAuthor

@matifali@DevelopmentCats, I have added the MCP server configuration.

DevelopmentCats reacted with eyes emoji

@Harsh9485
Copy link
ContributorAuthor

@matifali@DevelopmentCats, let me know if you need any changes in the code.

@Harsh9485
Copy link
ContributorAuthor

@Harsh9485 while refactoring Claude code module, we ran into an issue where it was not possible to conditionally disable the Coder Tasks e.g. "AI Prompt" needs to exist. Lets revist this next week. Thanks for all your work

@matifali, what if we implement my earlier idea? We could create a new 'Aider CLI' module for the Coder Tasks instead of modifying the existing one. I believe this would solve the problem and meet your requirement.

@Harsh9485
Copy link
ContributorAuthor

Hey@matifali, could you let me know what the current plan is? I'd like to start working on it and just want to make sure the plan is still the same.

Can we also add input to disable agentAPI and coder tasks altogether? Like a mode that only installs the agent. I am looking for something like.
1.Refactor to support Coder Tasks with AgentAPI with "AI Prompt" included
2.An install-only mode without running or starting the task also skips AgentAPI installation.

@matifali
Copy link
Member

Hi@Harsh9485 leta revert these changes as currently there is no clean way to dual-purpose the module. I will also ask@35C4n0r to guide you as they are refactoring the Claude Code module.

@Harsh9485
Copy link
ContributorAuthor

Hey@matifali and@35C4n0r, I reverted the changes, but I left your suggestion changes in place. Let me know when you've had a chance to look at it.

@Harsh9485
Copy link
ContributorAuthor

I'm refactoring the aider module now.

@Harsh9485
Copy link
ContributorAuthor

I'll refactor the MCP part shortly.

coder_mcp=<<-EOT
coder:
args:
- exp
- mcp
- server
cmd: coder
description: Report ALL tasks and statuses (in progress, done, failed) you are working on.
enabled: true
envs:
- CODER_MCP_APP_STATUS_SLUG: aider
- CODER_MCP_AI_AGENTAPI_URL: "http://localhost:3284"
name: Coder
timeout: 3000
type: stdio
developer:
display_name: Developer
enabled: true
name: developer
timeout: 300
type: builtin
EOT

@Harsh9485
Copy link
ContributorAuthor

hey@matifali@DevelopmentCats,
I wanted to let you know that the Aider agent doesn't support using a Task prompt with interacting mode. When we pass one, the module just runs the prompt and exits. We also can't get the agent's response because it disappears upon exit.

if [-n"${ARG_AI_PROMPT:-}" ];then
printf"Aider task prompt provided :$ARG_AI_PROMPT"
PROMPT="Every step of the way, report tasks to Coder with proper descriptions and statuses. Your task at hand:$ARG_AI_PROMPT"
agentapi server --term-width=67 --term-height=1190 -- aider --model$ARG_MODEL --yes-always --message"$ARG_AI_PROMPT"

@Harsh9485
Copy link
ContributorAuthor

Hey@matifali, I commented out the code yousuggested for choosing between the two agents. I think we're dropping that plan now, so I'll remove it soon.

# if [[ "${AIDER_PROMPT}" == "true" && -n "${ARG_AI_PROMPT:-}" ]]; then
# printf "Aider start only with this prompt : $ARG_AI_PROMPT"
# mkdir -p $HOME/.aider-module/
# echo aider --model $ARG_MODEL --yes-always --message "$ARG_AI_PROMPT" > $HOME/.aider-module/aider_output.txt

@Harsh9485
Copy link
ContributorAuthor

The Aider agent doesn't have native support for MCP configuration. Is it okay if I usethird-party software? and please let me know what should I do?

@matifali
Copy link
Member

The Aider agent doesn't have native support for MCP configuration. Is it okay if I usethird-party software? and please let me know what should I do?

What do you think@DevelopmentCats and@35C4n0r

@matifalimatifali assignedmatifali and unassignedmatifaliSep 19, 2025
@DevelopmentCats
Copy link
Contributor

The Aider agent doesn't have native support for MCP configuration. Is it okay if I usethird-party software? and please let me know what should I do?

What do you think@DevelopmentCats and@35C4n0r

I think that since we don't have a realistic eta on when aider might add MCP support, our best option would be to use:https://github.com/lutzleonhardt/mcpm-aider at least until it is updated on aider's end.

@Harsh9485
Copy link
ContributorAuthor

@DevelopmentCats, sorry, I didn’t see your message earlier. I’ve added MCPM-aider, and now I’ve found a way to add the Coder MCP server to it.

@Harsh9485
Copy link
ContributorAuthor

Tried adding Coder MCP server viamcpm-aider add, but env vars aren’t supported.

Screenshot 2025-10-02 131523

@Harsh9485
Copy link
ContributorAuthor

Hey@matifali,@DevelopmentCats, I think we should drop the idea of configuring the Coder MCP server for now. Once Aider supports MCP, I’ll implement it.
Also, we shouldn’t use the TASK prompt for interactive mode. When a user gives a TASK prompt, it’s only sent once, and when the output is completely fetched, both Aider and AgentAPI exit. Because of this, the user can’t see the output properly. I think that’s kind of a bug.

@DevelopmentCats
Copy link
Contributor

Hey@matifali,@DevelopmentCats, I think we should drop the idea of configuring the Coder MCP server for now. Once Aider supports MCP, I’ll implement it. Also, we shouldn’t use the TASK prompt for interactive mode. When a user gives a TASK prompt, it’s only sent once, and when the output is completely fetched, both Aider and AgentAPI exit. Because of this, the user can’t see the output properly. I think that’s kind of a bug.

A lot of these CLI modules have a similar issue that we have had to work around. AgentAPI now supports an -I flag so for this you would want to pass the prompt into the session with that so that way we aren't locked into a print style output.

As for the MCP Server issue I'm honestly not too sure when we would be seeing this since Development on aider seems to have slowed down exponentially in the last few months.

@Harsh9485
Copy link
ContributorAuthor

If any CLI module already uses the -I flag,@DevelopmentCats could you share its name? It would really help.

@DevelopmentCats
Copy link
Contributor

If any CLI module already uses the -I flag,@DevelopmentCats could you share its name? It would really help.

The copilot module that was just released uses this flag.

Sign up for freeto join this conversation on GitHub. Already have an account?Sign in to comment
Reviewers

@matifalimatifalimatifali requested changes

@DevelopmentCatsDevelopmentCatsAwaiting requested review from DevelopmentCats

@35C4n0r35C4n0rAwaiting requested review from 35C4n0r

Requested changes must be addressed to merge this pull request.

Assignees

@Harsh9485Harsh9485

Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.

Aider Module: Tasks+AgentAPI Support
3 participants
@Harsh9485@matifali@DevelopmentCats

[8]ページ先頭

©2009-2025 Movatter.jp