Bash – “history” stops working when run inside bash script

You could do something like:

SHELL=/bin/bash PROMPT_COMMAND='unset PROMPT_COMMAND; history -s "$CMD";
    eval "$CMD"' CMD='vi /etc/issue' gnome-terminal

(here using vi /etc/issue as your command).

That has the advantage of running $CMD as a job of that shell, so you can suspend resume, interrupt it as other jobs and it can affect the environment of the shell (for instance you can do CMD='PATH=$foo:$PATH').

It assumes your ~/.bashrc doesn't set $PROMPT_COMMAND itself.

Edit:

For multiple tabs:

PROMPT_COMMAND='unset PROMPT_COMMAND; history -s "$CMD"; eval "$CMD"
  ' gnome-terminal --tab --title /etc/issue -e 'env CMD="vi /etc/issue" bash' \
                   --tab --title who -e 'env CMD=who bash'

The error is raised because xargs cannot find a history command. It is a shell builtin, as you can confirm with type history, thus not visible to xargs. Try

echo 1 | xargs history -d; echo $?

The return value is 127. In man xargs, EXIT STATUS section:

0 if it succeeds
123 if any invocation of the command exited with status 1-125
124 if the command exited with status 255
125 if the command is killed by a signal
126 if the command cannot be run
127 if the command is not found
1 if some other error occurred.

Expanding on ilkkachu's comment, in principle you could invoke Bash and call history from the spawned shell.

echo 1 | xargs -I {} bash -c 'echo $HISTFILE; history' bash {}

The above command does not raise an error, after all the builtin history is available to the Bash shell. However, from that same command one also finds that HISTFILE is unset and history outputs nothing: The history is not enabled on a non-interactive shell. Again, you could activate it with the set builtin, export HISTFILE and HISTFILESIZE... But we don't want a headache. Editing .bash_history directly is the straightforward way to go.